I think there are lot's of issues in the issue tracker that could
      be tackled, but at this point I am not sure about how to start.
      Are the discussions about the big bang namespace change already
      over? Is it even possible to add features in such a seemingly
      "namespace-change-only" release?
    What needs to be done to actually add a feature? Is a PR
      containing the spec and API changes enough? I guess a TCK test
      would have to be added as well? How is the decision made that a
      feature is added?
    It would be great if we could illustrate the process with a more
      or less simple issue(https://github.com/eclipse-ee4j/jpa-api/issues/163)
      so that people get a feeling for how the specification can be
      shaped.
    
      
      My suggestion is beginning to bootstrap the
        discussion here yourself by looking at and prioritizing the
        existing issues together. No need to wait for anyone to get that
        started.
      
      
      I have to admit though, I personally don't have
        many big ticket gaps in mind for JPA. The specification at this
        point feels pretty feature complete. I do know though that there
        are smaller scale enhancements that could be prioritized. Some
        of those the right end users could probably even implement by
        themselves.
      
      
      The biggest work I think is in DeltaSpike Data. I
        personally don't think that is an approach that should be
        standardized in JPA yet (too much room for innovation left and
        it is very opinionated).
      
      
      The only big ticket work I see in the future is
        non-blocking support. However it is far too early to standardize
        that here. That first needs to be sorted out at the Java SE and
        database levels.
      
      
      What do others think?
      
      
      Reza Rahman
      Principal Program Manager
      Java on Azure
      
      
      Please note views expressed here are my own as an
        individual community member and do not reflect the views of my
        employer.
      
      
      
        Sent via the
          Samsung Galaxy S7, an AT&T 4G LTE smartphone
       
      
      
      
        -------- Original message --------
        
        Date: 11/1/19 6:01 AM (GMT-05:00) 
        
        Subject: [jpa-dev] What's next for JPA? 
        
        
       
      
        Hi all,
        
        
        What
          are the current plans for the future versions of the JPA spec?
          
        
        
        
        When is
          the next version expected? 
        
        
        
        Is
          there a roadmap? 
        
        
        
        What
          features are being discussed?
        
        
          
            
              
                
                  
                  
                  Best regards,
                  Behrang Saeedzadeh
                  
                 
               
             
           
         
       
      
      
      _______________________________________________
jpa-dev mailing list
jpa-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jpa-dev