+1
On Fri, Apr 22, 2016 at 11:37 PM, Jonathan Ellis wrote:
> +1
>
> On Fri, Apr 22, 2016 at 4:12 PM, Jake Luciani wrote:
>
> > I propose the following artifacts for release as 2.1.14.
> >
> > sha1: 209ebd380b641c4f065e9687186f546f8a50b242
> > Git:
> >
> >
> http://git-wip-us.apache.org/repos/as
+1
On Fri, Apr 22, 2016 at 11:37 PM, Jonathan Ellis wrote:
> +1
>
> On Fri, Apr 22, 2016 at 4:15 PM, Jake Luciani wrote:
>
> > I propose the following artifacts for release as 2.2.6.
> >
> > sha1: 37f63ecc5d3b36fc115fd7ae98e4fc1f4bc2d1d6
> > Git:
> >
> >
> http://git-wip-us.apache.org/repos/asf
The old "most stable" labeling was super-important in the old days since
newer releases tended to have a fair amount of instability - hence the
admonition to wait for a x.y.5 release before using the x.y release line.
But that dramatic degree of release instability is no longer the case.
Besides, w
