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 require changing the release scripts, but is a possibility as we
think about rewriting some of the release procedure in Gradle.

On Jan 24, 2017 22:07, "Nick Burch" <[email protected]> wrote:

> 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, just in case.  It's a helper to expose
>> the formula evaluation code more cleanly for evaluating formulas not tied
>> to a specific cell, like conditional formatting and data validation
>> expressions.
>>
>
> I'd suggest you create a branch of trunk, and commit to that. I'm happy to
> help review, especially the conditional formatting angle. Once we're all
> happy, and the release is done, merge away!
>
> Nick
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to