MicroProfile 2020 releases and Jakarta EE9

[Emily Jiang]

Just thought to kick off a discussion on our roadmap for 2020 releases so that individual specifications can plan their potential major releases.

1. Feb release: I think we would like to use this release to consume Jakarta EE8 and remain as a minor release. Therefore, no backward incompatible changes are allowed.

2. June release: it will be one year since the last major release. How about mark this a major release so that individual specs can start planning their major releases accordingly?

3. October release: this should be a minor release.

However, if Jakarta EE9 is released and a couple of runtime passes the TCKs, we should consider consuming Jakarta EE9 in this release. As a consequence, this will be a major release. If this is the case, we will have 2 major releases in a year. However, I suggest MicroProfile specs should not reintroduce any backward incompatible changes to muddy the water. I don't see this is an issue as this is just an one-off release.

Basically, if we agree to still make June release a major release, MicroProfile Fault Tolerance and Config spec can plan the backward incompatible changes in June release, as well as other MP Specs.

Thoughts?

Emily

[Ken Finnigan]

I think it makes sense for specifications to target breaking changes for an MP release in June, but we may decide closer to that time to delay a major release until October if Jakarta EE 9 is likely to be available.

If possible, it would be good to avoid two breaking change releases in one year.

--
You received this message because you are subscribed to the Google Groups "Eclipse MicroProfile" group.
To unsubscribe from this group and stop receiving emails from it, send an email to microprofile...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/microprofile/3772f830-57c5-44e2-867e-62b1f4b1fc14%40googlegroups.com.