[QGIS-Developer] QGIS 3.0 Soft Feature Freeze

[Nyall Dawson]

On 3 January 2018 at 06:51, Tim Sutton <tim at kartoza.com> wrote:
>
> Hi
>
> On 02 Jan 2018, at 12:16, Nyall Dawson <nyall.dawson at gmail.com> wrote:
>
> On 2 January 2018 at 19:54, Mathieu Pellerin <nirvn.asia at gmail.com> wrote:
>
>
> +1 to set a release date for the last week of January. That'll give us 2 weeks of freeze period (assuming the vote turns out not to extend the soft freeze) which can be used to focus on fixes only. The soft freeze period saw a nice set of fixes too, which was nice.
>
>
> I'm in favour of hard freezing this time (assuming we can get those
> last couple of PRs reviewed quickly and merged).
>
> But I'm against setting a hard deadline for the final release yet.
> That said truth is that IMO 3.0 still feels very buggy, and there's
> lots of open high priority regressions against it. I think we've got
> two options:
>
> 1. Move to a regular "are we ready for final release?" vote
>
> or
>
> 2. Just decide that 3.0.0 will have bugs, and that we should "release
> early, release often" and hope that we stabilise things quickly for
>
> 3.0.1/3.0.2/…
>
>
>
> I think on balance I prefer option #2 as it will get more people using QGIS 3 - we must just be careful to tell people that it is ‘next-gen’ and that the LTR is still 2.18….

Ok, let me re-word option 2 as:

"2. Carefully manage release expectations, with detailed explanations
of known issues and regressions in the release notes. Stress in press
releases/release notes that 3.0 is a new major release and that the
QGIS team do not consider it a suitable replacement for the current
stable LTR release, and that it is highly recommended that
organisations do not replace their existing QGIS 2.x installations
before careful in-house testing and evaluation of its suitability for
their workplace. The next stable LTR QGIS release will be QGIS 3.2."

Nyall