On Wed, Aug 27, 2008 at 12:39:46PM +0200, Carsten Möller wrote: > Florian Lohoff schrieb: > > On Wed, Aug 27, 2008 at 10:56:19AM +0200, Michael Bergbauer wrote: > >> as there are lots of changes to the [EMAIL PROTECTED] clients recently and > >> also some > >> changes that don't work quite well in the first place, would it probably > >> be possible/useful, to have the autoupdate feature of [EMAIL PROTECTED] > >> checking out a > >> designed 'stable' version from SVN insteast of the latest, with > >> potentially lots of bugs in it? > >> > >> And in order to avoid not testing new code, perhaps have it a > >> configuration option to check out stable or latest. > > > > I second that - I'd like to see a "stable" or "production" branch on > > svn which is automatically followed by clients in default - Why not have > > the branch to follow in the config. People can try and break things on > > HEAD and once the dust has settled merge the changed to production for > > clients to check. > > Even for us "small" users this is very frustating. So the newly > discussion about setting up a maintenance(release)/branch is necessary. > A few days ago I suggested exactly the same, but got only negative response.
If I've understood you correctly you want to setup a stable branch where no commits go in before they have been tested by several people. This kind of setup is more pain than it's worth because most changes are small, simple and everyone is fairly sure it's going to work. What we have recently had is a very big cleanup and reorganization of code going on in trunk, what I'd rather see is for these kind of changes to be done in a separate branch. There is a small but important difference between these setups, in that only changes that we think might cause trouble are tested in this way. If you want a super-stable branch with loads of testing then go right ahead, it's not hard to get svn access, but don't expect every developer to use loads of time and energy getting the code he's written into some stable branch. -- Knut Arne Bjørndal aka Bob Kåre [EMAIL PROTECTED] [EMAIL PROTECTED]
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Tilesathome mailing list [email protected] http://lists.openstreetmap.org/listinfo/tilesathome
