Re: [Ganglia-developers] 3.3.3dp1 release candidate

2012-03-21 Thread Bernard Li
Hi Daniel:

On Tue, Mar 20, 2012 at 10:47 AM, Daniel Pocock dan...@pocock.com.au wrote:

 I've put it in the pre-release section on Sourceforge:
 https://sourceforge.net/projects/ganglia/files/pre-release/

 Bernard, can you copy it to the page you mentioned, or let me know how
 to do this in future?

That location is fine.  http://ganglia.info/downloads is just web
space hosted by SourceForge for our website.  If you have access to
modify the website files, you have access to it.

It might actually be better to host it via their file release system
(which you've done) since that probably provides mirroring
automatically.

Thanks,

Bernard

--
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure
___
Ganglia-developers mailing list
Ganglia-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ganglia-developers


[Ganglia-developers] 3.3.3 tagged

2012-03-21 Thread Daniel Pocock
-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-release page on Sourceforge, if no problems are
found in the next 7 days then it can become the official
release.

https://sourceforge.net/projects/ganglia/files/pre-release/



-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)

iQIcBAEBCAAGBQJPaaFLAAoJEGxlgOd711bEz/sP/RWF1uMcMMGho+EVx44KIvVA
hwtV0Wi2hMYkoqRPLcI2Bg+y/UzkMaVvGTuaRQQs4xF4sxw0UlJv+L649eV3/viJ
zhnAQyJ7GQCOPns9sgra5R+FcclUsdEUZwmDZmWJoRvCSfsxacQHJkhsgfvTLCYD
96UhAaANUOq/7GpoCt46spOdD2ZdbObu/J7lj7pSEy4nDJjYOBQtQWx50nc42OMQ
yiOHzlg+2p4oZBHDkqkquT4O5f+kl5e6Ot2EkA4egpcBEWChpCLs7Jptn4kxMLLJ
3HtIC44cUVHo4cb1Lk/3nRna0zUhfvqSPpTTtAhrjDrZPYly5UhA1EA4DEhSwK0o
gg0O4tYcNcApsD3Ihoj1ARkJN70mHITEhu777FMsv+fb9DOUxC+ZRMrOhR55KiEG
xkJHQOAtXhDXcAZvG3TVXbcGeHaNhIj5GlrOTDxIRj4xndxNehImS9wxjc8WNf9v
T3nK7cFO5cMIvAmHZdwb/esrPa33IOQPefdK+TLZmokip2nvdqCraXAWih2URu1W
wUa+I1vWAIo0ilqQZH/EcQBhdfwgCvq2RCOWgrf5OT3vO1yYsdnHd0cUrVBr0zd3
Mmfb325Eq0Eb4L5fwQ5BwAPUdIDgFN8XNFlz4uKx0JrwNykPY5DoD7rQwh7K1Xdb
PQ9qPLoP/oy+Fh51m4U5
=g4Xd
-END PGP SIGNATURE-

--
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure
___
Ganglia-developers mailing list
Ganglia-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ganglia-developers


Re: [Ganglia-developers] 3.3.3 tagged

