Hi, Le 07/05/2010 22:15, Antoine Toulme a écrit :
1. I think we should encourage people to have their own policy for version naming. Most of the time using the incremental approach is fine, but for releasing, they may want to pass a promoting version fragment
2. We should not split on -, only replace -SNAPSHOT.
Okay, I'll file a bug report for this one.
I don't think we should jump rc1 to rc2 right away.
I think buildr should ask the next version : it doesn't have to (and can't) guess the next release name. Sometines, it will be x.y.z-rc2, sometimes it will be x.y.z : buildr can't know the client validited it in his environment and that we decided to make a final release "production ready".
-- Jean-Philippe Caruana ******************************** 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.. ********************************
