Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] Drop support for Qt 5.6? [was: [RFC 1/2] qt5: bump latest version to 5.10.0]
Date: Mon, 26 Feb 2018 09:22:13 +0100	[thread overview]
Message-ID: <87woz0rwi2.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20180225182810.GC2276@scaer> (Yann E. MORIN's message of "Sun, 25 Feb 2018 19:28:10 +0100")

>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:

 > Nimai, All,
 > On 2018-02-25 18:10 +0000, Nimai Mahajan spake thusly:
 >> That's fine, but keep in mind this will never be as stable as their LTS
 >> releases, where they are constantly fixing bugs (5.9 is supposed to be
 >> supported til 2020, whereas 5.11 will come out in May and deprecate 5.10).
 >> Latest branch just keeps getting new > features thrown in it without fixes
 >> to existing ones.

 > 5.6 is supposed to be maintained for three years after being introduced,
 > that is 2016-03-16 [0], which brings us toward 2019-03-16 as well, so a
 > bit more than a year still. ;-)

 > [0] https://www1.qt.io/qt-news/20578/

Correct, so this IMHO means we need to move to 5.9 for the LTS version
by the time we release Buildroot 2019.02, unless something changes - But
until then I would prefer to keep 5.6.

-- 
Bye, Peter Korsgaard

  parent reply	other threads:[~2018-02-26  8:22 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-11 16:13 [Buildroot] [RFC 0/2] Qt5 bump latest version to 5.10.0 Gaël PORTAY
2018-02-11 16:13 ` [Buildroot] [RFC 1/2] qt5: " Gaël PORTAY
2018-02-12 13:37   ` nimaim
2018-02-25 17:06     ` [Buildroot] Drop support for Qt 5.6? [was: [RFC 1/2] qt5: bump latest version to 5.10.0] Arnout Vandecappelle
2018-02-25 17:17       ` Baruch Siach
2018-02-25 17:26       ` Yann E. MORIN
2018-02-25 17:42         ` Nimai Mahajan
2018-02-25 17:52           ` Yann E. MORIN
2018-02-25 18:10             ` Nimai Mahajan
2018-02-25 18:28               ` Yann E. MORIN
2018-02-25 18:29                 ` Nimai Mahajan
2018-02-26  8:22                 ` Peter Korsgaard [this message]
2018-02-26 11:50                   ` Nimai Mahajan
2018-02-26 12:14                     ` Peter Korsgaard
2018-02-26 12:17                       ` Nimai Mahajan
2018-02-26 20:45                         ` Nimai Mahajan
2018-02-26  8:18       ` Peter Korsgaard
2018-02-12 21:07   ` [Buildroot] [RFC 1/2] qt5: bump latest version to 5.10.0 Gaël PORTAY
2018-02-11 16:13 ` [Buildroot] [RFC 2/2] qt5webengine: select libnss Gaël PORTAY
2018-02-12 21:19   ` Gaël PORTAY
2018-02-11 22:11 ` [Buildroot] [RFC 0/2] Qt5 bump latest version to 5.10.0 Julien CORJON
2018-02-12 18:20   ` Gaël PORTAY
2018-02-12 22:20 ` Gaël PORTAY
2018-02-13 15:23   ` Gaël PORTAY
2018-02-13 16:35     ` Gaël PORTAY
2018-02-19 22:58     ` Gaël PORTAY

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87woz0rwi2.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox