[
http://jira.nuxeo.org/browse/NXBT-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julien Carsique resolved NXBT-60.
---------------------------------
Resolution: Fixed
reopen this issue in case of naming changes, for now naming as described here
is fine.
> Build, version and package naming convention
> --------------------------------------------
>
> Key: NXBT-60
> URL: http://jira.nuxeo.org/browse/NXBT-60
> Project: Nuxeo ECM Build/Test Environment
> Issue Type: Improvement
> Components: Continuous integration, Distribution
> Reporter: Benoit Delbosc
> Assignee: Julien Carsique
>
> As there are more and more distributions, we need more consistency to name
> build and version. Here is a proposal inspired from the eclipse project.
> Nuxeo build types
> =====================
> * Integration Builds
> They are nightly builds that pass all integration tests. Integration
> builds may be promoted to stable builds after a few days of testing
> * Stable Builds
> Stable builds are integration builds that have been found to be stable
> enough for most developers to use. They are milestones or release
> candidates.
> * Releases
> Releases are builds that have been declared major releases, Releases are
> the right builds for people who want to be on a stable, tested release,
> and don't need the latest features and improvements.
> * Maintenance releases
> Maintenance builds are produced to incorporate fixes into an existing
> release.
> Nuxeo build versionning
> ========================
> * Integration Builds (5.1.7-I20090225_1730)
> The version used are target release (5.1.7 or 5.2.0), an 'I' for
> integration and a time stamp like 5.1.7-I20090225_1730, all the jar inside
> the package are also using this versions.
> * Stable Builds (5.1.7-RC2)
> Version are using a M for milestone or RC for release candidate
> ex: 5.1.7-M2 or 5.1.7-RC1.
> * Releases (5.1.7)
> Releases are builds that have been declared major releases, Releases are
> the right builds for people who want to be on a stable, tested release,
> and don't need the latest features and improvements.
> Version is 5.1.7 or 5.2.0 without any final or GA.
> * Maintenance releases (5.1.7.1)
> Maintenance builds are produced to incorporate fixes into an existing
> release, we just add a number to the release version: 5.1.7.2
> Nuxeo build distribution naming
> ==================================
> * projects:
> - Nuxeo EP: nuxeo-ep
> - Nuxeo Web Engine: nuxeo-we
> - Nuxeo shell: nuxeo-shell
> * versions (see above section)
> * web server
> - JBoss: jboss
> - Jetty: jetty
> - Glassfish: gf
> * arch
> - windows 32b: win32
> - windows 64b: win32-x86_64
> * package release number, a number that is incremented until expected stuff
> is packaged.
> * extension type:
> - windows: .exe
> - unix: .tar.gz
> - java: .jar
> - zip: .zip
> Exemples:
> * nuxeo-ep-5.2.0-jboss-1.zip
> * nuxeo-ep-5.2.0-M4-jboss-1.zip
> * nuxeo-we-5.2.0-I20090225_1200-jetty-1.zip
> * nuxeo-ep-5.2.0-I20090225_1200-jboss-win32-x86_64-1.exe
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.nuxeo.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
ECM-tickets mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm-tickets
