Hi, Dr. Peter Poeml wrote:
On Tue, Mar 11, 2008 at 03:22:23 +0100, Adrian Schröter wrote:
How about releasing a new build package once in a while? Right now, build.rpm in openSUSE:Tools was last updated in September last year. So I assume most people still use that old version.
openSUSE:Tools is intended to be kept stable. However we could create new versions for testing in openSUSE:Tools:Unstable first and later merging back.
bye adrian
A lag of half a year sounds like a bit of a too strong safety belt to me.
There is no "openSUSE:Tools:Unstable" that I can see either. (It's sheer existence wouldn't actually mean that anyone tests it anyway.)
I propose to surface changes much earlier, release early and often, you know, to keep breakage small and revertible.
We can also test the svn version, I suppose, can't we?
I do that regularily with a "larger setup" and also some big projects mirrored from build.o.o, and testing this also :-) I build and install: - osc - build - obs-server - rails 2.0 stuff completly from svn trunc, from one source code version. I currently use -r 3408 (that was when abauer fixed the errors with https://bugzilla.novell.com/show_bug.cgi?id=366405) I intend to update to current revision, especially after the new build features and the osc merge. I had already asked to put a copy into openSUSE:Tools:Unstable, but have no permission, to get openSUSE:Tools:Unstable lets say every week or so, or when some new features are to be tested. Where should the rails 2.0 copy (e.g. from darix) go? Also into openSUSE:Tools:Unstable? Cheers, Martin --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org