Re: Time for another release?

I'll start the release process Fri 2017-01-27 00:00 UTC. After this time, please open feature branches for ongoing development until we have closed the vote for the the release artifacts. On Jan 24, 2017 11:57 PM, "Javen O'Neal" wrote: > We could also fork the trunk to a

Re: Time for another release?

We could also fork the trunk to a release branch when we want to make a release candidate so that development can continue on the trunk. There likely wouldn't be any changes to make on the branch, so we would end up copying the release branch to a tag and deleting the release branch. This would

Re: Time for another release?

On Wed, 25 Jan 2017, Greg Woolsey wrote: I have something I'm going to file an issue about tomorrow, but it could wait. Although having it in would help fix some bugs I'm working around with Vaadin Spreadsheet. It would be my first official commit, so I don't want to do it near a code freeze,

Re: Time for another release?

I have something I'm going to file an issue about tomorrow, but it could wait. Although having it in would help fix some bugs I'm working around with Vaadin Spreadsheet. It would be my first official commit, so I don't want to do it near a code freeze, just in case. It's a helper to expose the

Re: Time for another release?

I'll take this release, then. Are there any outstanding changes that should be committed before creating the the artifacts for 3.16 beta 2? On Jan 24, 2017 10:45, "Greg Woolsey" wrote: > I have a product release for my day job this week, best I sit this one out > :) > >

Re: Time for another release?

I have a product release for my day job this week, best I sit this one out :) On Tue, Jan 24, 2017 at 8:40 AM Javen O'Neal wrote: > Definitely go for a beta. Also want to check out how JCmpApi is doing to > find API breaks. > > Greg, do you want to be release manager for 3.16

Re: Time for another release?

Definitely go for a beta. Also want to check out how JCmpApi is doing to find API breaks. Greg, do you want to be release manager for 3.16 beta 2? If not, I can do it. On Jan 23, 2017 23:52, "Andreas Beeker" wrote: > I would go for another beta soon. > Who will be the

Re: Time for another release?

I would go for another beta soon. Who will be the release manager? Andi - To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org For additional commands, e-mail: dev-h...@poi.apache.org

Time for another release?

Hi All We seem to be about 2 months after our last beta release now, and about 4 months since our last final release. Is it worth doing another beta soon, to let people test possible breaking changes from some of the enum and deprecated stuff? Or hold off a bit longer, and just go for 3.16