Here my 2 cents to this topic. I think the whole problem currently arises form the fact the there is a change how releases are coming out (or better how they should come out ;-)
What most customer want (and can handle) is: * a development version where new functionality is going in * a current stable release Bugs found in the development release which are apparently also in the current stable release and considered as critical, should be backported to the stable release (---> this leads to bug-fix releases). This kind of organization implies the need of a person who decides: a) what is considered as critical bug b) is it possible to backport the bug-fix to the stable release (with possible i mean in terms of effort and how complicate the backport is - if it is too big there is the risk of introducing new bugs with the bug-fix) c) when is a bug-fix version released Currently i have the impression no one organizes this kind of releases management. It really does not matter if you define a bug-fix release 2.0.8-1, 2.0.8-2 etc. or if you do it like 2.0.9, 2.0.10, etc. The important is to define a schema and stick to it. Since the latest official release is 2.0.8 i would like to see bugfixe against this release and not a changeset against a development branch. damn, .... the email is longer than i wanted. Thx for the good work. On Wednesday 16 May 2007, Andrew Beekhof wrote: > On 5/16/07, Serge Dubrouski <[EMAIL PROTECTED]> wrote: > > On 5/16/07, Andrew Beekhof <[EMAIL PROTECTED]> wrote: > > > On 5/15/07, Serge Dubrouski <[EMAIL PROTECTED]> wrote: > > > > Andrew, you used to periodically update the stable Mercury repositary > > > > but it looks like you aren;t doing this anymore. Why? > > > > > > I assume you mean: > > > http://hg.linux-ha.org/heartbeat > > > > I meant http://hg.beekhof.net/lha/crm-stable. In the past it used to > > be updated regularly, though I don't know what was the main criteria > > to update that branch. > > ah that one. > not sure why I stopped updating that... but if people are indeed > finding it useful then i'm happy to start it up again. > > > > > > > > > Its not been updated because there has been no release to update it from. > > > > > > > Putting HB built > > > > from development version into production isn't an appropriate > > > > solution, > > > > > > What is a released version if not a development version thats passed > > > some testing hurdle? > > > > And testing is a key thing for production environment. You won't argue > > that it's not a good practice to put code submitted yesterday into > > production today, will you? > > Right, I'd not try to argue that. > What I was trying to say was that the version I made mention of > http://hg.linux-ha.org/dev/archive/SLE10-SP1.tar.bz2 > got that testing. > > > > > > The problem here, is that the version in > > > question was certified by SUSE for SLES users and there was no > > > corresponding official community release. > > > > > > What is available though, is binaries for fedora, debian as well as a > > > number of older SUSE platforms built from the same source at: > > > http://software.opensuse.org/download/server:/ha-clustering/ > > > > > > I've also been campaigning for the ability to build for other > > > archs+distro combinations, but this is a work in progress. > > > > > > > > > > using 2.0.8 as you siad isn;t a good way too and there is no > > > > current stable build anymore. > > > > > > go back and look at the first line of my initial response. > > > its not a situation i'm particularly happy about either but we hope to > > > have the situation rectified "soon". > > > > > > > > > > > On 5/15/07, Andrew Beekhof <[EMAIL PROTECTED]> wrote: > > > > > On 5/15/07, Benjamin Watine <[EMAIL PROTECTED]> wrote: > > > > > > Hi > > > > > > > > > > > > I'm about to install Heartbeat on a fresh Debian 4 system, and I was > > > > > > wondering wich version of heartbeat I should install ? > > > > > > Some bugs have been corrected since v2.0.8, and I would like to > > > > > > install > > > > > > these corrections too. So should I install v2.0.8 and apply the > > > > > > patches > > > > > > that I want, or install the latest development version ? > > > > > > > > > > > > If you think there's no major problem installing latest snapshot, > > > > > > where > > > > > > can I find it ? here ? : > > > > > > http://hg.linux-ha.org/dev/archive/tip.tar.bz2 > > > > > > Any other version to suggest ? > > > > > > > > > > A question with a rather unsatisfactory answer I'm afraid. > > > > > > > > > > I wouldn't recommend 2.0.8 - both due to its age and some rather > > > > > unpleasant bugs and memory leaks it contained. > > > > > > > > > > But I also wouldn't recommend the latest snapshot either as the lrmd > > > > > is in a rather sorry state. > > > > > > > > > > The link posted by Sam is probably the best bet for pre-built > > > > > packages. Otherwise, if one is comfortable with building from > > > > > scratch, I would use: > > > > > > > > > > http://hg.linux-ha.org/dev/archive/SLE10-SP1.tar.bz2 > > > > > > > > > > which is what will be going into SLES10, SP1 and was the subject of a > > > > > respectable amount of testing. > > > > > > > > > > > > > > > > > Thanks in advance. > > > > > > _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
