Weekly Releases: March Roadmap, 1.6rc2.5, 1.7.1
Team,
As announced in February: <a href="http://blog.jquery.com/2009/02/12/jquery-ui-17-is-the-new-16/">http://blog.jquery.com/2009/02/12/jquery-ui-17-is-the-new-16/</a> , starting this month (March) we're doing weekly releases (it's actually bi-weekly releases on two different branches, alternating weeks). Our first was last week with 1.7. Yay! From now on we'll alternate with preview and stable bug fix releases. This means:
March 11: 1.6rc2.5
March 18: 1.7.1
March 25: 1.6rc2.6 or 1.6final
April 1: 1.7.2
Releases are scheduled for Wed. morning. Nothing will block a release. The trunk needs to be stable enough that the release can happen. Always. Not the day of, not the day before. Instability that could otherwise block the release needs to remain in a ticket patch or a development branch. If something isn't finished or ready, the release goes on, and the feature or fix can be worked on for the next release, 2 weeks later.
<b>1.6rc2.5 to 1.6 final</b>
1.6rc2.5: Tomorrow we'll release 1.6rc2.5. This will be 1.6rc2 plus any bug fixes that were done for 1.6rc3 not including migration to the new jQuery UI CSS Framework, and not including API changes. No new code will be written for this initial preview release. It will simply be a merging of selected fixes (drawing a line in the svn revision history for each plugin). This will provide a baseline against which the team and community can develop and test against for the next two weeks, in preparation for 1.6 final.
<b>1.7.1, 1.7.2 etc.</b>
As stated on the Development and Planning wiki ( <a href="http://wiki.jqueryui.com/FrontPage#status">http://wiki.jqueryui.com/FrontPage#status</a> ), stable bug fix releases will not be developed in the trunk, but in a branch. This is only kind of true, depending on how you look at it. Let me explain. Assume a bug is found today in 1.7. This bug is filed against 1.7 and the milestone is set to 1.8 (not 1.7.1). The bug is worked on and fixed in the trunk (currently version 1.8pre). After this point, the bug can be considered for inclusion in the next stable bug fix release (if another one happens). This means development won't be done on the 1.7.x branch itself. Rather specific crtical fixes will be merged from the trunk to the branch. This accomplishes a few things
- ensures a stable bug fix release can't be blocked by something that's in the milestone, but not yet completed
- ensures changes happen in both the trunk and the branch
- allows for development to start on the next major release (1.8) without waiting for the last stable bug fix release (1.7.3? 1.7.4?)
- ensures only the most critical and blocker fixes are included in the stable bug fix release
Please let me know if you have any questions or feedback. Thanks.
- Richard
As announced in February: <a href="http://blog.jquery.com/2009/02/12/jquery-ui-17-is-the-new-16/">http://blog.jquery.com/2009/02/12/jquery-ui-17-is-the-new-16/</a> , starting this month (March) we're doing weekly releases (it's actually bi-weekly releases on two different branches, alternating weeks). Our first was last week with 1.7. Yay! From now on we'll alternate with preview and stable bug fix releases. This means:
March 11: 1.6rc2.5
March 18: 1.7.1
March 25: 1.6rc2.6 or 1.6final
April 1: 1.7.2
Releases are scheduled for Wed. morning. Nothing will block a release. The trunk needs to be stable enough that the release can happen. Always. Not the day of, not the day before. Instability that could otherwise block the release needs to remain in a ticket patch or a development branch. If something isn't finished or ready, the release goes on, and the feature or fix can be worked on for the next release, 2 weeks later.
<b>1.6rc2.5 to 1.6 final</b>
1.6rc2.5: Tomorrow we'll release 1.6rc2.5. This will be 1.6rc2 plus any bug fixes that were done for 1.6rc3 not including migration to the new jQuery UI CSS Framework, and not including API changes. No new code will be written for this initial preview release. It will simply be a merging of selected fixes (drawing a line in the svn revision history for each plugin). This will provide a baseline against which the team and community can develop and test against for the next two weeks, in preparation for 1.6 final.
<b>1.7.1, 1.7.2 etc.</b>
As stated on the Development and Planning wiki ( <a href="http://wiki.jqueryui.com/FrontPage#status">http://wiki.jqueryui.com/FrontPage#status</a> ), stable bug fix releases will not be developed in the trunk, but in a branch. This is only kind of true, depending on how you look at it. Let me explain. Assume a bug is found today in 1.7. This bug is filed against 1.7 and the milestone is set to 1.8 (not 1.7.1). The bug is worked on and fixed in the trunk (currently version 1.8pre). After this point, the bug can be considered for inclusion in the next stable bug fix release (if another one happens). This means development won't be done on the 1.7.x branch itself. Rather specific crtical fixes will be merged from the trunk to the branch. This accomplishes a few things
- ensures a stable bug fix release can't be blocked by something that's in the milestone, but not yet completed
- ensures changes happen in both the trunk and the branch
- allows for development to start on the next major release (1.8) without waiting for the last stable bug fix release (1.7.3? 1.7.4?)
- ensures only the most critical and blocker fixes are included in the stable bug fix release
Please let me know if you have any questions or feedback. Thanks.
- Richard
Topic Participants
Richard Worth
cloudream
huixiu