As it looks like we will be delaying the release, I propose that we have another beta round. Would 2.9-beta2 be a sensible name? We should also propose GeoTools 15-beta2. These fixVersion tags can be used for new issues on master.
We should also declare a lifting of the code freeze.
Kind regards,
--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/>
New Zealand
I had added releases to the schedule (see https://github.com/geoserver/geoserver/wiki/Spring-4-Upgrade). We can issue a beta2 when the feature branch is merged back in.
Not sure this needs to affect geotools release schedule - geoserver beta2 may end up using geotools 15.1 for example.
On 3 March 2016 at 12:14, Ben Caradoc-Davies <ben@anonymised.com> wrote:
As it looks like we will be delaying the release, I propose that we have
another beta round. Would 2.9-beta2 be a sensible name? We should also
propose GeoTools 15-beta2. These fixVersion tags can be used for new
issues on master.We should also declare a lifting of the code freeze.
Kind regards,
–
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/>
New Zealand
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
Geoserver-devel mailing list
Geoserver-devel@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
–
Jody Garnett
Thanks, Jody.
I think this certainly does affect the GeoTools release schedule. The release schedule is aligned to enable coordinated changes. For example, what if we need to change a GeoTools transitive dependency or change an API in GeoTools to complete the GeoServer Spring 4 upgrade? We would need a GeoTools 16 milestone at the least, and I think that would be bad as milestones get less testing. I support keeping the alignment of GeoTools releases with GeoServer releases despite the delay in the GeoServer release.
Kind regards,
Ben.
On 04/03/16 09:44, Jody Garnett wrote:
I had added releases to the schedule (see
https://github.com/geoserver/geoserver/wiki/Spring-4-Upgrade). We can issue
a beta2 when the feature branch is merged back in.Not sure this needs to affect geotools release schedule - geoserver beta2
may end up using geotools 15.1 for example.--
Jody GarnettOn 3 March 2016 at 12:14, Ben Caradoc-Davies <ben@anonymised.com> wrote:
As it looks like we will be delaying the release, I propose that we have
another beta round. Would 2.9-beta2 be a sensible name? We should also
propose GeoTools 15-beta2. These fixVersion tags can be used for new
issues on master.We should also declare a lifting of the code freeze.
Kind regards,
--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/>
New Zealand------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/>
New Zealand
Yeah okay I can see that, dependencies will be thrown around with wild abandon during the spring 4 migration. We will delay geotools as well.
On 3 March 2016 at 13:08, Ben Caradoc-Davies <ben@anonymised.com> wrote:
Thanks, Jody.
I think this certainly does affect the GeoTools release schedule. The release schedule is aligned to enable coordinated changes. For example, what if we need to change a GeoTools transitive dependency or change an API in GeoTools to complete the GeoServer Spring 4 upgrade? We would need a GeoTools 16 milestone at the least, and I think that would be bad as milestones get less testing. I support keeping the alignment of GeoTools releases with GeoServer releases despite the delay in the GeoServer release.
Kind regards,
Ben.On 04/03/16 09:44, Jody Garnett wrote:
I had added releases to the schedule (see
https://github.com/geoserver/geoserver/wiki/Spring-4-Upgrade). We can issue
a beta2 when the feature branch is merged back in.Not sure this needs to affect geotools release schedule - geoserver beta2
may end up using geotools 15.1 for example.–
Jody GarnettOn 3 March 2016 at 12:14, Ben Caradoc-Davies <ben@anonymised.com> wrote:
As it looks like we will be delaying the release, I propose that we have
another beta round. Would 2.9-beta2 be a sensible name? We should also
propose GeoTools 15-beta2. These fixVersion tags can be used for new
issues on master.We should also declare a lifting of the code freeze.
Kind regards,
–
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/>
New Zealand
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel–
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/>
New Zealand
–
Jody Garnett