+1.

Colin

On Fri, Dec 27, 2019 at 12:29 PM Guozhang Wang <guozh...@confluent.io>
wrote:

> Hmm, I think that's pushed by someone by mistake, we can delete it.
>
>
> Guozhang
>
>
> On Thu, Dec 26, 2019 at 12:18 PM Matthias J. Sax <matth...@confluent.io>
> wrote:
>
>> Should we delete `master` ? (Was not even aware it exists...)
>>
>>
>> -Matthias
>>
>> On 12/25/19 9:50 AM, M. Manna wrote:
>> > +1 with what  John mentioned.
>> >
>> > Master is more like a template that gets created for new repo. It’s not
>> in
>> > use for any Kafka activities (not that we know of).
>> >
>> > Regards,
>> >
>> >
>> > On Wed, 25 Dec 2019 at 17:04, John Roesler <vvcep...@apache.org> wrote:
>> >
>> >> Hi Sachin,
>> >>
>> >> Trunk is the basis for development. I’m not sure what master is for, if
>> >> anything. I’ve never used it for anything or even checked it out.
>> >>
>> >> The numbered release branches are used to develop patch releases.
>> >>
>> >> Releases are created from trunk, PRs should be made against trunk, etc.
>> >>
>> >> Thanks for asking!
>> >> John
>> >>
>> >> On Wed, Dec 25, 2019, at 08:54, Sachin Mittal wrote:
>> >>> Hello Folks,
>> >>> I just wanted to know what commits goes into what branch.
>> >>>
>> >>> I see trunk branch which seems default and latest.
>> >>> I also see master branch which seems bit behind trunk.
>> >>> I also see different versions branches like 2.2, 2.3 and 2.4 which are
>> >> also
>> >>> actively updated.
>> >>>
>> >>> I wanted to know when forking kafka repo, which is the branch one
>> should
>> >>> use base off to build from source or do any active development.
>> >>>
>> >>> What is the difference between between trunk and master branch?
>> >>> Also release branches are created from trunk or master branch?
>> >>>
>> >>> Also when issuing a pull request which is the general branch one
>> should
>> >> use
>> >>> as target?
>> >>>
>> >>> Thanks
>> >>> Sachin
>> >>>
>> >>
>> >
>>
>>
>
> --
> Thanks,
> Guozhang
>
> *Guozhang Wang | Software Engineer | Confluent | +1 607.339.8352
> <607.339.8352> *
>

Reply via email to