I've put the revised instructions (as below) into the wiki now:
https://github.com/ganglia/monitor-core/wiki/BuildingARelease
On 15/08/12 15:50, Daniel Pocock wrote:
>
>
> On 15/08/12 13:05, Vladimir Vuksan wrote:
>> There are a number of small fixes and one enhancement e.g. report CPU
>> steal which I feel would be a great improvement. I don't believe we need
>> to go all the way to 3.5.0 to roll those out. We can but then we have
>> proliferation of versions any time we add any enhancements.
>
> Is there something wrong with that?
>
> Many people believe it is a good thing, as a 3.[N+1] release emphasizes
> to people that they need to review new config options, default values
> may have changed, etc
>
> The actual work in preparing a 3.4.1 or a 3.5.0 is about the same
>
>> I do not want to wait until end of August. I personally prefer to
>> release often. Most of these fixes have been in the trunk for 2 months
>> already so I see no reason to delay any further.
>
>
> Most of the effort I've put into the existing releases this year has
> been done to ensure that we have something consistent to coincide with
> publication of the book and major distributions like Debian (which has
> just gone into their freeze ahead of the 7.0 release). I believe we are
> at that stage.
>
> If there does need to be an August release, I leave that for other
> people to decide and support - but unless there is a commercial driver
> for it, I personally don't have the time to invest in reviewing changes,
> releasing, testing, etc as well as dealing with any final book issues
> this month
>
> If someone does want to release, it is all scripted now, that is how I
> built 3.3.8 and 3.4.0, just checkout the git2dist tool, e.g.
>
> cd ganglia-git
>
> vi configure.in (update the version details)
> git commit -m 'Update for 3.4.1'
> git tag -s -m 'Tag v3.4.1' 3.4.1 && git push
>
> mkdir ~/ws
> git clone git://git.code.sf.net/p/git2dist/code ~/ws/git2dist
> ~/ws/git2dist/git2dist git2dist.rc 3.4.1
>
> and it will build and test the tarball for you. It even unpacks the
> tarball and tries to build the binary, test the binary, etc. The
> process must be run on a Debian 6 environment or autotools will give
> unpredictable results.
>
> You can just test-run the process too, just skip the tag step.
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Ganglia-developers mailing list
Ganglia-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ganglia-developers
