On 11 July 2013 08:43, Scott Kitterman <ubuntu@kitterman.com> wrote:
--
Best regards,
Aigars Mahinovs mailto:aigarius@debian.org
#--------------------------------------------------------------#
| .''`. Debian GNU/Linux (http://www.debian.org) |
| : :' : Latvian Open Source Assoc. (http://www.laka.lv) |
| `. `' Linux Administration and Free Software Consulting |
| `- (http://www.aiteki.com) |
#--------------------------------------------------------------#
I know it can be confusing, but the $devel-proposed (that should be future> 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...
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.
Best regards,
Aigars Mahinovs mailto:aigarius@debian.org
#--------------------------------------------------------------#
| .''`. Debian GNU/Linux (http://www.debian.org) |
| : :' : Latvian Open Source Assoc. (http://www.laka.lv) |
| `. `' Linux Administration and Free Software Consulting |
| `- (http://www.aiteki.com) |
#--------------------------------------------------------------#