Re: [rdf4j-dev] What is develop branch?

[Jacek Grzebyta <grzebyta.dev@xxxxxxxxx>]

Thanks for explanations.

Best regards,
Jacek

On 18 May 2017 at 13:55, James Leigh <james.leigh@xxxxxxxxxxxx> wrote:
> Thanks Peter for your explanation. More details can be found in the
> developer guide[1].
>
> What we previously used the master branch for is now going to use the
> develop branch. So if you want to compile the latest version use the
> develop branch.
>
> Any fixes that should go into a patch release should branch from
> master. The master branch is going to be a stale version of the develop
> branch, forked prior to the minor version number being incremented,
> with all subsequent bug fixes merged in. This will make it easier to do
> a patch release as all the fixes will already be merged in.
>
> Regards,
> James
>
> [1] http://docs.rdf4j.org/developer/
>
>
>
> On Wed, 2017-05-17 at 09:13 +1000, Peter Ansell wrote:
>> It doesn't discuss what to do for API breaking major release
>> features,
>> but tracking develop, as the latest branch, would probably be the
>> best
>> idea.
>>
>> Cheers,
>>
>> Peter
>>
>> On 17 May 2017 at 09:07, Jacek Grzebyta <grzebyta.dev@xxxxxxxxx>
>> wrote:
>> >
>> > Hi,
>> >
>> > I so it means my PR 739 is rather for next major release. Should I
>> > merge develop into that or keeping with master is OK?
>> >
>> > Cheerio,
>> > Jacek
>> >
>> > On 16 May 2017 at 23:55, Peter Ansell <ansell.peter@xxxxxxxxx>
>> > wrote:
>> > >
>> > > Hi Jacek,
>> > >
>> > > See James' changes to the workflow which introduced the develop
>> > > branch:
>> > >
>> > > https://github.com/eclipse/rdf4j-doc/blob/master/doc/developer/in
>> > > dex.adoc
>> > >
>> > > Basically, branch from develop for the next minor release, and
>> > > master
>> > > for the next patch release.
>> > >
>> > > Cheers,
>> > >
>> > > Peter
>> > >
>> > > On 17 May 2017 at 08:27, Jacek Grzebyta <grzebyta.dev@xxxxxxxxx>
>> > > wrote:
>> > > >
>> > > > Hi,
>> > > >
>> > > > I looked at eclipse/rdf4j and found that new branch `develop`
>> > > > exists.
>> > > > I just wanted to know if that branch should be a starting point
>> > > > for
>> > > > changing API PRs or still master branch is for that?
>> > > >
>> > > > Thanks,
>> > > > Jacek
>> > > > _______________________________________________
>> > > > rdf4j-dev mailing list
>> > > > rdf4j-dev@xxxxxxxxxxx
>> > > > To change your delivery options, retrieve your password, or
>> > > > unsubscribe from this list, visit
>> > > > https://dev.eclipse.org/mailman/listinfo/rdf4j-dev
>> > > _______________________________________________
>> > > rdf4j-dev mailing list
>> > > rdf4j-dev@xxxxxxxxxxx
>> > > To change your delivery options, retrieve your password, or
>> > > unsubscribe from this list, visit
>> > > https://dev.eclipse.org/mailman/listinfo/rdf4j-dev
>> > _______________________________________________
>> > rdf4j-dev mailing list
>> > rdf4j-dev@xxxxxxxxxxx
>> > To change your delivery options, retrieve your password, or
>> > unsubscribe from this list, visit
>> > https://dev.eclipse.org/mailman/listinfo/rdf4j-dev
>> _______________________________________________
>> rdf4j-dev mailing list
>> rdf4j-dev@xxxxxxxxxxx
>> To change your delivery options, retrieve your password, or
>> unsubscribe from this list, visit
>> https://dev.eclipse.org/mailman/listinfo/rdf4j-dev
> _______________________________________________
> rdf4j-dev mailing list
> rdf4j-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/rdf4j-dev