Hi, On Thu, May 7, 2015 at 12:31 AM, Stian Soiland-Reyes <[email protected]> wrote: > > Looks much simpler :) Thinking ahead for Commons it should make it > easier for $anyone to do the release as well. >
Indeed, that simplifies much more the process. There are still some small details to have it completely automated. Some things from commons-parent make it harder. Buty we are close to have it in the state that anybody would just need: mvn release:clean mvn release:prepare mvn release:perform >> I guess you would bump master to be on 0.1.1-SNAPSHOT afterwards, or > >> are you setting them to 0.2-SNAPSHOT and 0.2.0-SNAPSHOT? > > I'd prefer to focus on the api evolution, so master will be > 0.2.0-SNAPSHOT, > > while I plan to keep a maintenance branch for 0.1.x. But I happy to > listen > > opinions about this. > > On consideration, after this particular release I think I agree that > we are aiming for 0.2.0, as we will try to lock down things like the > hashCode definitions (COMMONSRDF-14) and verify that in the tests - > which can't really be said to be a patch release even though > signature-wise the commons-rdf-api could be just the same -- so > leaving it as 0.2.0-incubating-SNAPSHOT after the release is probably > fine. Sorry for bringing this up! > I had to think the same question, and I could be wrong, but I think we all here agree the api is the priority of the project. > I am not sure if we would be able to set a general rule for what the > SNAPSHOT version should be after a release -- perhaps when we feel > stable the rule would be that "master" would be set for a patch update > (e.g. ) - which could be revised (e.g. to > 0.9.0-SNAPSHOT) if a later change forces a new minor version (for > example a new method, or a change of the javadoc contract). > Keeping the api as priority, maybe we can have the rule that master will always contain X.Y.0-SNAPSHOT version. After all X.Y.Z are maintenance versions we can keep on their on branch. But I think we should discuss that aspect. That for bring it in, Stian. Cheers, -- Sergio Fernández Partner Technology Manager Redlink GmbH m: +43 6602747925 e: [email protected] w: http://redlink.co
