You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by Konstantin Boudnik <co...@apache.org> on 2013/08/06 04:50:53 UTC
[PROPOSAL] EOL'ed releases 0.3.x
Guys,
I wanna propose something drastic yet necessary in my opinion. I don't see
much of the interest in the community to continue with Bigtop release on top
of Hadoop 1.x. I might be missing something on the account of the other
developers here, but I find it harder and harder to spare any time for 0.3.1,
considering how much I need to do in the trunk based releases of Bigtop.
Hereby, I am proposing to close 0.3.1 related tickets and archive 0.3.1
version in JIRA, as well as to remove branch 0.3.1, effectively shelving the
effort on Hadoop 1 based reference implementation of the stack.
If there's not much objections on the proposal above, I will go ahead and do
the logistics in a couple of days. Otherwise, we might need to call a vote ;)
Thoughts?
--
Regards,
Cos
Re: [PROPOSAL] EOL'ed releases 0.3.x
Posted by Mark Grover <gr...@gmail.com>.
Thanks, Cos!!
On Fri, Aug 16, 2013 at 5:26 PM, Konstantin Boudnik <co...@apache.org> wrote:
> As per the discussion below I have archived version 0.3.1 in JIRA and
> renamed
> branch-0.3.1 -> deprecated-branch-0.3.1
>
> Cos
>
> On Mon, Aug 05, 2013 at 07:50PM, Konstantin Boudnik wrote:
> >
> > Guys,
> >
> > I wanna propose something drastic yet necessary in my opinion. I don't
> see
> > much of the interest in the community to continue with Bigtop release on
> top
> > of Hadoop 1.x. I might be missing something on the account of the other
> > developers here, but I find it harder and harder to spare any time for
> 0.3.1,
> > considering how much I need to do in the trunk based releases of Bigtop.
> >
> > Hereby, I am proposing to close 0.3.1 related tickets and archive 0.3.1
> > version in JIRA, as well as to remove branch 0.3.1, effectively shelving
> the
> > effort on Hadoop 1 based reference implementation of the stack.
> >
> > If there's not much objections on the proposal above, I will go ahead
> and do
> > the logistics in a couple of days. Otherwise, we might need to call a
> vote ;)
> >
> > Thoughts?
> > --
> > Regards,
> > Cos
> >
>
Re: [PROPOSAL] EOL'ed releases 0.3.x
Posted by Konstantin Boudnik <co...@apache.org>.
As per the discussion below I have archived version 0.3.1 in JIRA and renamed
branch-0.3.1 -> deprecated-branch-0.3.1
Cos
On Mon, Aug 05, 2013 at 07:50PM, Konstantin Boudnik wrote:
>
> Guys,
>
> I wanna propose something drastic yet necessary in my opinion. I don't see
> much of the interest in the community to continue with Bigtop release on top
> of Hadoop 1.x. I might be missing something on the account of the other
> developers here, but I find it harder and harder to spare any time for 0.3.1,
> considering how much I need to do in the trunk based releases of Bigtop.
>
> Hereby, I am proposing to close 0.3.1 related tickets and archive 0.3.1
> version in JIRA, as well as to remove branch 0.3.1, effectively shelving the
> effort on Hadoop 1 based reference implementation of the stack.
>
> If there's not much objections on the proposal above, I will go ahead and do
> the logistics in a couple of days. Otherwise, we might need to call a vote ;)
>
> Thoughts?
> --
> Regards,
> Cos
>
Re: [PROPOSAL] EOL'ed releases 0.3.x
Posted by Andrew Purtell <ap...@apache.org>.
On Tue, Aug 6, 2013 at 4:03 PM, Mark Grover <gr...@gmail.com>wrote:
> I am +1 on proposal to close 0.3.1 related tickets and archive 0.3.1
> version
> in JIRA
>
+1
> I would personally prefer if we should renamed the git branch from
> "branch-0.3.1" to something like "deprecated-branch-0.3.1".
+1 to this too.
--
Best regards,
- Andy
Problems worthy of attack prove their worth by hitting back. - Piet Hein
(via Tom White)
Re: [PROPOSAL] EOL'ed releases 0.3.x
Posted by Mark Grover <gr...@gmail.com>.
I am +1 on proposal to close 0.3.1 related tickets and archive 0.3.1 version
in JIRA.
I would personally prefer if we should renamed the git branch from
"branch-0.3.1" to something like "deprecated-branch-0.3.1".
Mark
On Tue, Aug 6, 2013 at 11:47 AM, Jay Vyas <ja...@gmail.com> wrote:
> Thanks roman - its a good point you make. certainly i have more pressing
> matters to attend also, and yes i guess your right, in the near future 2.x
> is going to be more important.
>
> so... i guess i ll just keep playing on the bigtop patches im already
> interested in / supposed to be looking at :)
>
Re: [PROPOSAL] EOL'ed releases 0.3.x
Posted by Jay Vyas <ja...@gmail.com>.
Thanks roman - its a good point you make. certainly i have more pressing
matters to attend also, and yes i guess your right, in the near future 2.x
is going to be more important.
so... i guess i ll just keep playing on the bigtop patches im already
interested in / supposed to be looking at :)
Re: [PROPOSAL] EOL'ed releases 0.3.x
Posted by Roman Shaposhnik <rv...@apache.org>.
On Tue, Aug 6, 2013 at 9:31 AM, Jay Vyas <ja...@gmail.com> wrote:
> For me at least --- the 1.X stuff is very important in the community... or
> at least... in my community :)
>
> Am i missing something? maybe i have misinterpretted the proposal.
Well, basically it boils down to having somebody drive the effort. ;-)
We've had a couple of folks so far chiming in on this thread saying
that they have no interest in driving 1.X based stuff. That said, part
of the reason Cos started this thread is to identify anybody who'd
be volunteering to drive it.
Jay, would you be willing to RM it? Personally I'd be more than
happy if you did, but I've got to warn you -- given that virtually
all commercial Hadoop distros are now 2.x based it could
end up being a pretty lonely job.
Thanks,
Roman.
Re: [PROPOSAL] EOL'ed releases 0.3.x
Posted by Jay Vyas <ja...@gmail.com>.
For me at least --- the 1.X stuff is very important in the community... or
at least... in my community :)
Am i missing something? maybe i have misinterpretted the proposal.
On Tue, Aug 6, 2013 at 12:22 PM, Konstantin Boudnik <co...@apache.org> wrote:
> The reason I have brought up the branch is that it doesn't have anything of
> value except for 0.3.1 specific things. But I have no problem with it
> laying
> around ;)
>
> Cos
>
> On Tue, Aug 06, 2013 at 09:04AM, Roman Shaposhnik wrote:
> > On Tue, Aug 6, 2013 at 8:29 AM, Sean Mackrory <ma...@gmail.com>
> wrote:
> > > No objection from me - although like Bruno, I don't see why we should
> > > delete the branch. Even if we have no intention of focussing further
> > > work on that line, it might be nice to keep it around for anyone who
> > > may want to build some stuff from it.
> >
> > Same here. +1 to cleaning up the JIRA and as for the branch -- we can
> > just let it linger I suppose.
> >
> > Thanks,
> > Roman.
>
--
Jay Vyas
http://jayunit100.blogspot.com
Re: [PROPOSAL] EOL'ed releases 0.3.x
Posted by Konstantin Boudnik <co...@apache.org>.
The reason I have brought up the branch is that it doesn't have anything of
value except for 0.3.1 specific things. But I have no problem with it laying
around ;)
Cos
On Tue, Aug 06, 2013 at 09:04AM, Roman Shaposhnik wrote:
> On Tue, Aug 6, 2013 at 8:29 AM, Sean Mackrory <ma...@gmail.com> wrote:
> > No objection from me - although like Bruno, I don't see why we should
> > delete the branch. Even if we have no intention of focussing further
> > work on that line, it might be nice to keep it around for anyone who
> > may want to build some stuff from it.
>
> Same here. +1 to cleaning up the JIRA and as for the branch -- we can
> just let it linger I suppose.
>
> Thanks,
> Roman.
Re: [PROPOSAL] EOL'ed releases 0.3.x
Posted by Roman Shaposhnik <rv...@apache.org>.
On Tue, Aug 6, 2013 at 8:29 AM, Sean Mackrory <ma...@gmail.com> wrote:
> No objection from me - although like Bruno, I don't see why we should
> delete the branch. Even if we have no intention of focussing further
> work on that line, it might be nice to keep it around for anyone who
> may want to build some stuff from it.
Same here. +1 to cleaning up the JIRA and as for the branch -- we can
just let it linger I suppose.
Thanks,
Roman.
Re: [PROPOSAL] EOL'ed releases 0.3.x
Posted by Sean Mackrory <ma...@gmail.com>.
No objection from me - although like Bruno, I don't see why we should
delete the branch. Even if we have no intention of focussing further
work on that line, it might be nice to keep it around for anyone who
may want to build some stuff from it.
On Mon, Aug 5, 2013 at 11:00 PM, Bruno Mahé <bm...@apache.org> wrote:
> On 08/05/2013 07:50 PM, Konstantin Boudnik wrote:
>>
>>
>> Guys,
>>
>> I wanna propose something drastic yet necessary in my opinion. I don't see
>> much of the interest in the community to continue with Bigtop release on
>> top
>> of Hadoop 1.x. I might be missing something on the account of the other
>> developers here, but I find it harder and harder to spare any time for
>> 0.3.1,
>> considering how much I need to do in the trunk based releases of Bigtop.
>>
>> Hereby, I am proposing to close 0.3.1 related tickets and archive 0.3.1
>> version in JIRA, as well as to remove branch 0.3.1, effectively shelving
>> the
>> effort on Hadoop 1 based reference implementation of the stack.
>>
>> If there's not much objections on the proposal above, I will go ahead and
>> do
>> the logistics in a couple of days. Otherwise, we might need to call a vote
>> ;)
>>
>> Thoughts?
>>
>
> If no one wants to take over the 0.3 branch, then +1 to close applicable
> tickets.
>
> But why deleting the 0.3.1 branch?
> Is there any issue with keeping it around?
>
>
> Thanks,
> Bruno
Re: [PROPOSAL] EOL'ed releases 0.3.x
Posted by Bruno Mahé <bm...@apache.org>.
On 08/05/2013 07:50 PM, Konstantin Boudnik wrote:
>
> Guys,
>
> I wanna propose something drastic yet necessary in my opinion. I don't see
> much of the interest in the community to continue with Bigtop release on top
> of Hadoop 1.x. I might be missing something on the account of the other
> developers here, but I find it harder and harder to spare any time for 0.3.1,
> considering how much I need to do in the trunk based releases of Bigtop.
>
> Hereby, I am proposing to close 0.3.1 related tickets and archive 0.3.1
> version in JIRA, as well as to remove branch 0.3.1, effectively shelving the
> effort on Hadoop 1 based reference implementation of the stack.
>
> If there's not much objections on the proposal above, I will go ahead and do
> the logistics in a couple of days. Otherwise, we might need to call a vote ;)
>
> Thoughts?
>
If no one wants to take over the 0.3 branch, then +1 to close applicable
tickets.
But why deleting the 0.3.1 branch?
Is there any issue with keeping it around?
Thanks,
Bruno