+1 !!!
> On Jan 28, 2021, at 12:39 PM, JB Onofré <j...@nanthrax.net> wrote:
>
> Hi Matt
>
> Yes it’s what I was referring by « details » (JDK, JMS version, etc).
>
> +1 !
>
> Regards
> JB
>
>> Le 28 janv. 2021 à 19:30, Matt Pavlovich <mattr...@gmail.com> a écrit :
>>
>> Hi JB-
>>
>> I think this is a good idea, esp w/ the JDK and Jakarta movement the way it
>> is.
>>
>> What do you think about adding the JDK, JEE, standards APIs and protocol
>> versions into the table? (like Karaf does, which I think is very useful).
>> Maybe the messaging protos and API versions in a separate tablet to keep the
>> first one about release cadence?
>>
>>
>> 5.17.x — JDK11, Jakarta?, JMS v2.0, MQTTv5?
>> 5.16.x —
>> 5.15.x — JDK 8, JEE, JMS v1.0, MQTTv3
>>
>> Thanks!
>> -Matt
>>
>>> On Jan 28, 2021, at 10:58 AM, Jean-Baptiste Onofre <j...@nanthrax.net>
>>> wrote:
>>>
>>> Hi guys,
>>>
>>> I would like to propose something similar to what we do on Apache Karaf
>>> regarding releases.
>>>
>>> http://karaf.apache.org/download.html
>>> <http://karaf.apache.org/download.html>
>>>
>>> Basically, my proposal is:
>>>
>>> - flag any branch < 5.15.x (5.14.x, 5.13.x, …) as "Not Active"
>>> - flag 5.15.x and 5.16.x as "Stable"
>>> - flag 5.17.x as "Development"
>>>
>>> About the release cycle, I would like to propose:
>>>
>>> - 5.15.x release every quarter (meaning that 5.15.15 will be scheduled for
>>> March, 9th)
>>> - 5.16.x release every two weeks (meaning that 5.16.2 will be scheduled for
>>> end of Feb)
>>>
>>> I would like to add details about releases schedule (and JDK version
>>> supported, etc) on
>>>
>>> http://activemq.apache.org/components/classic/download/
>>> <http://activemq.apache.org/components/classic/download/>
>>>
>>> Thoughts ?
>>>
>>> Regards
>>> JB
>>
>
