Re: HAMM FREEZE IS ONE WEEK AWAY
> > We can always remove the other architectures from Hamm if they are not
> > ready for release just yet. However, remember that "multi-arch" was
> > a 2.0 release goal.
>
> Actually, I would love just a bit more time after a code freeze. I think
> we could resolve 75% of the problems within a few weeks, but at the rate
> the x86 maintainers were releasing packages, we couldn't make headway at
> all and always had to play catch-up just to keep our heads above water.
I don't mind letting packages that already exist for one architecture
being admitted into another architecture if it was automatically
compiled. Since it was obviously approved for one, there is no reason
why it shouldn't be approved for another.
Guy, is there any way "dinstall" could detect this? If not, I'll just
have to do it by hand like all the other packages destined for "frozen".
> How much time before "release date" and the freeze would we have? Also,
> would 100% of the packages need to be ported, or just the required and
> standard stuff (optional is third priority to me at least).
I think we can swing 2-3 weeks for these such uploads.
Brian
( bcwhite@verisim.com )
-------------------------------------------------------------------------------
In theory, theory and practice are the same. In practice, they're not.
--
E-mail the word "unsubscribe" to debian-devel-request@lists.debian.org
TO UNSUBSCRIBE FROM THIS MAILING LIST. Trouble? E-mail to listmaster@debian.org .
Reply to: