nap a écrit : > For each big feature, we can increment the version (0.4.1, 0.4.2, > etc). So it will be easier for testers to know which version they got :) I think this is not a good idea. For a lot of people, changing the revision version means only security fixes and bugfixes -> small changes. Bigger changes is related to major or minor. (see http://semver.org/) If you really have a new big feature, change to 0.5 or 0.6, ... And "Release early, release often" :)
Aurélien ------------------------------------------------------------------------------ Oracle to DB2 Conversion Guide: Learn learn about native support for PL/SQL, new data types, scalar functions, improved concurrency, built-in packages, OCI, SQL*Plus, data movement tools, best practices and more. http://p.sf.net/sfu/oracle-sfdev2dev _______________________________________________ Shinken-devel mailing list Shinken-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/shinken-devel
