Let's Discuss Interim Releases (and a Rolling Release)

Marco Trevisan marco.trevisan at canonical.com
Fri Mar 1 12:06:26 UTC 2013

Il giorno ven, 01/03/2013 alle 07.12 +0100, David Henningsson ha
> When I was new to Ubuntu, the intuitive thing to do to help out was to 
> download a beta release, test it, and report bugs. That's what betas are 
> for, right? Well, I learned that if I did that, the developers were 
> triaging my bug report around final freeze, and after that there was no 
> possibility to change anything. I then tried reporting bugs much 
> earlier, all I would get was a report back two months later, telling me 
> to test a new version of the package. After a few cycles, I had learned 
> that the right time to do testing was around feature freeze; when it's 
> still easy to upload, but the upstream versions have stopped pouring in.
> As we now move to a rolling release schedule, when is the right time to 
> do a wide-scale testing and report bugs? Without just being met with a 
> "please check if it's fixed in the next version" message?

As we're suggesting to move to a RR with Quality in mind, I think that
the right moment to report bugs is "as soon as you see them" and it's up
to the developers to fix them as soon as possible without big delays, as
the the timeframe to develop is now extended without any rush for FF or
UIF (at least, until next LTS) and most of features can be stopped for a
while until we don't have a stable and fixed build to work on.

More information about the ubuntu-devel mailing list