You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by Anatoli Fomenko <af...@yahoo.com> on 2012/08/24 06:31:59 UTC
Bigtop release for Hadoop 1.1
My project requires Hadoop 1.1, and as I understand Bigtop release for Hadoop 1.1 has been planned.
I would be very interested in helping with preparing this release. Please let me know when and how I could help.
Thank you,
Anatoli
Re: Bigtop release for Hadoop 1.1
Posted by Roman Shaposhnik <rv...@apache.org>.
On Fri, Aug 24, 2012 at 8:45 AM, Anatoli Fomenko <af...@yahoo.com> wrote:
> Thanks Cos for a good news. I'm standing by for your updates.
Anatoli -- don't be afraid to contribute patches, etc. Cos and I will make
sure it all gets reviewed/committed in time!
Thanks,
Roman.
P.W. Welcome to Bigtop! ;-)
Re: Bigtop release for Hadoop 1.1
Posted by Anatoli Fomenko <af...@yahoo.com>.
Thanks Cos for a good news. I'm standing by for your updates.
Anatoli
________________________________
From: Konstantin Boudnik <co...@apache.org>
To: bigtop-dev@incubator.apache.org; Anatoli Fomenko <af...@yahoo.com>
Sent: Thursday, August 23, 2012 10:39 PM
Subject: Re: Bigtop release for Hadoop 1.1
Thanks Anatoli!
I guess this is what I needed as a little reminder, because I got distracted
with some stuff and have delayed with the 0.3.1 work.
I have just created branch-0.3.1 for all the work related on the release. I
will send out proposal for the release BOM shortly. I will go through the JIRA
and mark whatever is relevant as affecting 0.3.1.
Please be warned that Hadoop 1.1 hasn't been officially released yet, which of
course doesn't stop us from the doing whatever needed work here.
You can help with cleaning the JIRAs in the release (once the list is ready)
and doing the usual development work, including testing, etc.
Your help would be greatly appreciated!
Cos
On Thu, Aug 23, 2012 at 09:31PM, Anatoli Fomenko wrote:
> My project requires Hadoop 1.1, and as I understand Bigtop release for Hadoop 1.1 has been planned.
>
> I would be very interested in helping with preparing this release. Please let me know when and how I could help.
>
> Thank you,
> Anatoli
Re: Keeping CHANGES.txt up to date
Posted by Arun C Murthy <ac...@hortonworks.com>.
The reason we maintained CHANGES.txt in Hadoop was to bifurcate new features, incompatible changes etc.
The same can be done by coming up with a convention for commit msgs; also having 'git log' local makes it much more palatable than 'svn log'. In svn land CHANGES.txt is much more critical for developer productivity.
Arun
On Aug 28, 2012, at 8:13 PM, Roman Shaposhnik wrote:
> On Tue, Aug 28, 2012 at 8:06 PM, Konstantin Boudnik <co...@apache.org> wrote:
>> I am coming from Hadoop's land where a normal practice is to accompany any
>> commit with an appropriate record in the CHANGES.txt. It seems to be much
>> easier not to miss anything this way around, doesn't it?
>
> Understood. Personally, I'm a big fan of autogenerating CHANGES.txt
> from the Git/SVN history. Not sure what others think.
>
> Thanks,
> Roman.
--
Arun C. Murthy
Hortonworks Inc.
http://hortonworks.com/
Re: Keeping CHANGES.txt up to date
Posted by Konstantin Boudnik <co...@apache.org>.
On Tue, Aug 28, 2012 at 08:13PM, Roman Shaposhnik wrote:
> On Tue, Aug 28, 2012 at 8:06 PM, Konstantin Boudnik <co...@apache.org> wrote:
> > I am coming from Hadoop's land where a normal practice is to accompany any
> > commit with an appropriate record in the CHANGES.txt. It seems to be much
> > easier not to miss anything this way around, doesn't it?
>
> Understood. Personally, I'm a big fan of autogenerating CHANGES.txt
> from the Git/SVN history. Not sure what others think.
Me too. So, if we have a process (as in a script:) in place for that then I am
totally fine and will in fact go ahead and remove two jiras from 0.5 section.
Sorry for the confusion - I musta been sleeping behind the wheel.
Cos
>
> Thanks,
> Roman.
Re: Keeping CHANGES.txt up to date
Posted by Roman Shaposhnik <rv...@apache.org>.
On Tue, Aug 28, 2012 at 8:06 PM, Konstantin Boudnik <co...@apache.org> wrote:
> I am coming from Hadoop's land where a normal practice is to accompany any
> commit with an appropriate record in the CHANGES.txt. It seems to be much
> easier not to miss anything this way around, doesn't it?
Understood. Personally, I'm a big fan of autogenerating CHANGES.txt
from the Git/SVN history. Not sure what others think.
Thanks,
Roman.
Re: Keeping CHANGES.txt up to date
Posted by Konstantin Boudnik <co...@apache.org>.
I am coming from Hadoop's land where a normal practice is to accompany any
commit with an appropriate record in the CHANGES.txt. It seems to be much
easier not to miss anything this way around, doesn't it?
Cos
On Tue, Aug 28, 2012 at 06:30PM, Roman Shaposhnik wrote:
> On Mon, Aug 27, 2012 at 7:22 PM, Konstantin Boudnik <co...@apache.org> wrote:
> >
> > Guys,
> >
> > I have noticed that CHANGES.txt hasn't been updated for a very long time.
> > Am I
> > missing something?
>
> I tend to only update it for releases. Do you see a release where it wasn't
> updated?
>
> Thanks,
> Roman.
Re: Keeping CHANGES.txt up to date
Posted by Roman Shaposhnik <rv...@apache.org>.
On Mon, Aug 27, 2012 at 7:22 PM, Konstantin Boudnik <co...@apache.org> wrote:
>
> Guys,
>
> I have noticed that CHANGES.txt hasn't been updated for a very long time.
> Am I
> missing something?
I tend to only update it for releases. Do you see a release where it wasn't
updated?
Thanks,
Roman.
Keeping CHANGES.txt up to date
Posted by Konstantin Boudnik <co...@apache.org>.
Guys,
I have noticed that CHANGES.txt hasn't been updated for a very long time. Am I
missing something?
Cos
Re: Bigtop release for Hadoop 1.1
Posted by Konstantin Boudnik <co...@apache.org>.
Thanks Anatoli!
I guess this is what I needed as a little reminder, because I got distracted
with some stuff and have delayed with the 0.3.1 work.
I have just created branch-0.3.1 for all the work related on the release. I
will send out proposal for the release BOM shortly. I will go through the JIRA
and mark whatever is relevant as affecting 0.3.1.
Please be warned that Hadoop 1.1 hasn't been officially released yet, which of
course doesn't stop us from the doing whatever needed work here.
You can help with cleaning the JIRAs in the release (once the list is ready)
and doing the usual development work, including testing, etc.
Your help would be greatly appreciated!
Cos
On Thu, Aug 23, 2012 at 09:31PM, Anatoli Fomenko wrote:
> My project requires Hadoop 1.1, and as I understand Bigtop release for Hadoop 1.1 has been planned.
>
> I would be very interested in helping with preparing this release. Please let me know when and how I could help.
>
> Thank you,
> Anatoli