[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
| 
Re: [microprofile-wg] [BALLOT][MicroProfile 6.0] Specification - Release Review - VOTE by Dec 6th (2 weeks)
 | 
  
    0 (iJUG)
    
    
    Why:
    As mentioned in the plan review
      already, I think the current way to build the MP platform release
      creates potential issues, as only the MP platform CI tests the
      included component specs with the Jakarta 10 Core Profile base
      line - as mentioned here we should think about releasing multiple
      versions with different Jakarta EE base versions and requirements
      in the future: 
https://github.com/eclipse/microprofile/issues/295 
    With this release, this is only partly
      solved with the major release of MP Metrics and new addition of MP
      Telemetry, the rest of the specs adds support for it only without
      trying to break anything and somehow running the tests hopefully
      with the new baseline too. Instead this could (and should) be
      ensured with two separate artifacts representing the different
      base lines defining the environment of use in the future.
    
    
    
    
    
    Additional small findings in spec
      document:
    
    
    - Typo in architecture section:
      OpenTelemetry is written without space in between.
    - Outdated MP Fault Tolerance statement
      in it's section: "Fault Tolerance 3.0 is now dependent on Jakarta
      EE 8 technologies." -> should be deleted.
    - Typo in MP Telemetry section: the 2nd
      telemetry should start with a lower case - but we may find a
      better description in this section at all in the future.
    
    
    
    I will create an issue for these soon.
    
    
    As mentioned in the MP Metrics ballot
      already, I think MP Metrics is a valid part of the platform for
      now, as OpenTelemtry Metrics is not in an equivalent state and it
      could be based on it - so dropping it now would be not an option
      and the request for making it optional came very late and external
      TCK dependencies to it could not be solved in time.
    My vote so goes in the opposite
      direction as Red Hat's and Tomitribe's cause here.
    
    But both reasons could be addressed in
      a future release hopefully.
    
    
    Thanks,
    Jan
    
    
    
    
    
    Am 22.11.22 um 22:03 schrieb Emily
      Jiang via microprofile-wg:
    
    
      
      To approve and ratify the Release Review of
        MicroProfile 6.0, the Steering Committee Representatives vote is
        requested. Please respond with +1 (positive), 0 (abstain), or -1
        (reject).  Any feedback that you can provide to support your
        vote will be appreciated. 
        
        The 
MicroProfile
          Specification Process requires the Specification Committee
        and the Community to provide feedback during the approval
        process using the relevant documents:
        
        
        
        This ballot will be fourteen days, ending on Tuesday, December
        6th.  However, it will be great if you can vote before December
        2nd. The ballot requires a Super-majority positive vote of the
        Steering Committee members.  There is no veto. Community input
        and Community votes are welcomed. However, only the votes
        delivered by Steering Committee Representatives will be counted.
        
--
        Thank you
        Emily
          Jiang on behalf of the MicroProfile Steering Committee
       
      
      
      _______________________________________________
microprofile-wg mailing list
microprofile-wg@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/microprofile-wg