Hi All,

I've finally looked at all the code changes from all the various people.
Here's the plan for getting past this merge impasse:

SHORT TERM
----------

1) Carlos please merge the glist_dev branch to CVS HEAD.  

   Lots of testing will happen after this and we should fix any release
   critical issues as soon as possible.

2) Ales will cut a release at this point.  Not having "Move and rotate"
   functionality that is technically perfect is no reason to hold up
   the above merge.  I want to get all the new functionality out in the
   field sooner than later.

3) PeterC, after Carlos is done, please create a branch for your noscreen
   changes. 

4) Patrick, after Carlos is done please create a branch
   for just the improved "move and rotate" functionality.  It's okay
   if there are a few support functions/files that also have to change,
   just as long as the work is geared to improving the "move and rotate"
   functionality.

Only after all the above branches are in back on HEAD will I consider
the next set of major refactoring patches.  Anybody object?  

All the major patch sets I looked at are quite good (lots of good
changes), however, we need break things down into smaller chunks
that address one change/feature at a time. 

LONG TERM
---------

Interestingly enough, this is the first time gEDA/gaf development has
faced such an impasse.  This is a good sign that the project is starting
to grow up.

I haven't fully formalized what I'm going to do to address the problem of
3+ people wanting to apply large patch sets.  It is clear that gEDA/gaf
will need to start relying on branching and merging much more, which is
something CVS just isn't very good at.  

More on this later, after we get pass the current impasse.  

                                                                -Ales




_______________________________________________
geda-dev mailing list
[email protected]
http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev

Reply via email to