snowdrop / team

Repository hosting daily tasks, general information, wiki, tricks, ...
3 stars 0 forks source link

Snowdrop / Red Hat Runtimes - website information review #266

Open BarDweller opened 3 years ago

BarDweller commented 3 years ago

We currently have snowdrop.me, and exist as a 'Red Hat Runtime'. Our presence on the official Red Hat website for Runtimes is inconsistent, and it would appear the main site may need updates, as it refers to Runtimes as only for Java.

cmoulliard commented 3 years ago

We currently have snowdrop.me, and exist as a 'Red Hat Runtime'.

What do you want to say here ? Can you rephrase please ?

cmoulliard commented 3 years ago

Our presence on the official Red Hat website for Runtimes is inconsistent, and it would appear the main site may need updates, as it refers to Runtimes as only for Java.

As you cover different aspects within this ticket, can you then better organize the content and use sub-titles please

Example:

## Red Hat Customer portal and Runtimes

### Lack of reference of Spring Boot Runtime
...
### Inconsistent versioning
cmoulliard commented 3 years ago
  • (Also, why is Red Hat Runtimes in the left table? isn't that what the page is about? and why is AMQ in both?)

This is because this page lists the 3 subscriptions that Red Hat proposes for the customers: Integration, Runtimes and Automation. If you buy the subscription of integration, then you will also got the runtimes (= support)

cmoulliard commented 3 years ago
  • 2.3 doesn't even appear to be an option, although it's been out since May 2020.

2.3 will only be added when it will be released. ER1 build has been created yesterday and Libor - QE team is testing it ;-)

BarDweller commented 3 years ago

We currently have snowdrop.me, and exist as a 'Red Hat Runtime'.

What do you want to say here ? Can you rephrase please ?

If I understand this correctly, Snowdrop is the upstream for the Spring Boot Red Hat Runtime. It's either that, or it IS the Spring Boot Red Hat Runtime. I'm trying to illustrate there are 2 facets here of the same thing, that we seem to use interchangeably, but yet never explain the relationship between, or define their boundaries of, via the pages.

BarDweller commented 3 years ago

Our presence on the official Red Hat website for Runtimes is inconsistent, and it would appear the main site may need updates, as it refers to Runtimes as only for Java.

As you cover different aspects within this ticket, can you then better organize the content and use sub-titles please

Example:

## Red Hat Customer portal and Runtimes

### Lack of reference of Spring Boot Runtime
...
### Inconsistent versioning

No probs.. was more focused on getting the words & thoughts captured.. will revisit the layout.

BarDweller commented 3 years ago
  • 2.3 doesn't even appear to be an option, although it's been out since May 2020.

2.3 will only be added when it will be released. ER1 build has been created yesterday and Libor - QE team is testing it ;-)

2.3.0 (community) has been available since May, yet the 'launch' thing that offers community versions still only offers 2.2.6. The comment was related to the same root cause tho, that 2.2.6 seems to be maximum version referred to across the site, even though 2.2.6 was released back in March, and the 2.2.x line is currently at 2.2.10 ? Looking at https://mvnrepository.com/artifact/dev.snowdrop/snowdrop-dependencies we have released a 2.2.10 (although it's not clear where 2.2.7/2.2.8/2.2.9 went). Either way, you'd expect all the various parts currently saying 2.2.6 to have updated.

cmoulliard commented 3 years ago

If I understand this correctly, Snowdrop is the upstream for the Spring Boot Red Hat Runtime.

Yes. Snowdrop is the name of our team, github domain, DNS name snowdrop.me | snowdrop.dev; corresponds also to our upstream projects and where we host projects that we build specifically for Red Hat Runtime Spring Boot Eg: SpringBoot with Vert.x as Reactive engine

cmoulliard commented 3 years ago

although it's not clear where 2.2.7/2.2.8/2.2.9 went

They were not released as currently we cannot productize everything that Pivotal is releasing due to time, resources constraints. Question: Should we productize and release them ?

cmoulliard commented 3 years ago

I propose that you move this task to the backlog (as we depend on the decision about what we will implement to support / generate a project) and runtime discussions @BarDweller

BarDweller commented 3 years ago

Agreed.