Re: [ee4j-pmc] Jakarta Activation 1.2.2, XML Binding 2.3.3 and XML Web S

["Kevin Sutter" <sutter@xxxxxxxxxx>]

Bill,
Since these other
projects are contained in the same Eclipse Project, it doesn't make any
sense to duplicate the effort of scanning and the iplog reviews from an
Eclipse process viewpoint.  We ran into this same condition with MicroProfile.
 Since all of our components are contained within the same MicroProfile
project, all of the github repos are referenced when creating the iplogs
and the scanning of the code.  So, we only submit the top-level MicroProfile
project for review and the other component reviews are implied or included.
 MicroProfile is kind of a special beast since everything is contained
within a single Eclipse project.

Lukas has a similar
condition but at a smaller scale.  Three of these components are contained
in the single XML Web Services Project -- XML Web Services, Web Services
Metadata, and SOAP Attachments.  Thus, there is only need for a single
iplog and code scan and Eclipse review for all three.  I'm pretty
sure this is what Lukas was referring to.

We still need
to do the full Spec reviews which we are doing via the PRs.

Hope this helps.

---------------------------------------------------
Kevin Sutter 
STSM, MicroProfile and Jakarta EE architect @ IBM
e-mail:  sutter@xxxxxxxxxx     Twitter:  @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)    
LinkedIn: https://www.linkedin.com/in/kevinwsutter



From:
       Bill
Shannon <bill.shannon@xxxxxxxxxx>
To:
       EE4J
PMC Discussions <ee4j-pmc@xxxxxxxxxxx>, Lukas Jungmann <lukas.jungmann@xxxxxxxxxx>
Date:
       02/04/2020
17:34
Subject:
       [EXTERNAL]
Re: [ee4j-pmc] Jakarta Activation 1.2.2, XML Binding 2.3.3 and XML Web
Services 2.3.3 release review
Sent
by:        ee4j-pmc-bounces@xxxxxxxxxxx

---

Lukas Jungmann wrote on 2/4/20 6:49
AM:
> On 2/4/20 3:07 PM, Kevin Sutter wrote:
>> +1 from me.  Thanks, Lukas!
>>
>> Question:  What about SOAP attachments and Web Services Metadata?
 Will those
>> be coming on a later request?
> 
> they are supposed to be covered by 'Jakarta XML Web Services 2.3.3'
which is
> top-level project for both + Jakarta XML Web Services itself (to not
spam
> everyone that much with copy-pasted stuff). For the next major version,
release
> records were already splited up to allow separate evolution of each
part in the
> future.

They're separate specs, they need to be approved separately.
They should be considered part of this bundle of requests.

Lukas, please provide the release review details.

_______________________________________________
ee4j-pmc mailing list
ee4j-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://www.eclipse.org/mailman/listinfo/ee4j-pmc