2012-03-21 Thread Michael Perzl
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: 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-release page on Sourceforge, if no problems are
 found in the next 7 days then it can become the official
 release.

 https://sourceforge.net/projects/ganglia/files/pre-release/



 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1.4.10 (GNU/Linux)

 iQIcBAEBCAAGBQJPaaFLAAoJEGxlgOd711bEz/sP/RWF1uMcMMGho+EVx44KIvVA
 hwtV0Wi2hMYkoqRPLcI2Bg+y/UzkMaVvGTuaRQQs4xF4sxw0UlJv+L649eV3/viJ
 zhnAQyJ7GQCOPns9sgra5R+FcclUsdEUZwmDZmWJoRvCSfsxacQHJkhsgfvTLCYD
 96UhAaANUOq/7GpoCt46spOdD2ZdbObu/J7lj7pSEy4nDJjYOBQtQWx50nc42OMQ
 yiOHzlg+2p4oZBHDkqkquT4O5f+kl5e6Ot2EkA4egpcBEWChpCLs7Jptn4kxMLLJ
 3HtIC44cUVHo4cb1Lk/3nRna0zUhfvqSPpTTtAhrjDrZPYly5UhA1EA4DEhSwK0o
 gg0O4tYcNcApsD3Ihoj1ARkJN70mHITEhu777FMsv+fb9DOUxC+ZRMrOhR55KiEG
 xkJHQOAtXhDXcAZvG3TVXbcGeHaNhIj5GlrOTDxIRj4xndxNehImS9wxjc8WNf9v
 T3nK7cFO5cMIvAmHZdwb/esrPa33IOQPefdK+TLZmokip2nvdqCraXAWih2URu1W
 wUa+I1vWAIo0ilqQZH/EcQBhdfwgCvq2RCOWgrf5OT3vO1yYsdnHd0cUrVBr0zd3
 Mmfb325Eq0Eb4L5fwQ5BwAPUdIDgFN8XNFlz4uKx0JrwNykPY5DoD7rQwh7K1Xdb
 PQ9qPLoP/oy+Fh51m4U5
 =g4Xd
 -END PGP SIGNATURE-

 --
 This SF email is sponsosred by:
 Try Windows Azure free for 90 days Click Here
 http://p.sf.net/sfu/sfd2d-msazure
 ___
 Ganglia-developers mailing list
 Ganglia-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/ganglia-developers


--
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure
___
Ganglia-developers mailing list
Ganglia-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ganglia-developers


[Ganglia-developers] new wiki: Version numbering

2012-03-21 Thread Daniel Pocock

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


--
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure
___
Ganglia-developers mailing list
Ganglia-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ganglia-developers


[Ganglia-developers] Other project related stuff (was:Re: releasing 3.3.2 today?)

