I've tagged a release candidate 3.3.3dp1
commit = c8531e5d57f6126eee6f47f1ad8734e86c1e9cb5 SHA-256 96cd90f2f978bb5e6c471798fa8d4b599a9910dfdae19bbfd7353abcb1497548 ganglia-3.3.3.tar.gz The two changes from 3.3.2: a) we are no longer calling it 3.3.2, because a tag already exists with that name b) created and added artefacts requested by Michael 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? If the release candidate is accepted, then we simply need to tag the same commit as the official 3.3.3 tag git checkout 3.3.3dp1 && \ git tag -s -m 'Tag final 3.3.3 release' 3.3.3 and advertise it as official in the usual way. This was created using the procedure here: https://github.com/ganglia/monitor-core/wiki/BuildingARelease - it would be interesting to know if anyone else can verify that the procedure is acceptable, make sure that I've added enough detail for anyone else to repeat it Regards, Daniel ------------------------------------------------------------------------------ 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
