apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vlad Rozov <v.ro...@datatorrent.com>
Subject Re: master branch in place of devel-3
Date Fri, 22 Jan 2016 00:55:38 GMT
If I remember correctly the idea behind using master and devel-3/devel-4 
was to use devel-3 and devel-4 for trunks on 3.x and 4.x and use master 
as the latest released version.

I am not proposing to use master one way or another, just stating my 
understanding behind the current configuration of the Apex core and 
malhar branches.

Thank you,


On 1/21/16 15:18, Thomas Weise wrote:
> It my be possible but I would question why. The master branch does not
> serve any other purpose, so why not use it for development?
> On Thu, Jan 21, 2016 at 2:58 PM, Vlad Rozov <v.rozov@datatorrent.com> wrote:
>> I guess not, I think that we don't have admin rights to manage apex core
>> or malhar mirrors on github.
>> Thank you,
>> Vlad
>> On 1/21/16 14:12, Pramod Immaneni wrote:
>>> Can't we set a default branch in the repo to be different from master?
>>> On Thu, Jan 21, 2016 at 2:04 PM, David Yan <david@datatorrent.com> wrote:
>>> Hi all,
>>>> We have been using the devel-3 branch for development in both Apex Core
>>>> and
>>>> Apex Malhar.  The reason was that we wanted to have the master branch to
>>>> point to the latest release so that when a user checks out from our git
>>>> repo, it's always the latest source release and it always works.
>>>> But on the other hand, from what I see, that is not what most active
>>>> apache
>>>> projects do.  I checked Flink, Spark, Storm, Samza, Pig, Hive, and
>>>> Hadoop,
>>>> and ALL of these projects have commits on the master branch that are at
>>>> most one day old.  Apex Core on the other hand, the last commit on the
>>>> master branch was Nov, 2015, and that was when we released Apex Core
>>>> 3.2.0.
>>>> Because of our stale master branch, it's easy for someone outside of the
>>>> Apex community to conclude that Apex is not very active compared to other
>>>> Apache projects.
>>>> To me, the benefits of using the devel-3 branch are simply not worth the
>>>> potential cost.  I would like to propose that we get rid of the devel-3
>>>> branch and use the master branch for development, instead of having the
>>>> master branch always reflecting the latest release.  We use tags for that
>>>> purpose.
>>>> Please share your thoughts.
>>>> Thanks!
>>>> David

View raw message