The release will most likely be done from the master branch. The only other one is for olap4j 2. 

About the maven-release-plugin. We can use the maven-release-plugin for olap4j-xmlaserver. That would be much simpler than my usual manually-deploy-and-test procedure. As for the core olap4j code, I'd rather we wait until olap4j 2 before making changes to the build system (it is currently based on subfloor/ant). The code is not nicely split into proper modules. If we migrate to maven, we should split the core API from the XMLA driver and the experimental packages. Making these changes now seems like overkill, and quite frankly, I don't think anyone has the bandwidth to do it right now.

I'm also expecting a late-coming contribution from one of the teams at Pentaho. I'd very much like to have it part of the release. I can't really spoil the beans, but it is something extremely nice to add, and I wouldn't want to play musical chairs with source files while these guys are working on their stuff.

I'll keep this list posted.

Luc


On Tue, Jan 21, 2014 at 2:19 PM, Julian Hyde <jhyde@pentaho.com> wrote:
Sounds like a good idea. Which branch (or commit SHA) do you intend to make the release from?

I'd like to "modernize" the process before you release. First, I'd like to use maven-release-plugin. Second, github projects tend to have a reverse-ordered file of release notes & release history (https://github.com/julianhyde/linq4j/blob/master/HISTORY.md is an example), so I'd like to add that.

Julian