Yes, anything that would make it incompatible with the corresponding
Java EE specification.
Ivar Grimstad wrote on 4/4/19 10:21 AM:
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.
Ivar
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
_______________________________________________
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
|
