-zefram
Looks like nobody replied to this, but if it's simply a question of
committing new versions when they turn up, or adding patches, I could do it.
I'm going to be keeping the FAQ up to date there anyway. I'll have to
refresh my CVS knowledge.
--
Peter Stephenson <p...@ifh.de> Tel: +39 50 844536
WWW: http://www.ifh.de/~pws/
Gruppo Teorico, Dipartimento di Fisica
Piazza Torricelli 2, 56100 Pisa, Italy
I would think that the purpose of the CVS repository would be to be to
store the authentic source as it would appear in the next release.
This would requite that the coordinator keeps it in sync with his
repository. Unless Zefram does this himself, how can you be sure that
a patch you check in would show up unmodified in the release?
A centralized CVS master site would also allow multiple `maintainers'
who can directly check in changes they make, but this would be a quite
different development model than the current one.
Zoli
Not necessarily. I've already explained this at least once: a CVS
repository *could* be used for that, but it could also be used merely
to keep track of different versions and patches.
> Unless Zefram does this himself, how can you be sure that
>a patch you check in would show up unmodified in the release?
Obviously, if a repository is not the master source, then patches still
have to go via zsh-workers.
-zefram
> Looks like nobody replied to this, but if it's simply a question of
> committing new versions when they turn up, or adding patches, I could do it.
> I'm going to be keeping the FAQ up to date there anyway. I'll have to
> refresh my CVS knowledge.
Check out my Project Management with RCS and CVS slides -- part of a
series of "ToolsTalks" I gave to other PhD students:
http://www.cs.washington.edu/homes/gjb/ToolsTalks/Project-Management.html
Comments and criticisms are appreciated.
Greg