| Re: [cu-dev] Release process for Concurrency 3.0 spec |
|
Hi Nathan, As you are a committer I think you can do those things which is why you get can get so far. I don’t remember a lot of the process. I see you have added Ed/Dmitry I think they are our mentors available
to us to help guide us through this part of the process. Steve From: Nathan Rauh <nathan.rauh@xxxxxxxxxx>
Given that we’re supplying the candidate for compatible implementation and have the information for it and the results and so forth, I’ve been trying to fill out some of the process for the
3.0 release based on this, and I’ve been surprised how far it seems to be letting me go without any additional authorization. Thus far I have the following two issues mostly filled out (some links within the checklists won’t be working until a week from now)
and it even allowed me to update the release record to replace the projected release date of last October with Feb 28 and to request a Generated IP Log, although I have no idea if I’ve done those things properly or if I should have included more information.
To any of you who know what you are doing with this sort of process, please review and correct or fill in parts that I have missed. I’m hoping that we will be able to check off the remaining boxes and submit the release review a week from now. If anyone
else would like to take over, I’d be happy to let them. Concurrency 3.0 release review issue: https://github.com/jakartaee/specifications/pull/449 Concurrency 3.0 compatibility certification request issue: https://github.com/eclipse-ee4j/jakartaee-platform/issues/464 |