Re: [rest-dev] Github Issue Tracking

[Jim Krueger <jckofbyron@xxxxxxxxx>]

+1: totally agree.

I was holding off on requesting the creation of  a 3.2 project until enough progress had been made on the release-3.2 branch to instill confidence that a 3.2 release with @Context deprecated (which would require a working alternative CDI-centric implementation) was feasible within the newly adjusted Jakarta EE11 schedule.    

How about labeling the 3.2 issues with “3.2” in the interim?

On Jan 27, 2024, at 3:08 AM, Markus Karg via rest-dev <rest-dev@xxxxxxxxxxx> wrote:

To have a better overview over all the new issues opened regarding 3.2, @Context replacement, etc. I would propose that we let us help from Github:

* Anything related to replacing @Context etc. (unrelated to any specific target version) should be labelled by "@Context" etc.

* Anything planned for inclusion in 3.2 should be moved into the 3.2 project. This includes moving issues from 4.0 to 3.2 project.

* …

 

WDYT?

 

-Markus

_______________________________________________
rest-dev mailing list
rest-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://accounts.eclipse.org