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:
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.
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.
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.
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:
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.
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.
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.
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.
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:
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.
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.
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?
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.
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.
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:
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.
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.