Hi @dev!
There has been a lengthly discussion about
how to improve the stability (actually: reliability)
of the TSVN releases.
Lübbe made a good point finding an average
of 1 out of 3 release being broken. Even though
that number improved over time, we do have
an issue here since a broken release implies
a lot of extra work:
* discuss the issue on the @dev list
* make a whole new release
My proposal:
* build releases as we do today
* release them on SF in an "RC" package
containing all installables for all platforms
(no need to have multiple RC packages,
imho, since early adopters should be able
to pick the right ones)
* announce the RC and encourage users
to test it
* if it fails, build another release
* after 2 weeks, move the installables to their
respective SF package and bump the version
file used to check for newer versions
* announce release
Basically, this is what we are doing today but
with tagging the packages as "untested" for
some time. We are trading a minor management
overhead against reduced @dev traffic (hopefully).
Comments?
-- Stefan^2
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Sun Jun 18 17:03:06 2006