Hi,
This may have been said before, if so, my apologies.
I've noticed that, each time, the stable+2 release name is chosen when
stable+1 is frozen.
I have, on one of my package (DTC-Xen), the feature to (de)bootstrap a
virtual machine. Because of this, the default Debian flavor is asked
through
On Tue, Oct 05, 2010 at 05:10:30PM +0800, Thomas Goirand wrote:
So, my request is quite simple. Could the name for the release after
Wheezy be chosen when Squeeze is release?
Nah. And it's not that likely that you could do something useful with it
anyway. (Given that we don't support skipping
Philipp Kern wrote:
On Tue, Oct 05, 2010 at 05:10:30PM +0800, Thomas Goirand wrote:
So, my request is quite simple. Could the name for the release after
Wheezy be chosen when Squeeze is release?
Nah. And it's not that likely that you could do something useful with it
anyway. (Given that
On Wed, 06 Oct 2010 00:09:06 +0800
Thomas Goirand z...@debian.org wrote:
Philipp Kern wrote:
On Tue, Oct 05, 2010 at 05:10:30PM +0800, Thomas Goirand wrote:
So, my request is quite simple. Could the name for the release after
Wheezy be chosen when Squeeze is release?
Nah. And it's
Neil Williams wrote:
Most of these packages go backwards in time, not forwards. We
can test that previous releases work with the tools - future releases
are likely to break stuff and you may well need new options or new
behaviour to work with future releases.
Certainly had this problem with
5 matches
Mail list logo