On Wed, 2008-04-16 at 20:43 +0000, Renier Morales wrote: > > > > We can certainly have an earlier stable release depending on need > and > > > bug fixes that go into 2.11.x. > > > Can I assume you have a specific need for having 2.12 in the > summer? > > > > I took a quick peek at the closed bugs/features in 2.11.x that are > not > > in 2.10.2. There are probably more, but these are the significant > ones > > I'm familiar with: > > > > 1924661 and 1888910: Involve adding LSB block to daemon init script > > * Probably not that big of a deal, except that at least two > > distros are having to patch this in right now. > > > > 1841151: Add the iLO2 plugin > > * Adds support for a family of rackmount servers which are of > > interest to HPI users > > * Strengthens OpenHPI's position as the de facto > implementation of > > HPI > > > > 1922399: Add the oa_soap plugin > > * Adds support for another major family of bladed server > hardware, > > also of interest to HPI users > > * Also strengthens OpenHPI's position as the de facto > > implementation of HPI > > > > 1804510: Name change of err() and dbg() macros > > * Changed names of these macros because the old ones caused > > confusion, resulting in unintended output to the system > error > > log > > * In itself, not that significant...however since this change > > affects so much code, it makes it more difficult to support > both > > the development trunk and the older 2.10.x versions, > especially > > for out-of-tree plugins > > > > Based on these, I'd suggest an earlier 2.12 release. However, this > is a > > lot of new code, so it certainly makes sense for it to stabilize for > a > > couple of months. > > > > Secondly, from what I understand, a delay in 2.12 is more difficult > for > > the distributions. Dates I've seen indicate that both SuSE and Red > Hat > > have code freeze dates this summer for upcoming releases, so an > earlier > > 2.12 would have a better chance of being accepted by them. Debian's > > next release target is September, and so a 2.12 version could also > > become part of Lenny if 2.12 came out earlier in the summer rather > than > > later. > > 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?
Being new to OpenHPI I am not familiar with the release logistics, please bear with me if I am asking obvious questions. Do we typically plan several interim development releases before a final release? Are there any major infrastructure changes planned that would require substantial work, hence requiring multiple interim releases? What is the planned content for these interim releases? We might be able to pitch in to help expedite the release. Thanks, -- Shuah ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Openhpi-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openhpi-devel
