Hi all,
As a step towards achieving our promise on Goals for the year 2018 [1], we
have taken up automating some of the work flow of glusterfs development
cycle.
Below is the update on one such effort.
This work intends to make the development process more efficient by
automating aspects o
Hi all,
Below is the proposal which most of us in maintainers list have agreed
upon. Sharing it here so we come to conclusion quickly, and move on :-)
---
Until now, Gluster project’s releases followed x.y.z model, where x is
indicating a major revision, and y a minor, and z as a patched release
GlusterFS Coverity covscan results are available from
http://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/2018-03-12-a96c7e74
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman
On Mon, Mar 12, 2018 at 5:51 PM, Amar Tumballi wrote:
> Hi all,
>
> Below is the proposal which most of us in maintainers list have agreed
> upon. Sharing it here so we come to conclusion quickly, and move on :-)
>
> ---
>
> Until now, Gluster project’s releases followed x.y.z model, where x is
>
Le lundi 26 février 2018 à 18:07 +0100, Michael Scherer a écrit :
> Hi folks,
>
> I finally managed to complete the deployment of a High Availiability
> reverse proxy for server hosted in the community cage[1]. While the
> switch should be invisible to everybody, and likely bring nothing
> (except
On 03/12/2018 10:34 AM, Atin Mukherjee wrote:
> *
>
> After 4.1, we want to move to either continuous numbering (like
> Fedora), or time based (like ubuntu etc) release numbers. Which
> is the model we pick is not yet finalized. Happy to hear opinions.
>
>
> Not sur
Hi,
As we wind down on 4.0 activities (waiting on docs to hit the site, and
packages to be available in CentOS repositories before announcing the
release), it is time to start preparing for the 4.1 release.
4.1 is where we have GD2 fully functional and shipping with migration
tools to aid Gluster
Hi,
Below are the features we are targeting for 4.1:
1. https://github.com/gluster/glusterfs/issues/364 - Write behind aggregate.
The patch is merged, documentation is pending.
2. https://github.com/gluster/glusterfs/issues/274 - Re-read dentry cache
The patch is under review, hopefully
On Wed, Feb 28, 2018 at 6:56 PM, Deepshikha Khandelwal
wrote:
> Hi,
>
> We have launched the alpha version of SOFTSERVE[1], which allows Gluster
> Github organization members to provision virtual machines for a specified
> duration of time. These machines will be deleted automatically afterwards
