Re: Add 2.2.4 to bugzilla

[Sander Temme]

On Jan 11, 2007, at 12:42 PM, Ruediger Pluem wrote:

could someone please add version 2.2.4 to the product Apache httpd-2 in bugzilla?

Done.

Are there any ideas how we can document / automate this as part of the release process?

This issue pops up regulary after each release.

Hard to automate... but we could include it in the release checklist: Ask Bugzilla admin to add new version. I am one, and will be happy to do this ahead of the release. However, I usually space on it. The combined 2.2.x versions have 198 bugs in (New, Assigned, Reopened, NeedInfo): http://issues.apache.org/bugzilla/buglist.cgi?product=Apache +httpd-2&version=2.2- HEAD&version=2.2.0&version=2.2.2&version=2.2.3&version=2.2.4&bug_status= NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=NEEDINFO

...and 183 in Resolved or Verified:

http://issues.apache.org/bugzilla/buglist.cgi?product=Apache% 20httpd-2&version=2.2- HEAD&version=2.2.0&version=2.2.2&version=2.2.3&version=2.2.4&bug_status= RESOLVED&bug_status=VERIFIED

Of the latter:

60 are Resolved, Invalid
 7 are Resolved, Wontfix
 1 is  Resolved, Later
37 are Resolved, Duplicate
70 are Resolved, Fixed
 8 are Resolved, Worksforme
 0 are Verified





S.

--
[EMAIL PROTECTED]            http://www.temme.net/sander/
PGP FP: 51B4 8727 466A 0BC3 69F4  B7B8 B2BE BC40 1529 24AF

These can probably be closed in some way, shape or form. What do you think is sufficient inactivity to amount to lazy verification of a Resolution transition? A week? Can I get a hum on that? If any of the former still exist in 2.2.4, they should be moved to 2.2-HEAD.

smime.p7s
Description: S/MIME cryptographic signature