From: Bian Naimeng <biannm@cn.fujitsu.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: poky@yoctoproject.org
Subject: Re: Why we release yocto on different branch
Date: Fri, 02 Aug 2013 14:33:59 +0800 [thread overview]
Message-ID: <51FB52D7.1010507@cn.fujitsu.com> (raw)
In-Reply-To: <EDC7964C-6C92-49D1-BA30-4CE95F5578A3@gmail.com>
said the following on 2013-7-24 15:02:, Khem Raj wrote:
>
> On Jul 23, 2013, at 11:57 PM, Bian Naimeng <biannm@cn.fujitsu.com> wrote:
>
>> Hi all,
>>
>> Why we release yocto on different branch?
>
> These branches are from same trunk which we call master in git terms.
>
>>
>> Yocto Project 1.2: denzil
>> Yocto Project 1.3: danny
>> Yocto Project 1.4: dylan
>>
>
> yes denzil danny and dylan and so on are codenames for branches on which releases are made.
>
>> Some questions.
>> 1. Do we always create a new branch to release the next Yocto Project?
>
> yes
Thanks for your answer.
Do we apply new features into these branches such as denzil/danny/dylan.
Only bug fix?
Thanks
Bian
>
>> 2. If so, which branch/commit the new branch start from?
>
> There is master branch and when the time comes the next release branch is spawned from master
>
>> 3. What's the relation between these branch?
>
> These are release branches cut from master at some point in time.
>
>>
>> Thanks,
>> bian
>>
>> _______________________________________________
>> poky mailing list
>> poky@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/poky
next prev parent reply other threads:[~2013-08-02 6:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-24 6:57 Why we release yocto on different branch Bian Naimeng
2013-07-24 7:02 ` Khem Raj
2013-08-02 6:33 ` Bian Naimeng [this message]
2013-08-02 7:28 ` Khem Raj
2013-08-02 8:09 ` Bian Naimeng
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=51FB52D7.1010507@cn.fujitsu.com \
--to=biannm@cn.fujitsu.com \
--cc=poky@yoctoproject.org \
--cc=raj.khem@gmail.com \
/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.