registry.quarkus.redhat.com should promote the 2.7 stream once it's available in addition to 2.2

[aloubyansky]

At least until 2.2 becomes officially not supported.

[gastaldi]

What 2.7 stream are you referring to? The community one? If so, isn't that supposed to be returned from registry.quarkus.io only?

Once the productized 2.7.x is out you'll get an output similar to what's displayed in https://registry.quarkus.io/client/platforms

{
  "platforms": [
    {
      "platform-key": "io.quarkus.platform",
      "name": "Quarkus Community Platform",
      "streams": [
        {
          "id": "2.6",
          "releases": [
            {
              "version": "2.6.3.Final",
              "member-boms": [
                "io.quarkus.platform:quarkus-bom::pom:2.6.3.Final",
                "io.quarkus.platform:quarkus-optaplanner-bom::pom:2.6.3.Final",
                "io.quarkus.platform:quarkus-kogito-bom::pom:2.6.3.Final",
                "io.quarkus.platform:quarkus-qpid-jms-bom::pom:2.6.3.Final",
                "io.quarkus.platform:quarkus-cassandra-bom::pom:2.6.3.Final",
                "io.quarkus.platform:quarkus-amazon-services-bom::pom:2.6.3.Final",
                "io.quarkus.platform:quarkus-camel-bom::pom:2.6.3.Final",
                "io.quarkus.platform:quarkus-hazelcast-client::pom:2.6.3.Final",
                "io.quarkus.platform:quarkus-debezium-bom::pom:2.6.3.Final",
                "io.quarkus.platform:quarkus-blaze-persistence-bom::pom:2.6.3.Final",
                "io.quarkus.platform:quarkus-google-cloud-services-bom::pom:2.6.3.Final"
              ],
              "quarkus-core-version": "2.6.3.Final"
            }
          ]
        },
        {
          "id": "2.7",
          "releases": [
            {
              "version": "2.7.0.CR1",
              "member-boms": [
                "io.quarkus.platform:quarkus-bom::pom:2.7.0.CR1",
                "io.quarkus.platform:quarkus-optaplanner-bom::pom:2.7.0.CR1",
                "io.quarkus.platform:quarkus-kogito-bom::pom:2.7.0.CR1",
                "io.quarkus.platform:quarkus-qpid-jms-bom::pom:2.7.0.CR1",
                "io.quarkus.platform:quarkus-cassandra-bom::pom:2.7.0.CR1",
                "io.quarkus.platform:quarkus-amazon-services-bom::pom:2.7.0.CR1",
                "io.quarkus.platform:quarkus-camel-bom::pom:2.7.0.CR1",
                "io.quarkus.platform:quarkus-hazelcast-client::pom:2.7.0.CR1",
                "io.quarkus.platform:quarkus-debezium-bom::pom:2.7.0.CR1",
                "io.quarkus.platform:quarkus-blaze-persistence-bom::pom:2.7.0.CR1",
                "io.quarkus.platform:quarkus-google-cloud-services-bom::pom:2.7.0.CR1"
              ],
              "quarkus-core-version": "2.7.0.CR1"
            }
          ]
        }
      ]
    }
  ]
}

[aloubyansky]

No, as the title says it's about registry.quarkus.redhat.com promoting the 2.7 product stream once it's available in addition to 2.2. Perhaps, that's a not an issue actually. But that's what we were talking about as a requirement. AFAIU, there should be a time window when both 2.2 and 2.7 should be available. Once 2.2 becomes unsupported (a couple of month), it should probably get unlisted, leaving only 2.7 as the recommended stream.

[gastaldi]

One option is to completely remove the unsupported platform release from the registry, but I am not sure if that is desired.

Another option is to introduce a column in the platform_release (or the platform_stream) table indicating if it's visible

[gastaldi]

I created #72 introducing a new unlisted column in platform streams. This will provide the ability to hide streams from the queries when they are no longer needed.