Please excuse my little German moment here
:-)
I would like to put up some guidelines on how to deal
with the code for discussion:
1. We should stay
on the public store. Again if anyone has objections, please tell
us now.
2. Since we are
several people working on the same code now, I would propose the
following:
a) Everybody opens
a branch for his/her code starting with the lastest version (1.33,
sames).
b) Each
branch could be distinguished by the initials and a private version number like
"1.33 CH 1.0" for mine or "1.33 MM 1.0"
for Maartens etc.
c) Every publish
should be all the way up to the top bundles to make sure everybody can
load the branch
consistently
d) To keep the
spirit of Sames, all modifications should have tests
e) After a while
when some work reaches a stable state, the work should selectively be integrated in order to create a new version
of the main stream. This would be the starting point again for contributers who
would have to move their unintegrated code to his/her new branch of that new
version.
IMHO there should
be only one integrator who has the reponsibility
- to select
the fitting parts (this could be prepared collectively in some discussions
with the final decision resting with the
integrator)
- to make sure that
all tests pass.
But since we have
not even published any code
yet, an integrator decision
can be left open for a while.
Sorry for being a
German (we love regulations :-), but I
think that such guidelines would help our
coordination.
Would this be ok with everybody or do you have other
ideas on how to organize this?
I think we should
wait if there are any objections to being on the public store for, lets say, 3
days - till Monday evening.
If we can go ahead,
I'd say we can start working on the code from Tuesday on.
Cheers and have a nice weekend,
Christian
Locked
