Alastair McKinstry wrote:
The question is: how do you release a SCC arch, if at all?
AFAIK, the terminology is FCC/SCC for mirror split, and "release-arch" and "non-release-arch" for which arches get released as stable. So the question is "how do you release a non-release arch?"
Once you get over giggling at the phrasing (or maybe that's just me), there're a few answers. The ones that come to my mind are:
(a) Just build against testing/stable instead of unstable; when etch happens, fix up any remaining problems, and release a snapshot that more or less matches etch. Rinse, repeat.
(b) Just build against unstable, until you get bored. Then stop, clean up some stuff and do some basic testing, then release a snapshot.
(c) Something elseNote that it's the porters who'll have to make that call. If you do it well, your port could even end up better supported than i386.
Exactly how "fixing some stuff" before a snapshot will work isn't clear and will have to be worked out -- my guess is we'll probably have to set things up so you can upload to "snapshot-s390" instead of unstable or so for a few weeks.
There would be version skew; will Security releases be available?
If the porting team provides them. Cheers, aj