All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] Any ETA for 2019.02.2?
Date: Fri, 26 Apr 2019 16:56:25 +0200	[thread overview]
Message-ID: <875zr0x1ba.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CY4PR1201MB01200C618215D77DFDAD8266A13E0@CY4PR1201MB0120.namprd12.prod.outlook.com> (Alexey Brodkin's message of "Fri, 26 Apr 2019 14:48:35 +0000")

>>>>> "Alexey" == Alexey Brodkin <Alexey.Brodkin@synopsys.com> writes:

Hi,

 >> Yes, the plan is to get a new releae out before the end of the
 >> month. 2019.02.1 is from End of March, and I normally do a point release
 >> approx once per month.

 > Right that's what I figured out myself judging by last few tags and so
 > was just checking. We're going to prepare some delivery and the question was
 > which release to use as a base, given that discussion I'll happily wait for
 > v2019.02.2 as discussed timeframe perfectly matches our delivery schedule :)

 > And thanks for taking care of that proven to be useful "stable" release process!

Great, it is always nice to hear that the work is useful to people -
Thanks!

-- 
Bye, Peter Korsgaard

      reply	other threads:[~2019-04-26 14:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-25 13:32 [Buildroot] Any ETA for 2019.02.2? Alexey Brodkin
2019-04-25 19:32 ` Thomas Petazzoni
2019-04-26  6:22   ` [Buildroot] [arc-buildroot] " Alexey Brodkin
2019-04-26 12:15 ` [Buildroot] " Peter Korsgaard
2019-04-26 14:48   ` Alexey Brodkin
2019-04-26 14:56     ` Peter Korsgaard [this message]

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=875zr0x1ba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.