4.2.x branch

[Phil Sorber <so...@apache.org>]

Hello All,

I plan to fork 4.2.x some time early next week. Here is the list of issues
that are not resolved for 4.2.0:

https://issues.apache.org/jira/browse/TS-2533?jql=project%20%3D%20TS%20AND%20fixVersion%20%3D%20%224.2.0%22%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened%2C%20%22Patch%20Available%22)

If there is something that is important in there get it committed ASAP.
Talk to me if you have concerns about any of them making it in.

Remember folks, this is an LTS release, so it needs to be extra stable...

Thanks.

Re: 4.2.x branch

[Leif Hedstrom <zw...@apache.org>]

On Jan 27, 2014, at 11:06 AM, Phil Sorber <so...@apache.org> wrote:

> Hello All,
> 
> I plan to fork 4.2.x some time early next week. Here is the list of issues
> that are not resolved for 4.2.0:
> 
> https://issues.apache.org/jira/browse/TS-2533?jql=project%20%3D%20TS%20AND%20fixVersion%20%3D%20%224.2.0%22%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened%2C%20%22Patch%20Available%22)
> 
> If there is something that is important in there get it committed ASAP.
> Talk to me if you have concerns about any of them making it in.


Cool. I’ve (for now), reshuffled all open Jira’s as follows:

	5.0.0 -> 5.1.0
	4.2.0 -> 5.0.0


I’ve then moved a handful of Jiras back to either 5.0.0 or v4.2.0 as appropriate. I’d like to urge everyone to take a look at the open tickets for v5.0.0 - v5.2.0, and move those accordingly. But be aware that we are branching v4.2.0 soon, so unless a bug truly will be fixes in the next few days, don’t mark it for v4.2.0.

Cheers,

— Leif