You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "A. Soroka" <aj...@virginia.edu> on 2017/02/01 14:58:41 UTC
Re: not sure if I am on track for release
Okay, I am _finally_ about to send the vote invitation, but I have one last question. The votes are normally called for 72 hours, but in this case, that would land the end on Saturday night, which is not a great schedule for participation. I'm not familiar enough with the the policies to know: is it legitimate for me to preemptively extend the deadline to Monday night to ensure that we get three complete, solid business days in there?
ajs6f
> On Jan 31, 2017, at 9:36 AM, Andy Seaborne <an...@apache.org> wrote:
>
> git is your friend!
>
> On 31/01/17 13:07, A. Soroka wrote:
>> Okay, cool, I'm back on track. Sorry this is taking so long-- first time jitters!
>>
>> ajs6f
>>
>>> On Jan 30, 2017, at 6:29 PM, Andy Seaborne <an...@apache.org> wrote:
>>>
>>>
>>>
>>> On 30/01/17 22:03, A. Soroka wrote:
>>>> I'm done a dry run of release now (several times, actually). The
>>>> versions in the release.properties file look good, e.g.:
>>>>
>>>> project.dev.org.apache.jena\:jena-iri=3.3.0-SNAPSHOT
>>>> project.rel.org.apache.jena\:jena-cmds=3.2.0
>>>>
>>>> i.e. all the project.rel versions are 3.2.0 (or Fuseki-appropriate
>>>> versions) and all the project.dev versions are 3.3.0-SNAPSHOT (or
>>>> 1.6.0-SNAPSHOT or 2.6.0-SNAPSHOT for Fuseki).
>>>>
>>>> BUT, the artifacts in target/ directories don't look right. They all
>>>> have SNAPSHOT versions, e.g. jena-3.2.0-SNAPSHOT-source-release.zip
>>>> or apache-jena-fuseki-2.5.0-SNAPSHOT.tar.gz.
>>>>
>>>> So the first question is: am I correct to think that this is wrong?
>>>> Those should be the real release versions (3.2.0 or 2.5.0), right?
>>>> And if this is wrong, is there some obvious thing I must have done to
>>>> go off like this? It has been almost a year since I used the Maven
>>>> release plugin, and I honestly remember very little of it.
>>>
>>>
>>> Same for me - target/*SNAPSHOT*
>>>
>>> The dry run does not modify the pom.xml, or any files in git. It just thinks about it and writes "pom.xml.tag" - that should be the pom that would be used for real.
>>>
>>> Andy
>>>
>>>>
>>>> ajs6f
>>>>
>>
Re: not sure if I am on track for release
Posted by Andy Seaborne <an...@apache.org>.
On 01/02/17 14:58, A. Soroka wrote:
> Okay, I am _finally_ about to send the vote invitation, but I have one last question. The votes are normally called for 72 hours, but in this case, that would land the end on Saturday night, which is not a great schedule for participation. I'm not familiar enough with the the policies to know: is it legitimate for me to preemptively extend the deadline to Monday night to ensure that we get three complete, solid business days in there?
>
That's fine - the RM gets to choose what they think is best. 72hr is a
minimum.
Andy
>
> ajs6f
>
>> On Jan 31, 2017, at 9:36 AM, Andy Seaborne <an...@apache.org> wrote:
>>
>> git is your friend!
>>
>> On 31/01/17 13:07, A. Soroka wrote:
>>> Okay, cool, I'm back on track. Sorry this is taking so long-- first time jitters!
>>>
>>> ajs6f
>>>
>>>> On Jan 30, 2017, at 6:29 PM, Andy Seaborne <an...@apache.org> wrote:
>>>>
>>>>
>>>>
>>>> On 30/01/17 22:03, A. Soroka wrote:
>>>>> I'm done a dry run of release now (several times, actually). The
>>>>> versions in the release.properties file look good, e.g.:
>>>>>
>>>>> project.dev.org.apache.jena\:jena-iri=3.3.0-SNAPSHOT
>>>>> project.rel.org.apache.jena\:jena-cmds=3.2.0
>>>>>
>>>>> i.e. all the project.rel versions are 3.2.0 (or Fuseki-appropriate
>>>>> versions) and all the project.dev versions are 3.3.0-SNAPSHOT (or
>>>>> 1.6.0-SNAPSHOT or 2.6.0-SNAPSHOT for Fuseki).
>>>>>
>>>>> BUT, the artifacts in target/ directories don't look right. They all
>>>>> have SNAPSHOT versions, e.g. jena-3.2.0-SNAPSHOT-source-release.zip
>>>>> or apache-jena-fuseki-2.5.0-SNAPSHOT.tar.gz.
>>>>>
>>>>> So the first question is: am I correct to think that this is wrong?
>>>>> Those should be the real release versions (3.2.0 or 2.5.0), right?
>>>>> And if this is wrong, is there some obvious thing I must have done to
>>>>> go off like this? It has been almost a year since I used the Maven
>>>>> release plugin, and I honestly remember very little of it.
>>>>
>>>>
>>>> Same for me - target/*SNAPSHOT*
>>>>
>>>> The dry run does not modify the pom.xml, or any files in git. It just thinks about it and writes "pom.xml.tag" - that should be the pom that would be used for real.
>>>>
>>>> Andy
>>>>
>>>>>
>>>>> ajs6f
>>>>>
>>>
>