On Mon, 2 Dec 2013, Stephan Kulow wrote:
On 02.12.2013 11:39, Richard Biener wrote:
With the Debian 'testing' distribution
approach you scale QA by
making people using 'unstable' (aka Factory) do testing and file
bugs which blocks packages from migrating from 'unstable' to
'testing' unless they are fixed. So to throw in another name
(than the appearantly misleading Tumbleweed), 'testing' is a
rolling release for 'unstable'. Do we want a rolling-released-Factory?
Our testing are devel projects. I bet some use devel:gcc to test
gcc and report bugs before you send it to Factory. But not enough.
Probably. I thought of devel projects as 'experimental', because
the devel projects are where development happens, not where
candidates for Factory reside, no? Which immediately makes me
think that we can automate this by immediately accepting submitrequests
to Factory into a single Factory:staging project (without "review").
Or that it would make sense to provide an aggregate of all devel
projects to be able to easily test the future distribution status?
[for example Base:build is more like QA for devel projects as it
links to devel project sources rather than factory]
Debian unstable's user base might justify such a
split - taking that
debian stable is really not for developers from what I've been told.
That's true - even the just released stable has a very old subversion
version ... stable is really stable, after all ;) They'd better
call it "mature".
Richard Biener <rguenther(a)suse.de>
SUSE / SUSE Labs
SUSE LINUX Products GmbH - Nuernberg - AG Nuernberg - HRB 16746
GF: Jeff Hawn, Jennifer Guild, Felix Imend"orffer
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org