30.05.2016 05:08, Sankarshan Mukhopadhyay написав:
It would perhaps be worthwhile to extend this release timeline/cadence
discussion into (a) End-of-Life definition and invocation (b) whether
a 'long term support' (assuming that is what LTS is) is of essentially
any value to users of GlusterFS.
Hello folks,
I'm trying to get a sense of how our Jenkins instance. In particular, I'm
trying to understand the following:
1. How jobs are created. Is this version controlled or automated in any
manner?
2. How are the machines created? Do we have a standardized image?
3. Where is the code (the re
The migration is now complete.
Please let me know if you notice any issues whatsoever.
On Mon, May 30, 2016 at 7:25 AM, Nigel Babu wrote:
> Hello,
>
> I'll be bring down Gerrit in 30 mins for a planned downtime of 2 hours.
> I'll post updates to this thread when all is well.
>
> --
> nigelb
>
On Mon, May 30, 2016 at 7:07 AM, Vijay Bellur wrote:
> Since we do not have any objections to this proposal, let us do the
> following for 3.7.12:
>
> 1. Treat June 1st as the cut-off for patch acceptance in release-3.7.
> 2. I will tag 3.7.12rc1 on June 2nd.
> 3. All maintainers to ack content an
On Fri, May 20, 2016 at 7:30 PM, Shyam wrote:
> On 05/19/2016 10:25 PM, Pranith Kumar Karampuri wrote:
>>
>> Once every 3 months i.e. option 3 sounds good to me.
>
>
> +1 from my end.
>
> Every 2 months seems to be a bit too much, 4 months is still fine, but gives
> us 1 in 3 to pick the LTS, I li
Hello,
I'll be bring down Gerrit in 30 mins for a planned downtime of 2 hours.
I'll post updates to this thread when all is well.
--
nigelb
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel
On Fri, May 20, 2016 at 10:00 AM, Shyam wrote:
> On 05/19/2016 10:25 PM, Pranith Kumar Karampuri wrote:
>>
>> Once every 3 months i.e. option 3 sounds good to me.
>
>
> +1 from my end.
>
> Every 2 months seems to be a bit too much, 4 months is still fine, but gives
> us 1 in 3 to pick the LTS, I l
Since we do not have any objections to this proposal, let us do the
following for 3.7.12:
1. Treat June 1st as the cut-off for patch acceptance in release-3.7.
2. I will tag 3.7.12rc1 on June 2nd.
3. All maintainers to ack content and stability of components by June 9th.
4. Release 3.7.12 around J
