From: Renier M. <re...@us...> - 2008-04-17 16:32:17
|
ope...@li... wrote on 04/17/2008 10:51:31 AM: > > In that case lets settle for the following release dates: > > 2.11.1 - 4/18 > > 2.11.2 - 5/16 > > 2.11.3 - 6/13 > > 2.11.4 - 7/11 > > 2.12.0 - 8/8 > > > > How does that sound? > > Do we typically plan several interim development releases before > a final release? Yes. > Are there any major infrastructure changes planned that would require > substantial work, hence requiring multiple interim releases? The interim (development) releases are for adding new features. The development releases serve as a test bed for these new features and allows for stabilization time. There is one feature, discussed on the ML last year, that I'm working on for 2.12.0 which changes the way domains are dealt with in order to provide some redundancy: https://sourceforge.net/tracker/index.php?func=detail&aid=1945076&group_id=71730&atid=532254 That one will need some time to stabilize. I have other features for additional hardware support, but these will happen at the end of '08. > What is the planned content for these interim releases? Take a look at the SF tracker for groups 2.11.1, 2.11.2, ... etc. Usually, a few things get pushed to the next devel release depending on time constraints, or amount of work needed to close them. The expectation is that as bugs are reported they will be placed in the next release groups. Other bugs are just in progress (e.g. the memory leak bug, looks like it might need to wait until 2.11.3). > We might be able to pitch in to help expedite the release. So I assume the plan above is not soon enough for you. When do you need a stable release? --Renier |