Hi Torsten,

Thanks for kickstarting the release process.

On Fri, Nov 16, 2012 at 2:27 PM, Torsten Dreyer wrote:

> 1. A lack of stress testing.
> We have a four weeks testing period with release binaries publically
> available, so I am not sure how to improve that. Do we need more
> testers? Do we need more time?

We've already got a fairly extensive lead-in time for the release.  More
testers on more platforms would seem to be the answer.  Perhaps we should
advertize for testers of those platforms that aren't adequately covered by
developers running git?

Making a complete package available, not just the binaries would help, as
testers wouldn't need to be git-aware.

> 2. Lack of graceful feature scaling.
> Is this really something we can solve in the release process?
AFAIK this was caused by the random buildings code, and entirely my fault.
I think that is probably a once-off rather than a systemic problem.

> 3. Change of the NOAA METAR url
> Also, this is more a bug or feature request than an issue with the
> release process


8. Write the changelog ASAP
> Yes - That can easily start right now. As it is just a simple wiki page,
> please contribute to
> http://wiki.flightgear.org/Changelog_3.0.0
As with the last release, I'll trim this down when we get to the release
date and produce a release announcement.
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
Flightgear-devel mailing list

Reply via email to