This was my understanding also, but I think that Andrea is right that we 
did not make it an explicit decision, or record it in the notes.

Shall we be clear and say the new freeze is, say, one or two weeks 
before 2.9-beta2?

In my view, the purpose of the freeze is to allow the orderly assembly 
of a beta and the branching of the RC. I see no point in freezing too 
early and another month might be overkill.

Kind regards,
Ben.

On 11/03/16 10:30, Jody Garnett wrote:
> My understanding is that the code freeze is off, schedule updated to
> include a second beta (which would start a new code freeze), testing and
> then a RC (which would start a new master).

-- 
Ben Caradoc-Davies <[email protected]>
Director
Transient Software Limited <http://transient.nz/>
New Zealand

------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785111&iu=/4140
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Reply via email to