Thorsten Scherler schrieb:
> On Tue, 2007-05-15 at 13:12 +0200, Andreas Hartmann wrote:
>> 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?
>
> Actually the recent threads make a nice document but someone needs to
> hack it together (be it in the wiki or preferable in our documentation).
OK, does anyone have the knowledge and time to do this?
> As I understood the problematic there is no easy fix for this issue
> meaning we should not risk anything and state clearly about the limited
> support as recommend by Richard and others.
>
>> [...]
>>
>>> 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?
>
> 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?
[...]
>> 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.
> 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?
-- Andreas
--
Andreas Hartmann, CTO
BeCompany GmbH
http://www.becompany.ch
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
