[Gluster-Maintainers] Stop sending patches for and merging patches on release-3.7

[Shyam]

On 02/01/2017 12:14 PM, Atin Mukherjee wrote:
>
> On Wed, 1 Feb 2017 at 17:06, Kaushal M <kshlmster at gmail.com
> <mailto:kshlmster at gmail.com>> wrote:
>
>     Hi all,
>
>     GlusterFS-3.7.20 is intended to be the final release for release-3.7.
>     3.7 enters EOL with the expected release of 3.10 in about 2 weeks.
>
>
> Am I missing any key points here? With 3.10 coming in, 3.9 goes EOL
> considering it is short term and then don't we need to maintain 3
> releases at a point? In that case 3.7 still needs to be active with 3.8
> & 3.10, no?

No, we maintain the last 2 LTMs, so in this case that is 3.8 and 3.10 
(when 3.10 releases).

Intermediate STMs are maintained for the 3 months till the next LTM 
comes along to replace it.

Reference: https://www.gluster.org/community/release-schedule/

>
>
>
>     Once 3.10 is released I'll be closing any open bugs on 3.7 and
>     abandoning any patches on review.
>
>     So as the subject says, developers please stop sending changes to
>     release-3.7, and maintainers please don't merge any more changes onto
>     release-3.7.
>
>     ~kaushal
>     _______________________________________________
>     maintainers mailing list
>     maintainers at gluster.org <mailto:maintainers at gluster.org>
>     http://lists.gluster.org/mailman/listinfo/maintainers
>
> --
> - Atin (atinm)
>
>
> _______________________________________________
> maintainers mailing list
> maintainers at gluster.org
> http://lists.gluster.org/mailman/listinfo/maintainers
>