I would set the version explicitly in the Buildfile, commit, do buildr release, etc. I might be missing something, I'm not too familiar with RCs in Buildr.
On Fri, May 7, 2010 at 03:11, Jean-Philippe Caruana < jeanphilippe1.caru...@orange-ftgroup.com> wrote: > Le 07/05/2010 12:08, jeanphilippe1.caru...@orange-ftgroup.com a écrit : > > So, for the next version, let's call it 2.0.0, we will do several -rc >> versions : 2.0.0-rc1, 2.0.0-rc2, 2.0.0-rc3 etc... and then the final >> 2.0.0 version. >> > > To be more precise, rc version go to integration environment and we need it > to be put in our public maven repo. Then, we do the production version (goes > to acceptance then prod environments) > > -- > Jean-Philippe Caruana - jeanphilippe.caru...@orange-ftgroup.com > Tel : 01 53 90 85 33 / 1533 - Projet AVSP > > ******************************** > Ce message et toutes les pieces jointes (ci-apres le "message") sont > confidentiels et etablis a l'attention exclusive de ses destinataires. > Toute utilisation ou diffusion non autorisee est interdite. > Tout message electronique est susceptible d'alteration. Multimedia Business > Services decline > toute responsabilite au titre de ce message s'il a ete altere, deforme > ou falsifie. > Si vous n'etes pas destinataire de ce message, merci de le detruire > immediatement et d'avertir l'expediteur. > ********************************* > This message and any attachments (the "message") are confidential and > intended solely for the addressees. Any unauthorised use or > dissemination is prohibited. > Messages are susceptible to alteration. Multimedia Business Services shall > not be liable for the > message if altered, changed or falsified. > If you are not the intended addressee of this message, please cancel it > immediately and inform the sender.. > ******************************** >
