On Sun, Apr 26, 2009 at 2:14 AM, Raffael Herzog <her...@raffael.ch> wrote: > Am Freitag, 24. April 2009 15.53:11 schrieb Johan Lindquist: >> I see that a release are tagged, but i see no suggestion of a place >> where could continue with maintenance work. What do you suggest for >> this? > > The easiest thing to do is to just copy e.g. /qa/project-1.0 to > /qa/project-1.0.1 and fix the bug there. The downside is that directories > in /qa may not be strictly read-only, which may be confusing. > > What about /maintenance? Copy /qa/project-1.0 to /maintenance/project-1.0, > fix the bug, copy that to /qa/project-1.0.1.
The original idea was that projects/products will have a pom tagged to /qa, and 'others' can take the /qa, copy it somewhere and do a release to releases/ after it has been verified. So, perhaps you /maintenance is a good idea, and that the /maintenance 'branch' is killed after the release, to lessen the confusion of where things "are alive" and evolving. (For the record, the /qa is writeable by release managers.) Cheers -- Niclas Hedhman, Software Developer http://www.qi4j.org - New Energy for Java I live here; http://tinyurl.com/2qq9er I work here; http://tinyurl.com/2ymelc I relax here; http://tinyurl.com/2cgsug _______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
