Release milestones and cadence testing in R cycle

[Ho Wan Chan]

Hi guys.

Yesterday in a Ubuntu Developer Summit session it has been decided that
Ubuntu Desktop (aka so-called "vanilla" Ubuntu) will only have two
milestones: 1 beta and 1 release candidate.

Official derivatives like us can select whatever testing options we like.
We can select how many alphas (hopefully no) and betas we want to do.
Also we can choose do something called "Cadence testing", implemented for
vanilla Ubuntu in the Q cycle. It means that we need to test it every two
weeks. The testing period is a week long, and the daily images will still
be built. That means there will NOT be any freezes. if we find any bugs, we
can fix it and without passing through a freeze we can immediately see the
effects of the fix when the next daily build comes on.

So here are the questions I want to ask:

1. How many alpha and beta releases are we going to do?

2. Are we going to use the "Cadence testing" method to test our images?

Please bear in mind that in the past 6 months we only have about 2-4
testers doing testing in the previous milestones in the Q cycle. So we
really need to think about which solution is the best for us.

I am going to maybe add this to the blueprints for discussion. Hopefully we
can also discuss it in the Ubuntu Developer Summit tomorrow, which will be
held in room B3-M1 around 15:00-16:00 CET.

Let us see how will the testing go on:D

Regards,
Howard Chan (smartboyhw)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-studio-devel/attachments/20121031/795b45a4/attachment.html>