Re: Re-evaluating Ubuntu's Milestones

2018-05-01 Thread flocculant
On 09/04/18 02:46, Simon Quigley wrote: Hello, This past cycle was interesting, with Spectre/Meltdown complications among other things causing the first two Alphas to be cancelled, and on the Lubuntu side of things, we missed Beta 1 because of a critical bug that wasn't noticed due to lack of

Re: Re-evaluating Ubuntu's Milestones

2018-04-21 Thread flocculant
On 21/04/18 02:35, Simon Quigley wrote: Happy Release Week! I do not believe there have been any -1s to this proposal from any flavor, nor from the Release Team, so I think it's time to move forward with it. In summary, what will now happen from here on out is that opt-in milestones will be

Re: Re-evaluating Ubuntu's Milestones

2018-04-20 Thread Simon Quigley
Happy Release Week! I do not believe there have been any -1s to this proposal from any flavor, nor from the Release Team, so I think it's time to move forward with it. In summary, what will now happen from here on out is that opt-in milestones will be discontinued in favor of testing "weeks"

Re: Re-evaluating Ubuntu's Milestones

2018-04-11 Thread Dustin Krysak
I follow suit with Steve here with regards to the automated testing (the referenced gate). If there are toolsets that already exist - even better! And from the sounds of it, the process has already been vetted. Dustin On Mon, Apr 9, 2018, 16:13 Steve Langasek, wrote:

Re: Re-evaluating Ubuntu's Milestones

2018-04-10 Thread Martin Wimpress
Hi all, On 10 April 2018 at 03:58, Simon Quigley wrote: > Hello, > > On 04/09/2018 03:13 PM, Steve Langasek wrote: > >> The one other value milestone images provide is to give a "known good" image >> to install the development release from. We have solved this for Ubuntu

Re: Re-evaluating Ubuntu's Milestones

2018-04-09 Thread Simon Quigley
Hello, On 04/09/2018 03:13 PM, Steve Langasek wrote: > The one other value milestone images provide is to give a "known good" image > to install the development release from. We have solved this for Ubuntu > Desktop and Server by having automated tests that gate the promotion of an > image

Re: Re-evaluating Ubuntu's Milestones

2018-04-09 Thread Valorie Zimmerman
On Mon, Apr 9, 2018 at 1:35 PM, flocculant wrote: > On 09/04/18 21:13, Steve Langasek wrote: > > ... > > The one other value milestone images provide is to give a "known good" image > to install the development release from. We have solved this for Ubuntu > Desktop and

Re: Re-evaluating Ubuntu's Milestones

2018-04-09 Thread flocculant
On 09/04/18 21:13, Steve Langasek wrote: ... The one other value milestone images provide is to give a "known good" image to install the development release from. We have solved this for Ubuntu Desktop and Server by having automated tests that gate the promotion of an image build to "current".

Re: Re-evaluating Ubuntu's Milestones

2018-04-09 Thread Steve Langasek
On Mon, Apr 09, 2018 at 02:31:31PM -0500, Simon Quigley wrote: > On 2018-04-09 03:30, Oliver Grawert wrote: > > well, apart from actual installer fixes, your users should get all > > these fixes through package updates anyway ...  > Right, which is another point for getting rid of these extra

Re: Re-evaluating Ubuntu's Milestones

2018-04-09 Thread Rik Mills
Generally in favour here, and i saw no significant opposite opinions when we've informally discussed this in Kubuntu. Rik Mills Kubuntu Devel Kubuntu Council On 09/04/18 02:46, Simon Quigley wrote: > Hello, > > This past cycle was interesting, with Spectre/Meltdown complications > among other

Re: Re-evaluating Ubuntu's Milestones

2018-04-09 Thread Simon Quigley
Hello Oliver, On 2018-04-09 03:30, Oliver Grawert wrote: well, apart from actual installer fixes, your users should get all these fixes through package updates anyway ...  Right, which is another point for getting rid of these extra milestones, in my opinion. One thing that the other

Re: Re-evaluating Ubuntu's Milestones

2018-04-09 Thread Ian Bruntlett
Hi Simon, On 9 April 2018 at 02:46, Simon Quigley wrote: > I am proposing that we get rid of the Alpha and Beta 1 milestones > entirely, and we organize a monthly testing "week" (Tuesday through > Thursday), which involves no archive freezes, no formally released ISOs, >