On Thu, 2016-01-28 at 09:53 -0800, Jon Grossart wrote:
Also, from the definition of Tumbleweed, it states it should be stable and tested software. An RC is by definition not that. It might be fine for them to roll into Factory for testing, but they probably shouldn't flow into TW until they are actually released.
There is no distinction between Factory and Tumbleweed to be made: what was called Factory 2 years ago is now called Tumbleweed (ok, it gained a lot of stability and automated testing in between, so it clearly is more stable than back in the days) at best, you can consider 'Factory' the thing before it's tested and released.. but you can't get it in an easy way... and it is released as one tested unit. No exception on any package can be made. So far, the decision if an RC is 'stable' or not has always been at the discretion of the maintainer. in case of LO, the fact that they call it 'RC' is more strategic - just like some other packages never get our of their beta: they do not want to 'promise' too much (look at wine: it takes months between 'stable' releases - hence Tumbleweed comes with the devel versions) Iw would argue, it stays on a case-by-case issue: if the maintainer feels it's stable and accepts getting smashed by bug reports if it's not: he can submit it. For users on the other hand that means: don't be afraid of reporting bugs! BUt not just that you do not like the version number chose by any random group (why LO calls their RC's as 5.1.0.3 when it's RC3 is beyond any logic anyway: 5.1.0 would logically be the release, and an added .3 makes it 'more recent and fixed') Dominique -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org