>>> On 3/21/2012 at 12:48 PM, in message
, Vladimir Vuksan
wrote:
> I agree with Alex. We are churning through too many versions. I would
> personally be OK with overriding the existing 3.3.2 tag and going with
> 3.3.2 instead of 3.3.4.
>
The problem with reusing a version number is that you e
Release 3.3.4
The release has now been tagged in git
commit = c25c4b31a874ab7105395eb712f5be8fc5a0539e
Filename: ganglia-3.3.4.tar.gz
SHA256 checksum:
4d86b49abe9afe48ae148c4738627680b81fc27a39bfb2e4fb4d89db53680842
It is still on the pre-release page on Sourceforge, if no problems are
found
On 21/03/12 19:48, Vladimir Vuksan wrote:
> I agree with Alex. We are churning through too many versions. I would
> personally be OK with overriding the existing 3.3.2 tag and going with
> 3.3.2 instead of 3.3.4.
Having been involved in the releases between 3.1.2 and 3.1.7, I accept
some of the re
I agree with Alex. We are churning through too many versions. I would
personally be OK with overriding the existing 3.3.2 tag and going with
3.3.2 instead of 3.3.4.
Vladimir
On Wed, 21 Mar 2012, Alex Dean wrote:
>
> On Mar 21, 2012, at 11:50 AM, Daniel Pocock wrote:
>
>> On 21/03/2012 16:49, J
On 21/03/2012 17:54, Alex Dean wrote:
>
> On Mar 21, 2012, at 11:50 AM, Daniel Pocock wrote:
>
>> On 21/03/2012 16:49, Jeff Buchbinder wrote:
>>> I found a small RPM packaging issue, which I corrected here:
>>>
>>> https://github.com/ganglia/monitor-core/commit/c25c4b31a874ab7105395eb712f5be8fc5a05
On Mar 21, 2012, at 11:50 AM, Daniel Pocock wrote:
> On 21/03/2012 16:49, Jeff Buchbinder wrote:
>> I found a small RPM packaging issue, which I corrected here:
>>
>> https://github.com/ganglia/monitor-core/commit/c25c4b31a874ab7105395eb712f5be8fc5a0539e
>>
>> I haven't changed the tagging or a
On 21/03/2012 16:49, Jeff Buchbinder wrote:
> I found a small RPM packaging issue, which I corrected here:
>
> https://github.com/ganglia/monitor-core/commit/c25c4b31a874ab7105395eb712f5be8fc5a0539e
>
> I haven't changed the tagging or anything yet.
Thanks for spotting that
I'll see if there is a
I found a small RPM packaging issue, which I corrected here:
https://github.com/ganglia/monitor-core/commit/c25c4b31a874ab7105395eb712f5be8fc5a0539e
I haven't changed the tagging or anything yet.
Jeff
--
This SF email i
Previous comments on this list (when the 3.3.2 release was proposed a
few weeks ago) suggested that all wiki material should move to github
Consequently, I've just gone along with that and added my comments on
release process and version numbers to the github wiki.
I actually think some of th
All,
My comments on this subject probably have more to do with the overall way
that the Ganglia projects works rather than just versioning. Right now we have
a wiki page that is hosted at SourceForge
(http://sourceforge.net/apps/trac/ganglia) which describes how the Ganglia
project used to
I've added a new wiki page to capture what has been discussed:
https://github.com/ganglia/monitor-core/wiki/VersionNumbers
Anyone who is impacted by this is really encouraged to add something to
the page, even if it is just a link at the bottom
I verified that this tar.gz release builds cleanly with my "autoreconf"
on the following OS versions:
AIX 5.1, AIX 5.3
RHEL 4 U3, RHEL 6, SLES 9 SP3, SLES 10, SLES 11 (all on Power Systems)
Regards,
Michael
On 03/21/2012 10:32 AM, Daniel Pocock wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Release 3.3.3
The release has now been tagged in git
commit = c8531e5d57f6126eee6f47f1ad8734e86c1e9cb5
Filename: ganglia-3.3.3.tar.gz
SHA256 checksum:
96cd90f2f978bb5e6c471798fa8d4b599a9910dfdae19bbfd7353abcb1497548
It is still on the pre-relea
13 matches
Mail list logo
