Re-evaluating Ubuntu's Milestones

[foss.freedom]

We mentioned this to Simon privately ... but saying things publicly is
also useful... Ubuntu Budgie fully agrees with this approach.

If the "advertisement - promotion" aspect is useful to prevent the
flavours being drowned out by plain old ubuntu (!) then we could just
call the post feature freeze test event "beta 1".  It will give those
friendly blog sites something to latch onto.

David

On 10 April 2018 at 16:47, Martin Wimpress
<martin.wimpress at canonical.com> wrote:
> Hi all,
>
>
> On 10 April 2018 at 03:58, Simon Quigley <tsimonq2 at ubuntu.com> wrote:
>> Hello,
>>
>> On 04/09/2018 03:13 PM, Steve Langasek wrote:
>> <snip />
>>> 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".  I would strongly encourage flavors to collaborate
>>> around this automation, instead of continuing to rely on a heavy-weight
>>> manual test process that leaves the "known good" image stale for weeks at a
>>> time.
>>>
>>> Code for this automation lives here:
>>>
>>>   https://code.launchpad.net/~ubuntu-test-case-dev/ubuntu-test-cases/desktop
>>>
>>> If there is interest from flavors in having this image gate, I would be
>>> willing to argue for Canonical hosting of the test infrastructure, as
>>> necessary.
>>>
>>> And if there *isn't* interest from flavors in doing this, well, I also don't
>>> think that should block on that as a reason to carry on with the existing
>>> milestone process, which I think is a very inefficient use of everyone's
>>> time.
>>
>> I think this is an excellent idea which would be great to look into for
>> the 18.10 cycle.
>>
>> Count Lubuntu in.
>>
>
> Absolutely count Ubuntu MATE in too.
>
>>> So to summarize, I think the right path forward is:
>>>
>>>  - discontinue all opt-in milestones for 18.10 and beyond
>>>    - implicitly discontinuing the matching milestone freezes
>>>  - coordinate a cadence of "testing weeks", organized by the flavor leads
>>>    (i.e.: requires no involvement from ubuntu-cdimage or ubuntu-release in
>>>    order to drive to success)
>>>  - at the flavor teams' discretion, implement automated QA gating of daily
>>>    image promotions
>>
>> Great, I think we're on the same page here. :)
>
> If the above can happen, that would be fantastic. Automating the heavy
> lifting of testing basic installer capabilities is great. In my
> experience the people interested in contributing time to QA are most
> interested in testing how new features look/work than ensuring the
> various install options are well tested and working.
>
> Regards, Martin.
>
> --
> Ubuntu-release mailing list
> Ubuntu-release at lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release