After 1.0, once we adopt semantic versioning, this will be natural. Lets say we release 1.1 and the trunk moved forward for 1.2 development. As we have bug fixes on the supported maintenance branch 1.1, first thing we should probably do is to make the branch 1.1.1-SNAPSHOT and as with trunk releases, when we decide to make a release cut a 1.1.1 and change the branch to 1.1.2-SNAPSHOT.
In the interim, I do not have any strong opinions how we approach it. Suresh On Sep 18, 2013, at 3:34 PM, Chathuri Wimalasena <[email protected]> wrote: > Hi All, > > For paramchem, we found a bug [1] in XBaya code. Xbaya jar is used by > paramboroo client. We have a separate branch for 0.8. We can commit the > changes in to that branch. But how can we make sure that paramboroo will get > the latest jar from the repo. What is the best way to maintain that ? > > There are several options : > • Update the version of 0.8 to some other version (0.81, 0.8_branch) > • Have a separate repo for the branch > What is the best approach we should use ? > > Regards, > Chathuri > > [1] https://issues.apache.org/jira/browse/AIRAVATA-920
