Yeah - that looks right. On July 7, 2014 at 9:05:06 PM, Cameron McKenzie ([email protected]) wrote:
This is the expected diff between pom.xml and pom.xml.tag? [cam:~/Documents/workspace/curator] cam% diff pom.xml pom.xml.tag 31c31 < <version>2.5.1-SNAPSHOT</version> --- > <version>2.6.0</version> 105c105 < <tag>HEAD</tag> --- > <tag>apache-curator-2.6.0</tag> On Tue, Jul 8, 2014 at 11:31 AM, Jordan Zimmerman <[email protected]> wrote: Yes - marked it as fixed. On July 7, 2014 at 8:30:38 PM, Cameron McKenzie ([email protected]) wrote: Ok, final question (I hope) for now. Do I just close the CURATOR-116 JIRA ticket? On Tue, Jul 8, 2014 at 11:27 AM, Jordan Zimmerman <[email protected]> wrote: No - we’re using semantic versioning. There’s some API changes as I recall. Also, this release has the new Curator-RPC. It should be 2.6.0. -Jordan On July 7, 2014 at 7:53:30 PM, Cameron McKenzie ([email protected]) wrote: Once I've merged CURATOR-116, I'll do a release. I presume that this should be a 2.5.2? On Tue, Jul 8, 2014 at 7:56 AM, Jordan Zimmerman <[email protected]> wrote: Up to you. You might want to push CURATOR-116 first. Once you’re ready, follow the steps here (updating them if needed): https://cwiki.apache.org/confluence/display/CURATOR/For+Curator+Committers#ForCuratorCommitters-release-curator -Jordan On July 7, 2014 at 4:54:06 PM, Cameron McKenzie ([email protected]) wrote: Yep, I'm happy to do the release, just let me know when you'd like me to go forward. cheers On Tue, Jul 8, 2014 at 1:20 AM, Jordan Zimmerman <[email protected] > wrote: > Looks like we have enough issues closed for a 2.6.0 release. Thoughts? > Cameron, it would be good for you to do the next release if you don’t mind. > > > https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+CURATOR+AND+fixVersion+%3D+2.6.0+ORDER+BY+updated+DESC%2C+priority+DESC%2C+created+ASC&mode=hide > > -Jordan > >