2012-03-21 Thread Brad Nicholes
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 work when the repository was SVN.  Now that things have moved 
to Github and some of the people who were running the project at the time are 
not as involved anymore (namely me :), it seems as though things are getting a 
little confusing.  For example, the versioning rules for Ganglia releases is 
also described on the sourceforge wiki 
(http://sourceforge.net/apps/trac/ganglia/wiki/how_project_works).  Although in 
some ways it might be similar to what has been discussed recently, it is 
different.  People who are trying to figure out how the Ganglia project works 
will probably run across the older wiki page first (since it is still linked to 
Ganglia.info) and then be confused by how versioning is actually handled now.  
Also, since the procedures and policies on the older wiki page were modeled 
around SVN, the Git way of doing things obviously makes a lot of the older wiki 
information obsolete.

   I think it is important that the Ganglia project gits on the same (wiki) 
page with regards to how the project works and what information the project 
wants to provide to new users and developers (all puns intended ;-) .  
Especially in light of the fact that many of us are working on the Ganglia 
Monitoring book.  Hopefully once the book is released, it will generate more 
interest in the Ganglia project and it would probably look bad if we had two 
different wiki pages providing conflicting information.  Since I haven't been 
as involved with the project especially since the source code was moved to Git, 
is there someone who could review the SourceForge wiki page and determine what 
information is still valid and which isn't?  At that point we could decided 
whether to just update the SourceForge wiki or move it all to Github wiki.

Comments?

Brad 


--
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure
___
Ganglia-developers mailing list
Ganglia-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ganglia-developers


Re: [Ganglia-developers] Other project related stuff

2012-03-21 Thread Daniel Pocock


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 this stuff may belong in the repo rather than 
any of the wikis (because the release process for a particular version 
should be kept with that version)

If github is the consensus, then I would propose that content should be 
cut and pasted (whether it is obsolete or not) and then the old pages 
deleted/replaced with pointers to new pages


On 21/03/2012 14:47, Brad Nicholes wrote:
 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 work when the repository was SVN.  Now that things have moved 
 to Github and some of the people who were running the project at the time are 
 not as involved anymore (namely me :), it seems as though things are getting 
 a little confusing.  For example, the versioning rules for Ganglia releases 
 is also described on the sourceforge wiki 
 (http://sourceforge.net/apps/trac/ganglia/wiki/how_project_works).  Although 
 in some ways it might be similar to what has been discussed recently, it is 
 different.  People who are trying to figure out how the Ganglia project works 
 will probably run across the older wiki page first (since it is still linked 
 to Ganglia.info) and then be confused by how version
ing
   is actually handled now.  Also, since the procedures and policies on the 
 older wiki page were modeled around SVN, the Git way of doing things 
 obviously makes a lot of the older wiki information obsolete.

 I think it is important that the Ganglia project gits on the same (wiki) 
 page with regards to how the project works and what information the project 
 wants to provide to new users and developers (all puns intended ;-) .  
 Especially in light of the fact that many of us are working on the Ganglia 
 Monitoring book.  Hopefully once the book is released, it will generate more 
 interest in the Ganglia project and it would probably look bad if we had two 
 different wiki pages providing conflicting information.  Since I haven't been 
 as involved with the project especially since the source code was moved to 
 Git, is there someone who could review the SourceForge wiki page and 
 determine what information is still valid and which isn't?  At that point we 
 could decided whether to just update the SourceForge wiki or move it all to 
 Github wiki.

 Comments?

 Brad


 --
 This SF email is sponsosred by:
 Try Windows Azure free for 90 days Click Here
 http://p.sf.net/sfu/sfd2d-msazure
 ___
 Ganglia-developers mailing list
 Ganglia-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/ganglia-developers


--
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure
___
Ganglia-developers mailing list
Ganglia-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ganglia-developers


Re: [Ganglia-developers] 3.3.3 tagged

2012-03-21 Thread Jeff Buchbinder
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 is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure
___
Ganglia-developers mailing list
Ganglia-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ganglia-developers


Re: [Ganglia-developers] 3.3.3 tagged

2012-03-21 Thread Daniel Pocock
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 any more feedback and then push out 3.3.4 tomorrow 
with that fix.  It should not prevent other people testing 3.3.3 though.


--
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure
___
Ganglia-developers mailing list
Ganglia-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ganglia-developers


Re: [Ganglia-developers] 3.3.3 tagged

2012-03-21 Thread Alex Dean

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 anything yet.
 
 Thanks for spotting that
 
 I'll see if there is any more feedback and then push out 3.3.4 tomorrow 
 with that fix.  It should not prevent other people testing 3.3.3 though.

I recall some confusion from users the last time we went through this process 
of incrementing the minor version number several times before a release: from 
3.1.2 to 3.1.7, I think.  We end up with a series of unreleased version numbers 
and that made some people wonder if they missed something.

http://www.mail-archive.com/ganglia-developers@lists.sourceforge.net/msg05496.html




signature.asc
Description: Message signed with OpenPGP using GPGMail
--
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure___
Ganglia-developers mailing list
Ganglia-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ganglia-developers


Re: [Ganglia-developers] 3.3.3 tagged

2012-03-21 Thread Daniel Pocock
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/c25c4b31a874ab7105395eb712f5be8fc5a0539e

 I haven't changed the tagging or anything yet.

 Thanks for spotting that

 I'll see if there is any more feedback and then push out 3.3.4 tomorrow
 with that fix.  It should not prevent other people testing 3.3.3 though.

 I recall some confusion from users the last time we went through this process 
 of incrementing the minor version number several times before a release: from 
 3.1.2 to 3.1.7, I think.  We end up with a series of unreleased version 
 numbers and that made some people wonder if they missed something.

 http://www.mail-archive.com/ganglia-developers@lists.sourceforge.net/msg05496.html


I think it has already been discussed and this process agreed

Can you suggest a way to improve the process (or the communication with 
users)?

--
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure
___
Ganglia-developers mailing list
Ganglia-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ganglia-developers


[Ganglia-developers] 3.3.4 tagged

2012-03-21 Thread Daniel Pocock



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 in the next 7 days then it can become the official
release.

https://sourceforge.net/projects/ganglia/files/pre-release/





--
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure
___
Ganglia-developers mailing list
Ganglia-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ganglia-developers