Petr Mladek píše v Po 03. 09. 2012 v 18:41 +0200:
4. Do 3.7.0-RCs every week (use the original schedule). There is not
enough time for feedback = demotivating for QA.
After all, this is still good solution. We released, 3.5 and 3.6 this
way and it somehow worked. The .0 release is
Bjoern Michaelsen píše v Čt 30. 08. 2012 v 17:41 +0200:
On Thu, Aug 30, 2012 at 05:14:02PM +0200, Petr Mladek wrote:
As mentioned, the 3.7.0 release and 3.7.1-rc1 are planed for the same
week now. It is bad because there is no time to proceed feedback from
3.7.0 users.
Comparing:
Bjoern Michaelsen píše v Čt 30. 08. 2012 v 17:41 +0200:
On Thu, Aug 30, 2012 at 05:14:02PM +0200, Petr Mladek wrote:
As mentioned, the 3.7.0 release and 3.7.1-rc1 are planed for the same
week now. It is bad because there is no time to proceed feedback from
3.7.0 users.
Comparing:
Petr Mladek píše v Čt 30. 08. 2012 v 16:53 +0200:
Hi,
on the recent ESC call, we agreed to try two weeks between RCs. It will
allow QA to do more testing. Also it will allow developers to fix the
found regressions.
Please, find the updated release plan at
On Thu, Aug 30, 2012 at 05:14:02PM +0200, Petr Mladek wrote:
As mentioned, the 3.7.0 release and 3.7.1-rc1 are planed for the same
week now. It is bad because there is no time to proceed feedback from
3.7.0 users.
Comparing:
https://wiki.ubuntu.com/PrecisePangolin/ReleaseSchedule
Petr Mladek píše v Čt 30. 08. 2012 v 16:53 +0200:
Hi,
on the recent ESC call, we agreed to try two weeks between RCs. It will
allow QA to do more testing. Also it will allow developers to fix the
found regressions.
Please, find the updated release plan at
