Re: Moving tickets out of 4.0 post freeze
I have used the 4.0 version as a "we need this before releasing 4.0" - do
you have another way of marking tickets we need fixed before releasing?
On Mon, Sep 24, 2018 at 2:09 PM Joshua McKenzie <jmckenzie@xxxxxxxxxx>
> We have quite a few tickets still flagged for 4.0 that aren't in keeping
> with the idea that the code is frozen:
> I propose we move all new features and improvements to 4.0.x to keep the
> surface area of change for the major stable.