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
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
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
You will need to tag the monitor-core release then run
scripts/package-ganglia-release 3.3.2
from monitor-core. It will pull in the ganglia-web submodule in the tree.
Vladimir
On Sat, 10 Mar 2012, Daniel Pocock wrote:
On 09/03/12 16:57, Daniel Pocock wrote:
On 09/03/12 15:42, Carlo
Hi Vladimir,
I'm a little nervous about this for a couple of reasons:
a) the tag doesn't cover the ganglia-web stuff
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)
c)
Actually tag will cover ganglia-web as basically web submodule is a
pointer to a particular version of ganglia-web so when you tag
monitor-core it contains pointer to right version of ganglia-web.
I would not be in favor of putting it back in monitor-core. I think we
should really keep the
Hi Vladimir,
`inadequate' is not what I am suggesting. Nor am I saying it is broken.
Rather, I think it adds extra steps that are possibly avoidable.
When I build a ganglia-modules-linux release, everything is done for me
by autotools:
git checkout
autoreconf --install
./configure
make dist
I know what you are saying :-). What I was trying to say is that if you
feel there is a better way and you are willing to make the changes to go
ahead :-). I am not married to package-ganglia-release so anything that
helps us long term is a win.
Vladimir
On Sat, 10 Mar 2012, Daniel Pocock
On Thu, Mar 08, 2012 at 04:34:19PM +0100, Daniel Pocock wrote:
Michael, do you have write access on the wiki? I think we need to get
this distribution-specific stuff captured there along with the general
notes I provided below.
having this instructions added to the codebase just like
On 09/03/12 15:42, Carlo Marcelo Arenas Belon wrote:
On Thu, Mar 08, 2012 at 04:34:19PM +0100, Daniel Pocock wrote:
Michael, do you have write access on the wiki? I think we need to get
this distribution-specific stuff captured there along with the general
notes I provided below.
having
I notice that configure.in was only updated to 3.3.1 after the package
was put out on Sourceforge
This breaks the OpenCSW package build and may impact other people too
Can I propose a 3.3.2 release?
I was going to add a release manager document on the wiki, but I don't
have write access (can
On 08/03/12 16:21, Vladimir Vuksan wrote:
Yes. I was thinking we need to release 3.3.2.
I don't mind helping out with it, but it would be good to document the
procedure some more first
One thing I just noticed is that monitor-core/web is now empty, so I'm
not sure how you bring together the
If you do an update to 3.3.2 could you also please make sure that the
following files exist:
ChangeLog
libmetrics/ChangeLog
libmetrics/INSTALL
As with the 3.3.1 tar.gz file they don't exist thus preventing a
autoreconf -fiv that I need to perform for all my additional Ganglia
modules. Here
Perhaps best thing is to fork the repo on Github and submit a pull
request.
Thanks,
Vladimir
On Thu, 8 Mar 2012, Michael Perzl wrote:
If you do an update to 3.3.2 could you also please make sure that the
following files exist:
ChangeLog
libmetrics/ChangeLog
libmetrics/INSTALL
As
Michael, do you have write access on the wiki? I think we need to get
this distribution-specific stuff captured there along with the general
notes I provided below.
I will do the same for the OpenCSW process, then if one of us gets hit
by a bus, the releases can live on
Regards,
Daniel
On
On Thu, 8 Mar 2012, Daniel Pocock wrote:
On 08/03/12 16:21, Vladimir Vuksan wrote:
Yes. I was thinking we need to release 3.3.2.
I don't mind helping out with it, but it would be good to document the
procedure some more first
One thing I just noticed is that monitor-core/web is now
In case there's any confusion about which wiki to use: We're working on porting
the information which is in the Trac wiki over to github. I think anyone with a
github account can create or a page.
https://github.com/ganglia/monitor-core/wiki
https://github.com/ganglia/ganglia-web/wiki
Github
Daniel,
I just finished commiting my changes for ganglia web 3.3.2 so if
you want to tag monitor-core as 3.3.2 and package it up that would be
great.
Vladimir
On Thu, 8 Mar 2012, Daniel Pocock wrote:
Michael, do you have write access on the wiki? I think we need to get
this
18 matches
Mail list logo
