On Wed, Sep 22, 1999 at 08:06:13AM +0200, Lars Gullik Bjønnes wrote:
> "Asger K. Alstrup Nielsen" <[EMAIL PROTECTED]> writes:
>
> I am also not quite sure how to put this into cvs. Should it just be a
> continuation of lyx-1_0_x or should we create a new lyx-devel module.
> Or should we rename the old lyx module to lyx-devel-old and put this
> new 1.1.x series in as lyx.
It shouldn't be a continuation of lyx-1_0_x, because
- it's going to be called 1.1
- even with the more incremental development model, it will be a while before
the 1.1 module is ready. Meanwhile, if you release 1.0.4 and a bug is
found, what do you do? You *could* do this with branches, but it seems that
there will be a big enough shift from 1.0 to 1.1 that it's worth a new name.
Within the lyx-1_1_x (or lyx-devel or whatever), you could have several
branches for the different (teams of?) developers working on different
pieces, if that would help development.
Would it be possible to make the lyx_old somehow into a branch of lyx_new?
That way you could maybe just use cvs merge functionality to make some of
the changes? (Or at least cvs diff functionality to see what to change.)
> No matter what we do we will not ba able to have a complete log in
> cvs. (too much file and dir shuffling)
Admittedly. There's probably a logical place to put a description of these
changes, however.
-Amir
