Most projects branch the code when changing major releases. I would like to be able to pull the 1.4 branch from CVS.
Yes, I could just take the 1.4 source tarball, but that doesn't work if we (someone) wants to produce (and distribute) a new release of an old version. Some people cannot switch to version 2.0 for a variety of releases, so they are stuck using 1.4. By not branching the 1.4.8 code, it is much more difficult to produce a 1.4.9 version (if desired), that might contain the user contributed patches to the version, or critical bug fixes. You could review the Apache projects to see how this works (and how useful it is). Every major open-source project I've worked with uses CVS branches - except iText :) Robert ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ iText-questions mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/itext-questions Buy the iText book: http://itext.ugent.be/itext-in-action/
