Version control practices: branching, merging, releases

[Barry Hawkins]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Michael Koch wrote:
[...]
| While the above is true this practice is at least uncommon for Debian
| packages. In Debian world a package normally depends on an older one.
| Several branches of a Debian package are not really supported by
| dpkg/apt-get.
[...]
The branches would not be used to provide multiple package version
simultaneously, but rather to allow flexibility in our approach to
maintaining them.  For example, branches of release versions of packages
could be in their own branch so that only applying security fixes could
be done in a well-insulated manner.  Experimental branches, say,
attempts to mograte to CDBS from debhelper (or back to debhelper from
CDBS ;-) ) could be done in a branch, and if works well, subsequently
merge it into the mainline.  These are just some examples.

| Branching and merging is possible CVS, Subversion, arch, monotone and
| others. We don't really need this feature but if we want we can with all
| of them. There is no need to switch to another system just becuase its
| not supported in CVS.
[...]
Yes, my wording may have miscommunicated that I was implying that
Subversion would allow us to branch, but that was not what I meant.  I
currently use branching quite effectively in CVS.  Subversion branching
and renaming are certainly easier than in CVS, but this functionality is
common to all worthwhile version control systems.
|
| I'm not against subversions. I really like it for some stuff where its
| superior to CVS. We just need to balance the efforts with the gains we
| will have.
[...]
Agreed.  Good discussion; thanks for weighing in.

Regards,
- --
Barry Hawkins
All Things Computed
site: www.alltc.com
weblog: www.yepthatsme.com

Registered Linux User #368650
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)

iD8DBQFCOYXS7bZ6kUftWZwRAjLlAJ9uVIqLGHca687q4/Z6asFsB6l23wCeMnQC
jBQXNCoCyPuOP59jXetWtcE=
=Tvyc
-----END PGP SIGNATURE-----