Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakartaee-platform-dev] [External] : Re: Jakarta 10.1?

We should consider a plan on service release of TCK's with updates to not use the security manager. IMO, we should avoid a complete release cycle of Jakarta EE, for update on not using security manager.


From: jakartaee-platform-dev <jakartaee-platform-dev-bounces@xxxxxxxxxxx> on behalf of Scott Marlow <smarlow@xxxxxxxxxx>
Sent: 08 October 2022 21:34
To: jakartaee-platform developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
Subject: [External] : Re: [jakartaee-platform-dev] Jakarta 10.1?

On Sat, Oct 8, 2022, 9:42 AM Emily Jiang via jakartaee-platform-dev <jakartaee-platform-dev@xxxxxxxxxxx> wrote:
I also support the idea of working on the task of fixing the SecurityManager asap without doing Jakarta EE 10.1 for this particular change because this release hasn’t brought much functionality update for the end users but adding a lot of work to go through the overall release process. +1 on tracking this activity across the board using a milestone. We can even define a deadline for this task.

+1 for someone creating a pull request against the tcks for this.  We can do a service release for this!



Sent from my iPhone

> On 7 Oct 2022, at 20:43, David Blevins <dblevins@xxxxxxxxxxxxx> wrote:
>> On Oct 7, 2022, at 1:58 PM, Ondro Mihályi <mihalyi@xxxxxxxxxxx> wrote:
>> I like the idea of milestone releases to get to Jakarta EE 11 step by step. But it would require that all individual specs also create milestone releases so that everything is aligned together. And I don't think that's feasible if milestone releases are too frequent. I think we could manage a milestone release every 3-6 months but not more often. But why not try that? E.g. with a milestone scheduled for Q1/2023 that aims for dropping SecurityManager, require Java 17 and support Java 18 or newer?
> Milestones would certainly be welcome if project's are up for it.  I know Scott Stark, Kevin and I have mentioned in Spec Committee discussions that these would really help the process.
> We have done a few, and some of them did have deadlines associated with them, but there could be value in some regularity.  I think one of the reasons we don't do them very frequently is deciding anything in a large community takes time, so if we're deciding each milestone one at a time, it means they don't frequently happen.
> It might be smart to pick a frequency, try it out for a year and revisit at this same time next year.
> We could even make it one of our goals in the 2023 program plan which is due in early November.
> -David
> PS Thank you Arjan for starting this tread -- it's a really fantastic discussion.
> _______________________________________________
> jakartaee-platform-dev mailing list
> jakartaee-platform-dev@xxxxxxxxxxx
> To unsubscribe from this list, visit
jakartaee-platform-dev mailing list
To unsubscribe from this list, visit

Back to the top