It looks like github is presenting nothing but problems. Anything that I have
had to install from there has always been a big hassle. Perhaps a more
simplified solution should be implemented.
________________________________
From: Daniel Pocock <dan...@pocock.com.au>
To: Carlo Marcelo Arenas Belon <care...@sajinet.com.pe>; Vladimir Vuksan
<vli...@veus.hr>; Carlo Marcelo Arenas Belon <care...@sajinet.com.pe>; Vladimir
Vuksan <vli...@veus.hr>
Cc: ganglia-developers@lists.sourceforge.net
Sent: Sunday, March 11, 2012 4:20 PM
Subject: Re: [Ganglia-developers] Ganglia 3.3.1 configure.in broken, 3.3.2
needed
Carlo Marcelo Arenas Belon <care...@sajinet.com.pe> wrote:
>On Sat, Mar 10, 2012 at 04:25:16PM -0500, Vladimir Vuksan wrote:
>> I am not married to package-ganglia-release so anything that
>> helps us long term is a win.
>
>I think the problems are not with the tools but with the process
>and as was spelled out on the original list of bulletpoints.
>
>agree though that simplifying tools goes also together with making
>the process simpler and less prone to failures.
>
It also means someone new to the project can do things more quickly without
needing to familiarise themselves with a specific build process or someone
familiar with packaging (e.g. Opencsw or Debian) can quickly push out a
security fix release even if they haven't looked at Ganglia before, just having
git and autotools knowledge will be sufficient
>> >> On Sat, 10 Mar 2012, Daniel Pocock wrote:
>> >>> a) the tag doesn't cover the ganglia-web stuff
>
>this is not correct, but made complicated by the fact that the tags are
Yes, I agree my statement was too general. Git does support a number of
workflows like this, but once again, every extra step in the release does add a
slightly higher risk of error
>
>not static, not standard (3.3.2-3 might had been better called 3.3.2.3
>IMHO),
>and that they are not matching :
>
> $ git describe --tags
> 3.3.2
> $ cd web/
> $ git describe --tags
> 3.3.2-1
>
>> >>> b) the tag is created before testing (which is not necessary when
>using
>> >>> git, you can tag after you test, because a tag is just a checksum
>of
>> >>> what you tested)
>
>more importantly, you could end up pushing that tag by mistake, and end
>up
>changing it later (something that wouldn't work since you can't force
>every
>clone to delete and reaquire that tag).
>
>if enforcing having a tag is going to be used in this way, will be
>better
>to stick to names like 3.3.2pre1 or use the old svn standard of not
>updating
>the main version after it has been tested and release prereleases with
>versions
>like 3.1.1.x (where x used to be the svn revision, but now would have
>to be
>a monotonically increasing number)
>
>I'd prefer using the 'pre' notation which is I submitted 74ddc9e so
>hopefully
>it will be more difficult to have a release like 3.3.1 where the
>version of
>the package (and associated libraries) was wrong.
In fact, a tag is just a pointer to a commit, so you can make two tags on the
same commit (e.g. 3.3.2rc and 3.3.2 can both point to the same commit just like
two symlinks pointing to the same file)
>
>the most important part of this being of course, that it is possible to
>do
>more coordinated and exhaustive testing before release.
>
Yes, exactly, I think we need a tarball stress test checklist similar to the
release checklist, I've already given some comments about possible tests and it
would be interesting to get further test cases that people would use if they
were doing the release
------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
Ganglia-developers mailing list
Ganglia-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ganglia-developers
------------------------------------------------------------------------------
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
_______________________________________________
Ganglia-developers mailing list
Ganglia-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ganglia-developers
