RE: [Koha-devel] change management
If you want an example of a project that is successfully using HSM, look at the linux kernel. That uses BitKeeper as its change-management software. Note that Linus hates CVS with a vengeance (or at least, if he doesn't hate it, he's very vocal about it being useless). CVS is far more oriented to a CRM approach. With BitKeeper, Linus controls the 2.5 master tree, Alan Cox is currently looking after a tree that's trying to fix IDE problems, Andrea and (forgotten his name) are looking after the VM, etc etc. And as Linus looks to deal with each area in turn, he looks at his lieutenant's tree and pulls the relevant fixes across into mainline. So if there are clear lines of responsibility, with different people responsible for different bits of Koha, it's probable that HSM and BitKeeper will turn out to be the easiest way to manage things. Cheers, Wol -----Original Message----- From: Pat Eyler [mailto:pate@eylerfamily.org] Sent: 07 February 2003 17:09 To: Andrew Arensburger Cc: koha-devel@lists.sourceforge.net Subject: Re: [Koha-devel] change management On Fri, 7 Feb 2003, Andrew Arensburger wrote:
On Fri, Feb 07, 2003 at 11:45:16AM -0500, Pat Eyler wrote:
I am not proposing that we move to something this detailed, but it make an interesting read. How can/should we manage the development of Koha after 2.0.X?
Did I miss something, or was there supposed to be a URL or news article?
Doh! Sometimes I hate mornings. The URL is: http://gcc.gnu.org/ml/gcc/2003-02/msg00313.html
Please forgive me if I'm being dense.
-- Andrew Arensburger This message *does* represent the arensb@ooblick.com views of ooblick.com Inside every short man is a tall man doubled over in pain.
------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Koha-devel mailing list Koha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/koha-devel This transmission is intended for the named recipient only. It may contain private and confidential information. If this has come to you in error you must not act on anything disclosed in it, nor must you copy it, modify it, disseminate it in any way, or show it to anyone. Please e-mail the sender to inform us of the transmission error or telephone ECA International immediately and delete the e-mail from your information system. Telephone numbers for ECA International offices are: Sydney +61 (0)2 9911 7799, Hong Kong + 852 2121 2388, London +44 (0)20 7351 5000 and New York +1 212 582 2333.
On Wed, Feb 12, 2003 at 12:01:00PM -0000, Anthony W. Youngman said:
If you want an example of a project that is successfully using HSM, look at the linux kernel. That uses BitKeeper as its change-management software. Note that Linus hates CVS with a vengeance (or at least, if he doesn't hate it, he's very vocal about it being useless). CVS is far more oriented to a CRM approach.
With BitKeeper, Linus controls the 2.5 master tree, Alan Cox is currently looking after a tree that's trying to fix IDE problems, Andrea and (forgotten his name) are looking after the VM, etc etc. And as Linus looks to deal with each area in turn, he looks at his lieutenant's tree and pulls the relevant fixes across into mainline.
So if there are clear lines of responsibility, with different people responsible for different bits of Koha, it's probable that HSM and BitKeeper will turn out to be the easiest way to manage things.
Hi there Bitkeeper certainly looks like a neat tool, I just have issues with its license :-) Im hoping subversion gets finished soon :) Chris -- Chris Cormack Programmer 025 500 789 Katipo Communications Ltd chris@katipo.co.nz www.katipo.co.nz
participants (2)
-
Anthony W. Youngman -
Chris Cormack