On mar., 2010-10-12 at 13:49 +0800, Paul Wise wrote: > On Tue, Oct 12, 2010 at 1:17 PM, Yves-Alexis Perez <corsac@debian.org> wrote: > > > Imho it's not a good idea to have the theme ready too soon, especially > > when we don't know when the release will be, and the theme might “wear > > out”. > > I thought about re-uploading the package every few months, changing > the theme, but that would be kinda silly. > > What about if the theme for testing/wheezy changed randomly on reboot > between candidates for the final wheezy theme? > > Or if the CUT proposals go ahead, each snapshot could contain a new > theme and before wheezy the final theme would be chosen. Wow, that would be a lot of themes/artwork. Not sure it could be done that often. > > > But we could proceed as Julien proposed, like, if we know the scheduled > > freeze date one year in advance, we could set a deadline like a month > > before. Though that means knowing the freeze one year in advance, which > > might not be that easy. > > I think one month is too short of a time, 6 months might be more appropriate. 6 months? I'm puzzled, what it is in a theme which would make it require 6 months to be chosen, uploaded to unstable and migrate to testing? Cheers, -- Yves-Alexis
Attachment:
signature.asc
Description: This is a digitally signed message part