"Change Namespace" could be understood as "Replace Namespace", hence I am always a friend of explicit listing the allowed/disallowed actions. And "guess" is a really bad word in this context. ;-) BTW, "adding/removing packages" is not obvious, as per the Java Language Specification namespaces do not exists, and packages are *not* hierarchical. So technically it is undefined what "adding/removing packages to a namespaces" means in Java. -Markus From: ee4j-pmc-bounces@xxxxxxxxxxx [mailto:ee4j-pmc-bounces@xxxxxxxxxxx] On Behalf Of Ivar Grimstad
Sent: Donnerstag, 4. April 2019 19:22
To: EE4J PMC Discussions
Subject: Re: [ee4j-pmc] Updated PMC Statement for work on Jakarta EE Specification Projects Somebody will probably correct me here, but my understanding of "change" in this context is: - adding/removing or changing signatures of exposed methods in existing classes/interfaces - adding/removing packages I guess, anything except fixing bugs at this point. I don't want to be nitpicking but if you want to make it bullet-proof you need to declare what "change" means. -Markus A little clarification. See inlined below. We have updated the PMC statement regarding work on the Jakarta EE Specification projects. - Must be able to release a Jakarta EE 8 artifact (minimal changes from the previous release) - Must be able to merge the Jakarta EE 8 related changes into the master branch after release - Must NOT publicly publish SNAPSHOTs or other releases that include the javax.* namespace (yet)
- Must NOT publicly publish SNAPSHOTs or releases that change the javax.* namespace. Apart from the above, the development of new features is good to go!
_______________________________________________
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
|
