Board index FlightGear The FlightGear project News

[TESTERS] 2.6.0 release preparations

News from the ever evolving world of FlightGear.

[TESTERS] 2.6.0 release preparations

Postby Gijs » Sun Dec 11, 2011 11:31 am

FlightGear 2.6.0 will be released on February 17, 2012. In order to provide a stable and smooth release we've set up a release plan. In this topic we will keep you informed on the current and upcoming state.

Please post any questions/doubts that you may have*. Now is the time to ask and clear things up.
More info on our release cycle can be found in the release plan.

* this topic is locked in order to keep the important messages all in one place. Feel free to open a new topic for your questions.
Airports: EHAM, EHLE, KSFO
Aircraft: 747-400
User avatar
Gijs
Moderator
 
Posts: 9306
Joined: Tue Jul 03, 2007 2:55 pm
Location: Amsterdam/Delft, the Netherlands
Callsign: PH-GYS
Version: Git
OS: Windows 10

Re: [CONTRIBUTORS] 2.6.0 release preparations

Postby Gijs » Thu Dec 15, 2011 9:16 pm

On December 17, our Git repository will be declared "frozen". This means that no new features or major changes shall be pushed. This period is for preparing the code for the release and make sure there are no major issues. It lasts for four weeks until creation of the release branches (January 17).

Contrary to the last release cycle, aircraft in fgdata may be handled as an exception from the frozen state. Any change to aircraft may be pushed to the repository if it is guaranteed that this change does not affect any other aircraft or system and if no file outside the root directory of that specific aircraft is changed. Aircraft defined as part of the base package (e.g. the c172p) enter the frozen state and shall not undergo major changes in that period.

Keep in mind that the people that are able to commit your stuff are just as busy finishing their own work as you are! Therefore it is important that you create merge requests for everything that you'd like to see included in the upcoming release, as soon as possible. This includes new aircraft and large updates to existing aircraft. This will also give everyone more time to check for bugs.

Don't let it wait for tomorrow, do it today!

Please post any questions/doubts that you may have. Now is the time to ask and clear things up.
More info on our release cycle can be found in the release plan.
Airports: EHAM, EHLE, KSFO
Aircraft: 747-400
User avatar
Gijs
Moderator
 
Posts: 9306
Joined: Tue Jul 03, 2007 2:55 pm
Location: Amsterdam/Delft, the Netherlands
Callsign: PH-GYS
Version: Git
OS: Windows 10

Re: [CONTRIBUTORS] 2.6.0 release preparations

Postby Gijs » Sat Dec 17, 2011 12:35 pm

December, 17th has arrived everywhere on this planet. This is our magic day for the next FlightGear version 2.6.0 to be released in just two months time from now (February 17th, 2012).

All our new features for the next release should be in the Gitorious repositories by today and the next four weeks should be used for hardening our code base.

  • Everybody working on the source code is strongly encouraged to review the code and look for potential issues. Maybe there are already some in the bugtracker, so it might be worth looking there, too. Please recompile your code with -Wall and carefully look at the compiler warnings - there are still too many and not all of them are nonsens. Please try to change your code so that no warnings are generated.
  • Aircraft developers can now check their models against a known set of features and are welcome to push their latest versions to FGDATA until short before we create the release branch.
Thanks everybody who has contributed during the last months. We have some great new features waiting to be explored and we probably also have fixed some long standing bugs. Now, let's try to make this the best FlightGear ever! Being almost green and mostly sunny with just a few showers on Jenkins is a good start.

The next action in our release plan will happen on January, 17th when we create the release branches. All the details and much more is published in the release plan.
Airports: EHAM, EHLE, KSFO
Aircraft: 747-400
User avatar
Gijs
Moderator
 
Posts: 9306
Joined: Tue Jul 03, 2007 2:55 pm
Location: Amsterdam/Delft, the Netherlands
Callsign: PH-GYS
Version: Git
OS: Windows 10

Re: [CONTRIBUTORS] 2.6.0 release preparations

