Thanks for taking care of this, Werner -- I hadn't thought about
labels/tags at all.
I don't think there were any deltas in the spec other than the
asciidoctor fixes and your updates to version numbers, etc., but if you
want to label the precise commit that I published from, it's
218937242b464d266f30a893a46eba7a6557bd96.
I agree with your proposal for uniform labeling across spec, api, and ri
repositories for upcoming milestones.
Will
On 03/31/2017 06:17 PM, Werner Keil wrote:
> I'll ask him if he wants.
>
> Btw, noticed especially because we're reminded in the EC on a regular
> basis, that EDR 1 is already ongoing for about 2 weeks. A little late,
> hopefully not too many deltas, but I tagged it
> https://github.com/javaee-security-spec/security-spec/releases/tag/edr1
> to pinpoint the spec sources, too. The POM said 1.0-edr as version, it
> is not really visible in the generated PDF (especially since I assume
> it was generated directly with Asciidoc in that case) but not bad to
> mention the stage there just in case.
>
> I'll set it to "1.0-SNAPSHOT" till a next stage is published. Please
> let's try to add more release tags then if possible ;-)
>
> As the API or RI and TCK were not part of the EDR (they can, but don't
> have to at this stage) it seems OK to use other version schemes like
> "m03" or "m03-SNAPSHOT" for the time being. Maybe for Public Review it
> could not hurt to label spec and other artifacts accordingly.
>
> Kind Regards,
> Werner
>
>
> On Fri, Mar 31, 2017 at 11:10 PM, Will Hopkins
> <will.hopkins_at_oracle.com <mailto:will.hopkins_at_oracle.com>> wrote:
>
> I'm not the expert, but it seems reasonable to me. The reason I
> asked for him to join as a contributor was for visibility -- it
> may be legally permissible for him to contribute, but he's not
> listed as a contributor, and if he's not on the users list I have
> no way to communicate with him. If he's going to contribute, he
> may as well join the EG and be part of the conversation.
>
>
> On 03/31/2017 05:00 PM, Werner Keil wrote:
>> Thanks for sharing, then 375 should be able to accept them likewise.
>>
>> Kind Regards,
>> Werner
>>
>>
>> On Fri, Mar 31, 2017 at 10:59 PM, arjan tijms
>> <arjan.tijms_at_gmail.com <mailto:arjan.tijms_at_gmail.com>> wrote:
>>
>> For the record, Oracle led JSR 372 which just went final
>> accepted a number of contributions from community members who
>> signed the OCA.
>>
>>
>> On Fri, Mar 31, 2017 at 10:52 PM, Werner Keil
>> <werner.keil_at_gmail.com <mailto:werner.keil_at_gmail.com>> wrote:
>>
>> I'll ask him. Other than that, is the OCA fine for API,
>> RI and TCK or Spec contributions should he or someone in
>> a similar situation only want to sign that?
>>
>>
>> On Fri, Mar 31, 2017 at 10:46 PM, Will Hopkins
>> <will.hopkins_at_oracle.com
>> <mailto:will.hopkins_at_oracle.com>> wrote:
>>
>> Can you also ask him to join the JSR as a contributor
>> at the JCP page? That way, he'll be officially listed
>> as a contributor to the JSR.
>>
>>
>> On 03/28/2017 08:56 AM, arjan tijms wrote:
>>> Ok, good
>>>
>>> On Tue, Mar 28, 2017 at 2:56 PM,
>>> <werner.keil_at_gmail.com
>>> <mailto:werner.keil_at_gmail.com>> wrote:
>>>
>>> Yes, he mentioned.
>>>
>>> If this is fine for both API and RI, he should
>>> be OK.
>>>
>>> Kind Regards,
>>>
>>> Werner
>>>
>>> *From: *arjan tijms <mailto:arjan.tijms_at_gmail.com>
>>> *Sent: *Tuesday, March 28, 2017 14:39
>>> *To:
>>> *jsr375-experts_at_javaee-security-spec.java.net
>>> <mailto:jsr375-experts_at_javaee-security-spec.java.net>
>>> *Subject: *[jsr375-experts] Re: Contributors to
>>> JSR375?
>>>
>>> Hi,
>>>
>>> Guillermo signed the OCA.
>>>
>>> See:
>>> http://www.oracle.com/technetwork/community/oca-486395.html
>>> <http://www.oracle.com/technetwork/community/oca-486395.html>
>>>
>>> Entry: Guillermo Gonzalez de Agüero - Soteria
>>>
>>> Kind regards,
>>>
>>> Arjan Tijms
>>>
>>> On Tue, Mar 28, 2017 at 2:31 PM, Werner Keil
>>> <werner.keil_at_gmail.com
>>> <mailto:werner.keil_at_gmail.com>> wrote:
>>>
>>> Dear Experts,
>>>
>>> Rudy also mentioned he saw commits by
>>> Guillermo (GH user: ggam) to Soteria and the
>>> JSR 375 API when we met during JavaLand lunch.
>>>
>>> At the moment Guillermo does not show as
>>> either EG Member or Contributor via
>>> Adopt-a-JSR. If he has not already requested
>>> to join as Associate/Contributor, please
>>> don't forget GitHub lists the person who
>>> proposed a PR as author and from an IP
>>> perspective he/she also owns the contribution.
>>>
>>> Especially since it is an Oracle led JSR and
>>> supposed to be part of the Java EE Platform,
>>> everyone should at least join as Associate
>>> to help as a contributor or sign the OCA if
>>> they prefer that.
>>>
>>> Thanks and Regards,
>>>
>>>
>>> Werner
>>>
>>>
>>
>> --
>> Will Hopkins | WebLogic Security Architect |+1.781.442.0310 <tel:+1%20781-442-0310>
>> Oracle Application Development
>> 35 Network Drive, Burlington, MA 01803
>>
>>
>>
>>
>
> --
> Will Hopkins | WebLogic Security Architect |+1.781.442.0310 <tel:+1%20781-442-0310>
> Oracle Application Development
> 35 Network Drive, Burlington, MA 01803
>
>
--
Will Hopkins | WebLogic Security Architect | +1.781.442.0310
Oracle Application Development
35 Network Drive, Burlington, MA 01803