On Thu, Apr 07, 2011 at 05:42:48PM +0100, Ben Hutchings wrote: > > I would love if we can summarize the above part by saying that we have > > consensus on: 1) announcing at the beginning of a release cycle a target > > freeze month, 2) refining it later on. > > I think you're missing step 0: the release team consults with the whole > body of developers, presumably with a suggested freeze date/month as a > starting point. This would also mean step 1 would be delayed slightly.
Well, it depends. If for instance we go for the "fixed-period" scheme
(proposed in this thread and discussed in the latter part of my mail)
the specific freeze month is fixed in advance. I agree that the
decision of that specific month should go through a "we propose this"
first, but it will happens once and for all (barring the need of
reviewing it which of course might arise in the future).
Cheers.
--
Stefano Zacchiroli -o- PhD in Computer Science \ PostDoc @ Univ. Paris 7
zack@{upsilon.cc,pps.jussieu.fr,debian.org} -<>- http://upsilon.cc/zack/
Quando anche i santi ti voltano le spalle, | . |. I've fans everywhere
ti resta John Fante -- V. Capossela .......| ..: |.......... -- C. Adams
signature.asc
Description: Digital signature
