[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Requesting freeze exception for OpenHPI 2.12.0-1



Hi,

I am requesting a freeze exception for OpenHPI 2.12.0-1.  It is a new
upstream version.  Please hear my case:

OpenHPI uses an even/odd release numbering scheme for release and
development versions, similar to the Linux kernel.  Currently,
Lenny/testing contains a development version, 2.11.2-1.  I uploaded that
in June, knowing that:
* there were substantial changes from the previous 2.10.x versions,
* that it would require a trip through the new queue,
* that upstream planned a summer release for 2.12.0, and
* it would be good to get some testing exposure in Debian before 2.12.
It was expected that the summer 2.12 version would line up with a fall
release of Lenny.

The same weekend you sent your e-mail [1] about the upcoming Lenny
freeze, OpenHPI was also in a week-long code freeze for 2.12.0.  I
considered trying to produce a not-quite-released 2.12 version for
Debian, but the spirit of the e-mail from the release team on Tuesday
[2] indicated that you'd rather see us take a few extra days and get it
right, rather than rushing to make the deadline.  The upstream 2.12.0
released on 7/25 [3].

I have done that, tested the 2.12.0-1 version currently in unstable, and
believe it to be the best and most supportable version for Lenny.  I'm
asking that this be allowed into testing, since we're still early in the
freeze.

Below, I've provided references to bugs fixed in the 2.12 version, which
would be present in 2.11.2 currently in Lenny.  None of these is
release-critical, so I can't argue the case on those merits.  OpenHPI
(libopenhpi2) has only one rdepends outside of itself: heartbeat.
Therefore, the risk to other packages is minimal.

>From my perspective as a package maintainer, the most important reason
to update to 2.12.0 is to have a supportable upstream version.

Thanks for your consideration,
Bryan Sutula

References:
1: http://lists.debian.org/debian-devel-announce/2008/07/msg00007.html
2: http://lists.debian.org/debian-devel-announce/2008/07/msg00006.html
3: http://sourceforge.net/mailarchive/message.php?msg_name=OFC5BD7579.04771702-ON87257491.0071D5B1-86257491.00722CF4%40us.ibm.com

Bugs fixed:
http://sourceforge.net/tracker/index.php?func=detail&aid=1930512&group_id=71730&atid=532251
http://sourceforge.net/tracker/index.php?func=detail&aid=2027371&group_id=71730&atid=532251
http://sourceforge.net/tracker/index.php?func=detail&aid=2027043&group_id=71730&atid=532251
http://sourceforge.net/tracker/index.php?func=detail&aid=2021749&group_id=71730&atid=532251
http://sourceforge.net/tracker/index.php?func=detail&aid=2019614&group_id=71730&atid=532251
http://sourceforge.net/tracker/index.php?func=detail&aid=2016272&group_id=71730&atid=532251
http://sourceforge.net/tracker/index.php?func=detail&aid=2013946&group_id=71730&atid=532251
http://sourceforge.net/tracker/index.php?func=detail&aid=1963765&group_id=71730&atid=532251
http://sourceforge.net/tracker/index.php?func=detail&aid=1823713&group_id=71730&atid=532251
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=493032



Reply to: