From: Denys Dmytriyenko <denys@ti.com>
To: Ankur Tyagi <ankur.tyagi85@gmail.com>
Cc: meta-arago@arago-project.org
Subject: Re: Upcoming stable branch
Date: Mon, 10 Jun 2019 18:20:30 -0400 [thread overview]
Message-ID: <20190610222030.GK25589@beryl> (raw)
In-Reply-To: <CADySD0GL-ndHy_g8zesfpyW-LagiyFn1-zv88g-sdWmPU6bFGg@mail.gmail.com>
No, <release>-next branches are used across many OpenEmbedded/Yocto layers
exactly the same - for testing changes to that release branch.
Denys
On Tue, Jun 11, 2019 at 08:15:41AM +1200, Ankur Tyagi wrote:
> Thanks Denys.
>
> Should I start with thud or thud-next?
> Is thud-next for next milestone release?.
>
> Regards
> Ankur
>
> On Tue, 11 Jun 2019, 5:15 a.m. Denys Dmytriyenko, <denys@ti.com> wrote:
>
> > No plans for warrior - we are on a single LTS per year schedule, picking
> > up
> > only Fall even releases and skipping Spring odd ones.
> >
> > Denys
> >
> >
> > On Mon, Jun 10, 2019 at 08:14:21AM +1200, Ankur Tyagi wrote:
> > > Hi,
> > >
> > > We are planning to upgrade arago distro in our product.
> > > At this point, I can only see thud branch in meta-arago whereas warrior
> > is
> > > available in oe-core.
> > >
> > > Is there any plan for warrior in meta-arago or is it being skipped?
> > > What is the difference between thud and thud-next?
> > >
> > > Thanks
> > > Ankur
> >
> > > _______________________________________________
> > > meta-arago mailing list
> > > meta-arago@arago-project.org
> > > http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago
> >
> >
next prev parent reply other threads:[~2019-06-10 22:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-09 20:14 Upcoming stable branch Ankur Tyagi
2019-06-10 17:15 ` Denys Dmytriyenko
2019-06-10 20:15 ` Ankur Tyagi
2019-06-10 22:20 ` Denys Dmytriyenko [this message]
2019-06-10 22:34 ` Ankur Tyagi
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=20190610222030.GK25589@beryl \
--to=denys@ti.com \
--cc=ankur.tyagi85@gmail.com \
--cc=meta-arago@arago-project.org \
/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.