[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [rdf4j-dev] Next patch release and new committers
|
You can also use the japicmp reports to verify specific 2.2/2.3 API
compatibility on the modules that it is enabled for by changing the
compare version to 2.2:
https://github.com/eclipse/rdf4j/blob/master/pom.xml#L167
Then running mvn verify, then checking for the various reports in
target/japicmp in the modules it is setup for, and adding it to others
that you want to preserve the public API for.
I didn't set it up to error the build, but you can also tell it to do
that to highlight if there are issues
(breakBuildBasedOnSemanticVersioning /
breakBuildOnSourceIncompatibleModifications /
breakBuildOnBinaryIncompatibleModifications):
https://siom79.github.io/japicmp/MavenPlugin.html
https://github.com/eclipse/rdf4j/blob/master/pom.xml#L712
Cheers,
Peter
On 26 April 2017 at 15:50, Håvard Ottestad <hmottestad@xxxxxxxxx> wrote:
> James, have you done any checks for backwards compatibility? Like running all the test code in 2.2 against the new cherry picked branch?
>
> Håvard
>
>> On 25 Apr 2017, at 17:37, James Leigh <james.leigh@xxxxxxxxxxxx> wrote:
>>
>> Please disregard my last message, I see that it is already there.
>>
>> Thanks!
>> James
>>
>>> On Tue, 2017-04-25 at 11:33 -0400, James Leigh wrote:
>>> Thanks Havard,
>>>
>>> Can you also include this issue?
>>> * #764 Include additional headers in sesame session requests
>>>
>>> Regards,
>>> James
>>>
>>>> On Fri, 2017-04-21 at 18:01 +0200, Håvard Ottestad wrote:
>>>> I just copied all those into a branch on rdf4j. I have write access
>>>> now :)
>>>>
>>>>
>>>> Was it correct to use "git cherry-pick -m 1 <commit sha1>" ?
>>>>
>>>>
>>>> https://github.com/eclipse/rdf4j/tree/releases/2.2.1
>>>>
>>>>
>>>>
>>>> Håvard
>>>>
>>>>
>>>>
>>>> On Wed, Apr 19, 2017 at 11:36 PM, James Leigh
>>>> <james.leigh@xxxxxxxxxxxx> wrote:
>>>> I'm still waiting for github permissions to eclipse/rdf4j. In
>>>> the
>>>> meantime I've put together a branch that I think contains the
>>>> relevant
>>>> issues[1]. The issues I think are ready are as follows:
>>>>
>>>> * #803: Added check for the SailChangedEvent
>>>> statementsAdded and
>>>> statementsRemoved flags
>>>> * #792: Encode dollar sign in repository template
>>>> replacement
>>>> * #787: CookieHandlers now check for empty context path
>>>> string
>>>> instead of null
>>>> * #786: Catch NumberFormatException when checking server
>>>> protocol
>>>> * #781: Use hashCode of PathIteration to identify
>>>> intermediate
>>>> variables
>>>> * #759 : Use fixed Locale.ENGLISH for XML error
>>>> verification
>>>> * #754: Fix serialisation of language tag in toSPARQL.
>>>> * #751: added benchmark module to root pom
>>>> * #747: Don't encode literals in quotes unless needed
>>>> * #695: Don't treat path modifiers as subqueries
>>>> * #637: Prompt user if using incompatible chars in
>>>> repository ID
>>>>
>>>> [1]
>>>> https://github.com/jamesrdf/rdf4j/releases/tag/2.2.1-SNAPSHOT
>>>>
>>>> Regards,
>>>> James
>>>>
>>>>
>>>>> On Wed, 2017-04-19 at 22:03 +0200, Håvard Ottestad wrote:
>>>>> Jeen wants James and I to cherry pick and set up a bug fix
>>>> release.
>>>>>
>>>>> Any other bug fixes that are critical?
>>>>>
>>>>> Håvard
>>>>>
>>>>>> On 19 Apr 2017, at 09:57, Damyan Ognyanov
>>>> <damyan.ognyanov@xxxxxxxxxxxx> wrote:
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> for the next version (8.2) of our GraphDB, we are planning
>>>> to move up from 2.1.6 but since the latest 2.2 release had
>>>> some bugs (#781 #764, etc.) that already have been fixed in
>>>> the master, we are aiming to use the upcoming 2.2.1 ...
>>>>>>
>>>>>>
>>>>>> so it would be good to have that patch release sooner,
>>>> e.g. somewhere in next 2 weeks ...
>>>>>>
>>>>>> Best,
>>>>>> Damyan
>>>>>> _______________________________________________
>>>>>> 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
> _______________________________________________
> 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