Postby Gijs » Thu Jan 12, 2012 4:12 pm

In less than one week we will pass the outer marker for our release of FlightGear 2.6.0: the creation of the release branches in our git repositories. A good time to read the final checklist:

  • All features work as desired?
  • All major bugs fixed?
  • All aircraft in FGDATA checked in?
  • No console debug messages?
The EOBT (estimated-off-branch-time?) for our branches is 0800UTC on January, 17th. We'll announce the precise time the evening before that day.

Please note that during that short period of 1-2 hours, everybody with commit rights is requested to _NOT_ push anything to our repositories.
Go flying, hug your kids, have a beer at the pub - whatever you like. Just stay away from http://gitorious.org/fg.

Please fasten your seat belts, fold away the table in front of you and turn off all your electronic devices. Thanks for flying FlightGear!
Airports: EHAM, EHLE, KSFO
Aircraft: 747-400
User avatar
Gijs
Moderator
 
Posts: 9306
Joined: Tue Jul 03, 2007 2:55 pm
Location: Amsterdam/Delft, the Netherlands
Callsign: PH-GYS
Version: Git
OS: Windows 10

Re: [CONTRIBUTORS] 2.6.0 release preparations

Postby Gijs » Mon Jan 16, 2012 8:31 pm

Soooo - the outer marker is hooting, final checklist ist completed, the gear is down and shows three green - let's go for it!

Tomorrow morning, on Jan. 17th between 06:00 and 09:00 UTC, We'll bump the version number to 2.6.0, tag and branch gitorious and if everything turns out as expected, bump the next/master branch to 2.7.0 for the next release cycle. Please, NO COMMIT AND NO PUSH during that period to ANY repository in http://gitorious.org/fg

We'll post a message here and on the mailing list when this task is completed.

Thanks for you cooperation!
Airports: EHAM, EHLE, KSFO
Aircraft: 747-400
User avatar
Gijs
Moderator
 
Posts: 9306
Joined: Tue Jul 03, 2007 2:55 pm
Location: Amsterdam/Delft, the Netherlands
Callsign: PH-GYS
Version: Git
OS: Windows 10

Re: [CONTRIBUTORS] 2.6.0 release preparations

Postby Gijs » Tue Jan 17, 2012 10:25 am

The release branches are ready and the next/master branches are open again for cool, great and fancy new features.

Please have a close look on the bug tracker and help sorting out the issues mentioned there. If you are unable to fix them, you can always try to provide info and test proposed "fixes".

What's next?
  • New development goes into next (fg/sg) and master (fgdata).
  • Bug fixes go into next (fg/sg) and master (fgdata). If they also fix a bug for the 2.6.0 release, please cherry-pick them into release/2.6.0
  • Bug fixes that do not match the current development because next|master have moved on go directly into release/2.6.0
Airports: EHAM, EHLE, KSFO
Aircraft: 747-400
User avatar
Gijs
Moderator
 
Posts: 9306
Joined: Tue Jul 03, 2007 2:55 pm
Location: Amsterdam/Delft, the Netherlands
Callsign: PH-GYS
Version: Git
OS: Windows 10

Re: [TESTERS] 2.6.0 release preparations

Postby Gijs » Fri Jan 27, 2012 9:13 pm

With just three more weeks to go till the release of FlightGear 2.6.0, we started distributing so called release candidates. These are basically complete releases, meant for testing by a large group of people. As the actual release is still some time away, bugs found during these tests have a fair chance getting fixed. Do note that the earlier bugs are reported, the more time we'll have to fix them.

See the introduction topic of our special "Release candidates" subforum for details and...

Start testing!
Airports: EHAM, EHLE, KSFO
Aircraft: 747-400
User avatar
Gijs
Moderator
 
Posts: 9306
Joined: Tue Jul 03, 2007 2:55 pm
Location: Amsterdam/Delft, the Netherlands
Callsign: PH-GYS
Version: Git
OS: Windows 10


Return to News

Who is online

Users browsing this forum: No registered users and 2 guests