You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by Evans Ye <ev...@apache.org> on 2020/03/16 06:05:32 UTC
[DISCUSS] Drop Apache Tajo, Apache Hama, and Apache Apex
Hi folks,
I'd like to raise the discussion about the cleanup of supported component
matrix.
From [1] the latest release of Tajo is 0.11.3 which was out on 2016-05-18.
Since then there're no further release. Similarly on Hama side the latest
release is on Jan 28, 2016 [2]. Apex is on Attic so there's no chance to
get new release further [3].
Though we'd like to support as many projects as possible, there's simply
not enough effort and resource to do it. Dropping them can also let us more
focus on what's valuable to the users. What do you think?
Kengo Seki
As 1.5 RM what do you think? I think if the discussion is positive this
will be in 1.5 release.
[1] https://tajo.apache.org/
[2] https://hama.apache.org/
[3] https://apex.apache.org/
Evans
Re: [DISCUSS] Drop Apache Tajo, Apache Hama, and Apache Apex
Posted by Kengo Seki <se...@apache.org>.
Sorry for missing this thread, I'm also +1 for dropping these inactive
components in 1.5.0. Will file a corresponding JIRA issue.
Kengo Seki <se...@apache.org>
On Tue, Mar 17, 2020 at 12:32 PM Jun HE <ju...@apache.org> wrote:
>
> I'm +1 to remove these inactive projects.
> I remember that there was a discussion to leave those projects to another
> branch, and related dev work depends on volunteered maintainer/contributor.
> So maybe we can start this after v1.5 is released.
>
>
> Masatake Iwasaki <iw...@oss.nttdata.co.jp> 于2020年3月17日周二 上午7:56写道：
>
> > I'm +1 on removing (effectively) retired products.
> >
> > While deprecating in the next release and
> > removing in after the next might be usual way,
> > I think it would be ok to remove them in 1.5.0.
> > Each product in Bigtop has dedicated subdirectories.
> > Removing (and reverting the removal) should be easy
> > unless it is depended by other products.
> >
> > Thanks,
> > Masatake Iwasaki
> >
> >
> > On 3/16/20 15:13, Konstantin Boudnik wrote:
> > > Thanks for bringing this up, Evans!
> > >
> > > I think this trimming makes total sense and we were through similar
> > > discussions before. In fact there's a consensus that we simply can't
> > > support all the projects that seem to be nice, especially those that
> > > weren't been active in 3+ years.
> > >
> > > I am in favor of trimming the stack down. Unless, there's a maintainer
> > > in the community who wants to step up and help.
> > >
> > > --
> > > Regards,
> > > Cos
> > >
> > > On 3/16/20 1:05 PM, Evans Ye wrote:
> > >> Hi folks,
> > >>
> > >> I'd like to raise the discussion about the cleanup of supported
> > >> component
> > >> matrix.
> > >>
> > >> From [1] the latest release of Tajo is 0.11.3 which was out on
> > >> 2016-05-18.
> > >> Since then there're no further release. Similarly on Hama side the
> > >> latest
> > >> release is on Jan 28, 2016 [2]. Apex is on Attic so there's no chance to
> > >> get new release further [3].
> > >>
> > >> Though we'd like to support as many projects as possible, there's simply
> > >> not enough effort and resource to do it. Dropping them can also let
> > >> us more
> > >> focus on what's valuable to the users. What do you think?
> > >>
> > >> Kengo Seki
> > >> As 1.5 RM what do you think? I think if the discussion is positive this
> > >> will be in 1.5 release.
> > >>
> > >> [1] https://tajo.apache.org/
> > >> [2] https://hama.apache.org/
> > >> [3] https://apex.apache.org/
> > >>
> > >> Evans
> > >>
> >
> >
Re: [DISCUSS] Drop Apache Tajo, Apache Hama, and Apache Apex
Posted by Jun HE <ju...@apache.org>.
I'm +1 to remove these inactive projects.
I remember that there was a discussion to leave those projects to another
branch, and related dev work depends on volunteered maintainer/contributor.
So maybe we can start this after v1.5 is released.
Masatake Iwasaki <iw...@oss.nttdata.co.jp> 于2020年3月17日周二 上午7:56写道：
> I'm +1 on removing (effectively) retired products.
>
> While deprecating in the next release and
> removing in after the next might be usual way,
> I think it would be ok to remove them in 1.5.0.
> Each product in Bigtop has dedicated subdirectories.
> Removing (and reverting the removal) should be easy
> unless it is depended by other products.
>
> Thanks,
> Masatake Iwasaki
>
>
> On 3/16/20 15:13, Konstantin Boudnik wrote:
> > Thanks for bringing this up, Evans!
> >
> > I think this trimming makes total sense and we were through similar
> > discussions before. In fact there's a consensus that we simply can't
> > support all the projects that seem to be nice, especially those that
> > weren't been active in 3+ years.
> >
> > I am in favor of trimming the stack down. Unless, there's a maintainer
> > in the community who wants to step up and help.
> >
> > --
> > Regards,
> > Cos
> >
> > On 3/16/20 1:05 PM, Evans Ye wrote:
> >> Hi folks,
> >>
> >> I'd like to raise the discussion about the cleanup of supported
> >> component
> >> matrix.
> >>
> >> From [1] the latest release of Tajo is 0.11.3 which was out on
> >> 2016-05-18.
> >> Since then there're no further release. Similarly on Hama side the
> >> latest
> >> release is on Jan 28, 2016 [2]. Apex is on Attic so there's no chance to
> >> get new release further [3].
> >>
> >> Though we'd like to support as many projects as possible, there's simply
> >> not enough effort and resource to do it. Dropping them can also let
> >> us more
> >> focus on what's valuable to the users. What do you think?
> >>
> >> Kengo Seki
> >> As 1.5 RM what do you think? I think if the discussion is positive this
> >> will be in 1.5 release.
> >>
> >> [1] https://tajo.apache.org/
> >> [2] https://hama.apache.org/
> >> [3] https://apex.apache.org/
> >>
> >> Evans
> >>
>
>
Re: [DISCUSS] Drop Apache Tajo, Apache Hama, and Apache Apex
Posted by Masatake Iwasaki <iw...@oss.nttdata.co.jp>.
I'm +1 on removing (effectively) retired products.
While deprecating in the next release and
removing in after the next might be usual way,
I think it would be ok to remove them in 1.5.0.
Each product in Bigtop has dedicated subdirectories.
Removing (and reverting the removal) should be easy
unless it is depended by other products.
Thanks,
Masatake Iwasaki
On 3/16/20 15:13, Konstantin Boudnik wrote:
> Thanks for bringing this up, Evans!
>
> I think this trimming makes total sense and we were through similar
> discussions before. In fact there's a consensus that we simply can't
> support all the projects that seem to be nice, especially those that
> weren't been active in 3+ years.
>
> I am in favor of trimming the stack down. Unless, there's a maintainer
> in the community who wants to step up and help.
>
> --
> Regards,
> Cos
>
> On 3/16/20 1:05 PM, Evans Ye wrote:
>> Hi folks,
>>
>> I'd like to raise the discussion about the cleanup of supported
>> component
>> matrix.
>>
>> From [1] the latest release of Tajo is 0.11.3 which was out on
>> 2016-05-18.
>> Since then there're no further release. Similarly on Hama side the
>> latest
>> release is on Jan 28, 2016 [2]. Apex is on Attic so there's no chance to
>> get new release further [3].
>>
>> Though we'd like to support as many projects as possible, there's simply
>> not enough effort and resource to do it. Dropping them can also let
>> us more
>> focus on what's valuable to the users. What do you think?
>>
>> Kengo Seki
>> As 1.5 RM what do you think? I think if the discussion is positive this
>> will be in 1.5 release.
>>
>> [1] https://tajo.apache.org/
>> [2] https://hama.apache.org/
>> [3] https://apex.apache.org/
>>
>> Evans
>>
Re: [DISCUSS] Drop Apache Tajo, Apache Hama, and Apache Apex
Posted by Konstantin Boudnik <co...@apache.org>.
Thanks for bringing this up, Evans!
I think this trimming makes total sense and we were through similar
discussions before. In fact there's a consensus that we simply can't
support all the projects that seem to be nice, especially those that
weren't been active in 3+ years.
I am in favor of trimming the stack down. Unless, there's a maintainer
in the community who wants to step up and help.
--
Regards,
Cos
On 3/16/20 1:05 PM, Evans Ye wrote:
> Hi folks,
>
> I'd like to raise the discussion about the cleanup of supported component
> matrix.
>
> From [1] the latest release of Tajo is 0.11.3 which was out on 2016-05-18.
> Since then there're no further release. Similarly on Hama side the latest
> release is on Jan 28, 2016 [2]. Apex is on Attic so there's no chance to
> get new release further [3].
>
> Though we'd like to support as many projects as possible, there's simply
> not enough effort and resource to do it. Dropping them can also let us more
> focus on what's valuable to the users. What do you think?
>
> Kengo Seki
> As 1.5 RM what do you think? I think if the discussion is positive this
> will be in 1.5 release.
>
> [1] https://tajo.apache.org/
> [2] https://hama.apache.org/
> [3] https://apex.apache.org/
>
> Evans
>