[kln2-devel] cvs policy

[Marek W. <Mar...@fu...>]

Fernando,

> About CVS, do you have any branching and/or check-in
> policy I should be aware of?

Actually everybody but me is new to the project. People started
working on things and there are already some commits, but there
is no clear CVS policy so far.

Please, commit only versions that compile (otherwise you would
disturb anyone who works on a separate task). Also errors in
administrative files (e.g. Makefiles) may lead to some
hard-to-predict problems, so I would rather be the only person
who commits changes to them.

Once these requirement is fulfilled - commit as often as
possible. Even if not everything is implemented or doesn't do
what it is supposed to do yet. This way
1. people can follow others work and adjust what they do;
2. if few people change the same file small changes are merged
   better.

Once you get an idea what you want to change, I suggest that you
share with others on kln2-devel (see my e-mail on key signatures
as an example). Especially, that your work will overlap a bit
with work of others (for example Jim is working on name-to-note
exercise which deals a lot with buttons).

~Marek

-- 

     \/   /|\  Marek Wieckowski
  #####  | | |
 = . . =  \|/  Institute of Theoretical Physics
    U      |   Warsaw University
  / ~ \___ |
 <|   |    |
  > . <    |   http://www.fuw.edu.pl/~wiecko
 <<___>>   |   http://klearnnotes2.sourceforge.net