[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
| 
Re: [jakarta.ee-spec.committee] [External] : Re: Clarification regarding EMO checklists for Release Reviews?
 | 
  
    Maria
    OK. So, we should allow the EMO office to tick-off all the items
      on those lists. 
    Thanks,
    -- Ed
    
    On 5/23/2024 11:19 AM, Eclipse
      Management Office EMO wrote:
    
    
      
      Hi Ed, 
        
the short answer is that EMO is trying to avoid duplicating
          review records. 
        Usually when a project plans for a release/progress review,
          they contact EMO to initiate the review which is done and
          tracked using a GitLab issue.
        Since the engagement in GitLab was rather low in the past,
          we thought it might be better to interact directly with the
          projects in the release PRs.
        The checklist provided by EMO is supposed to be filled by
          EMO as well. We take into consideration the ballot status and
          PMC communications and summarize everything into our
          checklist.
        This has been an experiment, and is something that we
          implemented recently, so any suggestions you or the community
          might have are more than welcome.
        Kind regards,
        Maria Teresa
       
      
      
        
        Hi
          there,
          
          I notice that the EMO is providing checklists for
          Specification PRs. 
          Could the EMO clarify who is responsible for filling in and
          reviewing 
          the items on these check-lists? The PR submitter, the
          specification team 
          mentor, or is this to be left for the EMO?
          
          Thanks,
          
          -- Ed
          
        
       
      
      
      
      -- 
      
        
          The Eclipse Management Organization
                |
            Eclipse
              Foundation