I think you should choose to use either 5.3/1.6 branch or release-5.3.0 tag.

If you want to regularly build last development version, you could consider building Nuxeo DM package from http://hg.nuxeo.org/nuxeo/nuxeo-distribution#5.3. See README.txt explaining how to build the various distributions.
Thanks to Maven, you don't need to build yourself last nuxeo sources, they are automatically downloaded from http://maven.nuxeo.org/ (http://maven.nuxeo.org/nexus/content/repositories/nuxeo-snapshot/).

FYI, here's a summary of our versioning policy and release process.
    Branch 5.3 is main development branch. Today, on this branch, artifacts are versioned 5.3.1-SNAPSHOT/1.6.1-SNAPSHOT.
    Branch 5.3.0 is maintenance branch for all existing (and future) 5.3.0.x versions. Artifacts are versioned 5.3.0.1-SNAPSHOT/1.6.0.1-SNAPSHOT (or 5.3.0/1.6.0 if not changed since last release).
    Tag release-5.3.0 is the source code of last Nuxeo release version 5.3.0. Artifacts are versioned 5.3.0/1.6.0.
    Next major version will be released from a new branch 5.3.1 (pulled from branch 5.3) and tagged as "release-5.3.1".
See "Nuxeo versioning policy" on http://doc.nuxeo.org/xwiki/bin/view/FAQ/DownloadingNuxeoSources for more details.

Cheers,

Robert P. J. Day a écrit :
On Tue, 10 Nov 2009, Stefane Fermigier wrote:

  
Hi,

Due to some (current, hopefuly) limitation in Mercurial, you have to
do the following:

1. Checkout the root project.

$ hg clone -r 5.3.0 http://hg.nuxeo.org/nuxeo

2. Edit the clone.sh (that's clone.bat on Windows) script, changing
all occurrences of "5.3" to "5.3.0" and "1.6" to "1.6.0".

3. Run clone.sh.
    

  so revision 5.3.0 represents the current *development* branch, does
it?  ok, i'll give it a shot and report back.

rday

p.s.  just to be clear, here's what i'm trying to do.  i can download
and install the nuxeo DM 5.3 zip file, but that of course represents
the latest *stable* release.  what i'd like to be able to do is
replace that install with an hg-updatable checkout so i can track the
ongoing commits and test the development branch instead.  and, for
convenience, i'd like to be able to do that without needing to check
out unrelated components -- just the DM stuff.

is that what the above represents?

--

========================================================================
Robert P. J. Day                               Waterloo, Ontario, CANADA

            Linux Consulting, Training and Kernel Pedantry.

Web page:                                          http://crashcourse.ca
Twitter:                                       http://twitter.com/rpjday
========================================================================
_______________________________________________
ECM mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm
To unsubscribe, go to http://lists.nuxeo.com/mailman/options/ecm
  

-- 
Julien Carsique, Nuxeo (Paris, France)
www.nuxeo.com - The Open Source ECM Platform - www.nuxeo.org
Nuxeo ECM Stack - The Java EE, scalable, standard-based ECM Platform
[email protected] | Tel: +33 1 40 33 79 87
_______________________________________________
ECM mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm
To unsubscribe, go to http://lists.nuxeo.com/mailman/options/ecm

Reply via email to