On 29/09/10 09:52, Martin Hejl wrote: > But either way - I didn't mean to start a "which versioning system > should we use" discussion, especially since it doesn't matter to the > problem at hand - no matter which versioning system is used, the source > tarballs still need to be uploaded into the File Release System. > > Martin > > Sorry, I wrongly understand you.
In any way, IMHO it'll be good to switch to one of more modern versioning system. CVS has some limitations that affects project development process - for ex., if we will use git or mercurial (about SVN - I don't sure because I didn't use it at all), we can mark commits that corresponds to each our release - so in buildenv config developer can specify for any version he wants to build some package (new or updated) and in same time we can continue project development for pre-release branch without breaking something. So I think that it'll be good if we will discuss about versioning system update (which system will be more preferred to this project) - so more opinions from members will be better than closed discussion of active developers/committers. ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
