> On Wed, Mar 31, 2021 at 10:03 AM Loïc MATHIEU <
loik...@gmail.com>
> wrote:
>
>> Good news!
>>
>>> We are still evaluating if we could drop Java 8 support in 2.x (1.x
>>> will
>> still be compatible with Java 8).
>>
>> Where will the fight occurs ;)
>> I think the community is ready for 11 now, so you have my vote on
>> this one
>> ;)
Yeah, last time it was the community voices/asks that was pulling for
keeping 8 as
their existing environment prohibited use of Java 11+.
We expected hard push back from commercial industry but thus far we
haven't seen Java 8 asks
from customers. Would be curious to hear what others seen.
Thus it looks like those who actually do start with Quarkus are willing
to use newer Java,
and those who are in areas where Java 8 is the newest version they can
use probably also won't start on
a new project using newer frameworks and approaches (even though they
have teams that would love to do so)
I also think its time to rip the bandaid - otherwise we'll stay stuck.
Yes, time is right to do such moves but I do want to underline we should
do what we can
(within reason) to enable easy transition. i.e. thinking out loud about
the mongodb as an example if possible
to keep current extension name for easy migration but have it include
the two split ones enabling an easy upgrade path.
Don't see 2.0 to be a place to break things for users - the 2.0 is more
about extension writers having
to update to vert.x 4 and other cleanup. We should still deprecate and
provide transitions where we can.
/max
>
>
>> - Others should have other ideas ;)
>>
>> Regards,
>>
>> Loïc
>>
>> Le mar. 30 mars 2021 à 17:40, Manyanda Chitimbo <
>>
manyanda...@gmail.com> a écrit :
>>
>>> Good news!! Thanks for the update!
>>>
>>> On Tue 30 Mar 2021 at 17:06, Guillaume Smet
>>> <
guillau...@gmail.com>
>>> wrote:
>>>
>>>> Hello,
>>>>
>>>> Quarkus was announced to the world 2 years ago. During these 2
>>>> years, a
>>>> lot of things happened, and we can’t thank you enough for all the
>>>> support
>>>> and contributions you have all provided. These two years have been
>>>> an
>>>> incredible journey, and this mail is about the future.
>>>>
>>>> At the moment Quarkus 1.13 is getting released. You should be able
>>>> to
>>>> use it very soon. It has a lot of cool features such as
>>>> DevServices,
>>>> Kubernetes Service Binding, and OpenTelemetry.
>>>>
>>>> *So what’s next?*
>>>>
>>>> Over the last few months, we have been working on the integration
>>>> of
>>>> MicroProfile 4 and Vert.x 4. MicroProfile 4 is the latest version
>>>> of the
>>>> MicroProfile specifications. It comes with plenty of novelties,
>>>> such as an
>>>> improved configuration, fault tolerance, OpenAPI, GraphQL, and so
>>>> on.
>>>> Vert.x 4 is the latest version of Vert.x containing lots of API
>>>> improvements, traceability support, and plenty of other novelties.
>>>> As
>>>> Quarkus is based on Vert.x and relies heavily on MicroProfile
>>>> specifications, such switches are important.
>>>>
>>>> That’s why we decided to bump the Quarkus version to 2.x once
>>>> these
>>>> features will be integrated.
>>>>
>>>> *Is that all in 2.x?*
>>>>
>>>> Oh no! These are mostly internal changes.* It should be noted that
>>>> the
>>>> migration of most applications will be a no-brainer.* We will
>>>> describe
>>>> the few breaking changes and how to update your applications if you
>>>> use
>>>> some incompatible code in a migration guide as usual.
>>>>
>>>> But, we have more to offer in 2.x. First, Stuart recently started
>>>> working on Continuous Testing. We plan to include it in 2.x.
>>>>
>>>> qs, the new Quarkus command-line tool is going to be included in
>>>> 2.x too.
>>>>
>>>> We are still evaluating if we could drop Java 8 support in 2.x (1.x
>>>> will
>>>> still be compatible with Java 8).
>>>>
>>>> We are working on other features, but we don’t want to tell you
>>>> everything now ;-) Follow the pull requests on GitHub to know more.
>>>>
>>>> *Is 1.13 really the last 1.x one?*
>>>>
>>>> We will still backport bug fixes in the 1.13 branch and release
>>>> 1.13.z
>>>> versions periodically.
>>>>
>>>> If we have features for a 1.14, we may even consider releasing a
>>>> 1.14.
>>>> However, the main development will focus on 2.x and our main branch
>>>> will be
>>>> 2.x soon.
>>>>
>>>> *What about the schedule?*
>>>>
>>>> We plan to cut a few alpha versions of 2.x in April and May to
>>>> collect
>>>> feedback, for a final release in June (this is not a commitment,
>>>> just a
>>>> rough plan).
>>>>
>>>> *Quarkus 2.x is the continuation of 1.x. It’s not a big refactor,
>>>> it’s
>>>> not something totally new. The focus will still be the same:
>>>> supersonic,
>>>> subatomic, fun!*
>>>> <
https://groups.google.com/d/msgid/quarkus-dev/CALt0%2Bo_1m3adZ5KBmVZautJXRh_uZYNgg-_%2BYUBnHVM3pLiq6A%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>>> .
>>> <
https://groups.google.com/d/msgid/quarkus-dev/CANwCmXKAtySrdLZpLAMKhi2q45OO1LcXNhyTGvzGZiFs17DTYA%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>> --
>> You received this message because you are subscribed to the Google
>> Groups
>> "Quarkus Development mailing list" group.
>> To unsubscribe from this group and stop receiving emails from it,
>> send an
>> email to
quarkus-dev...@googlegroups.com.
>> To view this discussion on the web visit
>>
https://groups.google.com/d/msgid/quarkus-dev/CAJLxjVFm3gSPb8Ymkmau%3DjHyZOg2GmqWiV34fV2i4w1P1_0xpA%40mail.gmail.com
>> <
https://groups.google.com/d/msgid/quarkus-dev/CAJLxjVFm3gSPb8Ymkmau%3DjHyZOg2GmqWiV34fV2i4w1P1_0xpA%40mail.gmail.com?utm_medium=email&utm_source=footer>
>> .
>>
>
> --
> You received this message because you are subscribed to the Google
> Groups "Quarkus Development mailing list" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to
quarkus-dev...@googlegroups.com.
> To view this discussion on the web visit
>
https://groups.google.com/d/msgid/quarkus-dev/CAJ97idE4NoCRkOjW3AncaL9Fc5Yy78jENK9kWqjyXTcrWQnyxw%40mail.gmail.com.