On Tue, 2007-05-15 at 14:26 +0200, Andreas Hartmann wrote:
> Thorsten Scherler schrieb:
...
> > If we agree that we do not have any urgent issues right now then we
> > announce the code freeze. Blocker issues that we may find in a RC can be
> > fixed in trunk as usual (without lifting the freeze)
>
> What if the fix requires fundamental or critical changes?
> Should the freeze be extended?
Actually fundamental or critical changes should not happen in the
release cycle. The freeze by definition is till we have a final release.
>
> [...]
>
> >> But if we mention the issue to the release notes, it might
> >> be reasonable to do the RC.
> >
> > A blocker cannot go into a release, the proxy issue for example is not a
> > blocker since it is partly working.
>
> OK, then we should change its status in Bugilla accordingly.
Actually all bugs (besides 42364) have they status as not critical,
where I am ATM a wee bit unsure about 34994 (not having dav support is a
pity).
>
> > It is a known issue and we should list it in the release notes.
> >
> >> 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.
> >
> > Yes, since we consider them as critical (e.g. core operations) like e.g.
> > you cannot login.
> >
> > Makes sense?
>
> Sure, I was just confused by the "blocker" status of the proxying bug.
> BTW, we have another critical one (42364). Should we update its status
> as well?
Actually this is a blocker and needs to be addressed in the rc.
salu2
--
Thorsten Scherler thorsten.at.apache.org
Open Source Java consulting, training and solutions
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
