Reduce bugginess of .0 releases
Closed, ResolvedPublic

Description

5.13.0 was an awesome release, but it suffered from a number of bugs and regressions:

Thoughts on how we can improve this with the next release?

ngraham created this task.Jun 28 2018, 1:17 PM
ngraham updated the task description. (Show Details)Jun 28 2018, 2:06 PM

I think we should increase the visibility of our beta phase and encourage people to take part in it.

To do that we can communicate to people more clearly that if they would install for example Neon Dev Stable instead of the User edition it allows exactly this seamlessly. For that and to encourage more people to take part I would urge to change the name "Neon Dev Stable" to something like "QA Contributor edition" or just "Contributor edition". So a name that signals the importance and the higher commitment the person is willing to bring in. Distros like OpenSuse with a beta channel could do something similar.

Mostly failed to do this due to Bionic upgrade taking focus away, still ToDo for 5.15 then

ngraham closed this task as Resolved.May 16 2022, 7:40 PM

We have had beta days for the last few releases and they've worked well. We haven't managed to get down to zero .0 regressions, but we've been doing better overall. Closing.