Hi, I was looking over the following issues:
1)
https://github.com/jakartaee/faces/issues/1707 specifically the comment here:
https://github.com/jakartaee/faces/issues/1707#issuecomment-16466382752)
https://github.com/jakartaee/faces/issues/1830
From a Faces perspective, it does not look as though we can deprecate something in 4.1 and then plan to remove it in 5.0 because 4.1 is not part of the Platform specification or its profiles.
There was recently an email on the spec mailing list:
https://www.eclipse.org/lists/jakarta.ee-spec/msg03023.html. The important part of the linked doc relating
to the above issues is:
"This process covers the Platform specification, its profiles, and the Component specifications that constitute them. Because of the capability for Component specifications to potentially release at a quicker cadence to the Platform and its profiles, it should be clarified that the Platform specification and its profiles are not allowed to “jump” a Component specification release to introduce breaking changes without first deprecating the feature/behaviour in the Platform specification and its profiles. This is to discourage a Component specification quickly doing two or more back-to-back releases to quickly remove a feature. See the Platform Feature section for further details."
For issue #1830 that means we can only remove something in 5.0 (EE11) that was previously deprecated in 4.0 (EE10) but not in 4.1.
I wanted to bring this up for discussion on the mailing list to ensure the entire Faces team was aware.
Regards,
Paul Nicolucci
