Re: m68k not a release arch for etch; status in testing, future plans?
On Wed, Oct 18, 2006, Anthony Towns wrote:
> * have m68k be in unstable, and have it have its own "testing-like"
> suite of some description
> + keeps the arch alive
> - some work to keep m68k-testing in sync with real testing needed
> - doesn't have real releases
> - may not have security support
Is it possible to run britney multiple times, the first time for all
releasable arches, and the following runs for each other arch, but
commit changes to etch/$arch?
For example, this would permit releasing an etch/m68k without a
Perhaps the maintenance of the testing propagation of m68k alone should
then be made by m68k porters instead of the *release* team.
Loïc Minier <firstname.lastname@example.org>