On Thursday, July 11, 2013 10:31:03 AM Aigars Mahinovs wrote:
> On 11 July 2013 08:43, Scott Kitterman <[email protected]> wrote:
> > > It seems so strange to spend six months saying "don't touch that" just
> > > to turn around and then spend nine months begging people to touch
> > > that...
> > I know it can be confusing, but the $devel-proposed (that should be future
> > proof) serves a completely different purpose than -proposed post-release.
> > Once
> > Saucy is released, saucy-proposed will serve the same purpose -proposed
> > has
> > always served. "Not for humans" only applies to the development phase.
> It looks like the two different uses of -proposed should be separated, no?
> So a $devel release would have an always empty $devel-proposed and all that
> is currently pushed there would go to $devel-autobuilder-only-proposed or
> something and a released verison would continue as-is.
In theory, sure. In practice, it would take a lot of work to do that for very
ubuntu-devel mailing list
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel