Remove 1.x, 2.0, 2.1, 3.0, 3.2, 4.0 MP versions from the Starter

[Emily-Jiang]

The version dropdown list is too long. Since this is a starter for generating new microservices, it does not make much sense to include the very old version of MP. In last week's hangout on 21st Feb, we have agreed to remove 1.x. We also suggested to only keep the latest 2 or 3 or 4 releases (2.2, 3.3, 4.1).

[Karm]

Hello,
@xstefank @rdebusscher @radcortez

Could you guys update https://wiki.eclipse.org/MicroProfile/Implementation for the latest WildFly (Martin), Quarkus (Roberto) and Payara (Rudy), please?

[rdebusscher]

Is that wiki still used since we now have the approved certification process based on published TCKs?

[Emily-Jiang]

@rdebusscher the wiki is still used. The certification is a formal process to claim for compatibility and then add the corresponding runtime to the wiki. In this case, one place to see all compatible impls as the issues raised for compatibility will be closed after the approval. It is difficult to see which runtimes support which MP versions. In the future, we will create a webpage to host the certification but it does not include standalone specs. Therefore, it is still good to keep the wiki.

[rdebusscher]

That is an idea but it will be confusing as it will be a mixture of certified runtimes and versions and non certified ones (mainly before MicroProfile became a Working group).
Are there already any of the CCR approved according the new TCK/compatibility process? As you mentioned, after certification is claimed, only then we can add the runtime.

[xstefank]

@Emily-Jiang then I don't understand what I should do in https://wiki.eclipse.org/MicroProfile/Implementation. Can I update it with the WildFly versions that have still open CCRs? I see that OL versions are also still having the CCRs open in https://github.com/microprofile/microprofile-wg/issues. So are we following the CCR process now and wiki is the official listing page of compatible implementations or we can just add the implementations there if we can prove that we passed the TCKs?

But I also agree with @rdebusscher. We should only have one place to list compatible implementations and adding implementations to this place should go through the certification process. What about leaving wiki for MP versions prior to the certification process being established and for the new implementations certified through the process create a new webpage at microprofile.io? Also, when do we say it was established? We have open CCRs for MP 5.0 and 4.1 so I propose to make the distinction there.

[Emily-Jiang]

Since the TCK process was standardised last week, we might just use the process to certify the runtimes and then add the correponding runtime to the wiki and the certification page on microprofile.io. We will discuss in today's call to reach concensus. By the way, in the past the wiki is pretty much non-certification driven from day one. We can refine the process.

[Karm]

@xstefank @radcortez Is it expected that I cannot see WildFly here?

https://microprofile.io/compatible/4-1/

[xstefank]

@Karm Working on the CCR right now.