Quoting Richard Brown <RBrownCCB(a)opensuse.org>rg>:
On Mon, 2013-12-02 at 11:50 +0100, Stephan Kulow
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.
That is exactly how I prefer to operate when testing/maintaining GNOME
Using GNOME:Factory (the gnome devel repo) with Factory gives me a way
of testing all of the 'incoming' GNOME changes.
If something in our GNOME devel repo fouls up, I'm a simple 'zypper
removerepo' and 'zypper dup' away from getting my machine back to
'usable' so I can get working on figuring out what broke in GNOME
Just some food for thought here:
* if the goal is an always 'stable' Factory, I'm not sure at what time
we are now best to submit GNOME:Factory to openSUSE:Factory.
There are two conflicting approaches:
* Release Often / Release early (approach used so far)
* Release stable (new ?)
Stable indicates no GNOME 3.11.x, as those are 'expected' to have bugs
and introduce changes mid-way. So in order to satisfy the '2nd' entry,
I'd argue that no submits should be done until at least RC1 of GNOME
(in this case). This is different to what was done so far, where GNOME
Team made sure it 'works', but was a bit more 'lose' on accepting to
forward with minor issues here and there (knowing that Factory was dev
/ integration project and some minor instabilities were acceptable).
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org