Michael Wechner schrieb:
> Thorsten Scherler wrote:
>
>> Hi all,
>>
>> I did a small search on all open bugs for 1.4.
>> http://tinyurl.com/2r482h (that is one reason I hate bugzilla the url
>> had a length of 1269 characters!).
>>
>> IMO there is no blocker in there anymore that cannot wait till 1.4.1. I
>> think we should to roll up a rc to get the beast out of the door.
>>
>> wdyt?
+1
What does that mean about the proxying issue?
Do we already have a decent documentation what can be done and how?
[...]
> As a note I think we shouldn't cancel RCs anymore just because more bugs
> might show up in the meantime, but rather collect
> them together with possible bug showing up within the RC and try to fix
> them or the next RC.
Should we continue the freeze and do the RC even if we find blockers?
As I understand it, the term "blocker" refers to a bug which prevents
a release. But if we mention the issue to the release notes, it might
be reasonable to do the RC.
BTW, our release mgmt guidelines [1] aren't very specific about this
case ("If tests fail, then ...").
According to the wiki [2], blockers and critical bugs must be fixed
before the release.
[1] http://lenya.apache.org/docs/release.html
[2] http://wiki.apache.org/lenya/ProjectReleaseHowTo
-- Andreas
--
Andreas Hartmann, CTO
BeCompany GmbH
http://www.becompany.ch
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
