[Vtigercrm-developers] Release naming

[Jeff Kowalczyk]

Callum Macdonald wrote:
> I think the naming of releases should be simplified. vtiger 5 patch 2
> and vtiger 5.0.2 are confusing names. It is not clear from what version
> you can apply patch 2, and so on. I suggest we use the same method as
> Joomla. When a new version is released (5.0.2) then the following files
> are released:
>
> I also think these files should all be released in the same package in
> sourceforge. In my opinion, splitting the full and patch releases is
> confusing.

Just an opinion, but I don't think vtigercrm should concern itself with
(or release) anything except pure-source, verbatim-to-the-svn-tag tar.gz
and .zip releases.

http://vtiger.fosslabs.com/cgi-bin/trac.cgi/wiki/ReleaseNaming
http://vtiger.fosslabs.com/cgi-bin/trac.cgi/wiki/ReleaseProcedure

Binary installers, patch-overlay releases, these are all the things
that third-party packagers do according to their own standards. We don't
want those problems. Packagers have the expertise and the ultimate
responsibility to do final-installation correctly for their security
strategy. What they need from the vtigercrm team is a rock-solid tarball
with a predictable layout, at a predictable unique URL, happening the same
way with every major, minor and bugfix release.

vtigercrm releases should be tailored for a primary consumer audience of
system packagers, and a secondary audience of expert manual install
aficionados who are willing to obsessively merge the unpacked source tree
to their own customized installation, and additionally set file
permissions, etc, according to a well-documented INSTALL.txt.