According to the current schedule, we have:
2017-09-18 18.0 2.12 1.12 stable release
2017-09-04 18.0-RC1 2.12-RC1 1.12-RC1 release candidate
2017-08-24 18.0-beta 2.12-beta 1.12-beta Jody Garnett beta release / code
freeze
Beta just got released today (2017-09-14), so this schedule is evidently
completely out the window. Normally we have two weeks before the RC, and
then another 2 weeks until the release.
In the interest of a somewhat sensible release date, while still giving
time to test and fix things, perhaps wait one week until RC1 (2017-09-21);
probably starting the RC1 release process next Wednesday?
Torben
On Thu, Sep 14, 2017 at 5:11 PM, Jody Garnett <[email protected]>
wrote:
> What do you suggestion Torben?
>
> We have a tension between getting off of master (lifting the code freeze)
> so RnD can continue; and holding on to the code freeze if a lot of bugs are
> going to turn up (and we have contributions in position to fix them next
> week.)
>
> I think it will come down to everyone's availability for testing and
> fixing next week. My own availability is only okay, I want to look at some
> of the packaging issues and confirm if they were fixed or not.
>
> --
> Jody Garnett
>
> On 13 September 2017 at 15:44, Torben Barsballe <
> [email protected]> wrote:
>
>> Given that we still seem to be finding plenty of bugs in the beta, I'm
>> going to say that has not yet done its job of making sure that master is
>> releasable (See the thread "GeoServer 2.12-beta artifacts available for
>> testing"). I think it needs some rather more thorough testing by a wider
>> range of people.
>>
>> Torben
>>
>> On Wed, Sep 13, 2017 at 10:55 AM, Jody Garnett <[email protected]>
>> wrote:
>>
>>> Picking up a conversation from gitter, with the beta un blocked we can
>>> start to update the poor release schedule: https://github.com/g
>>> eoserver/geoserver/wiki/Release-Schedule
>>>
>>> The way i figure it the beta release has done its job of making sure
>>> master is releasable -and I do not see any reason to "wait" to make the RC
>>> (which is where unfreeze and get limited testing from our user list).
>>>
>>> With that in mind can I ask two questions:
>>>
>>> 1) Can we start the RC1 on Monday 18 September, followed by release
>>>
>>> There are some priorities for testing:
>>> - Does CORS instructions work correctly for the bin distribution (needed
>>> to have some jars packaged)
>>> - Do all the different bundles correctly include marlin
>>>
>>> This would end the code freeze (which was the question from Gitter).
>>>
>>> We would need a volunteer for the RC to go ahead next week.
>>>
>>> 2) Are we okay with a shorter one week RC - with a Monday 25 September?
>>>
>>> Sorry about the GWC integration not going smooth; thanks to everyone who
>>> helped out.
>>> --
>>> Jody Garnett
>>>
>>> ------------------------------------------------------------
>>> ------------------
>>> Check out the vibrant tech community on one of the world's most
>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>> _______________________________________________
>>> Geoserver-devel mailing list
>>> [email protected]
>>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>>
>>>
>>
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
