From: "Kevin Hilman" <khilman@baylibre.com>
To: Guillaume Tucker <guillaume.tucker@gmail.com>,
kernelci@groups.io, Guillaume Tucker <guillaume.tucker@gmail.com>
Cc: Dan Rue <dan.rue@linaro.org>, Matt Hart <matthew.hart@linaro.org>
Subject: Re: staging projects in github
Date: Tue, 12 Mar 2019 10:47:16 -0700 [thread overview]
Message-ID: <7hr2bct26z.fsf@baylibre.com> (raw)
In-Reply-To: <CAH1_8nC=aa9jOa1rTzb7=joDXqjTDty+qeGe4bqpE11fqOgN-A@mail.gmail.com>
Guillaume Tucker <guillaume.tucker@gmail.com> writes:
> On Tue, Mar 5, 2019 at 5:24 PM Guillaume Tucker via Groups.Io
> <guillaume.tucker=gmail.com@groups.io> wrote:
>
>>
>> On Tue, Mar 5, 2019 at 5:04 PM Dan Rue <dan.rue@linaro.org> wrote:
>>
>>> On Tue, Mar 05, 2019 at 04:48:52PM +0000, Matt Hart wrote:
>>> > On Tue, 5 Mar 2019 at 05:14, Kevin Hilman <khilman@baylibre.com> wrote:
>>> > >
>>> > > Can we consolidate the various "-staging" project in github with the
>>> > > originals? I've never fully understood why we created separate github
>>> > > projects, when we should just be using a staging branch within the
>>> main
>>> > > project.
>>
>> [...]
>
>> I'm not sure if I'm considering all of the use-cases, but in the past
>>> I've much preferred having staging == "master" and then tagging for
>>> production releases. This does make it difficult (but not impossible) to
>>> have things in staging that are not promoted to production.
>>>
>>
>> What would make most sense imo would be to have the master branch
>> receiving the PRs (like Dan wrote) and a live "prod" branch used
>> by Jenkins.
>>
>
> So how about having one last staging -> prod sync this week using
> the kernelci-core-staging project, and then switch to using
> kernelci-core only starting from next week?
Sounds good to me.
Kevin
next prev parent reply other threads:[~2019-03-12 17:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-05 5:14 staging projects in github Kevin Hilman
2019-03-05 16:48 ` Matt Hart
2019-03-05 17:04 ` Dan Rue
2019-03-05 17:24 ` Guillaume Tucker
[not found] ` <15891FEF165BAE41.4955@groups.io>
2019-03-12 10:22 ` Guillaume Tucker
2019-03-12 17:47 ` Kevin Hilman [this message]
2019-03-18 10:33 ` Guillaume Tucker
2019-03-19 17:32 ` Kevin Hilman
[not found] ` <158B2EF7D55104B8.7925@groups.io>
2019-03-12 11:52 ` Guillaume Tucker
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=7hr2bct26z.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=dan.rue@linaro.org \
--cc=guillaume.tucker@gmail.com \
--cc=kernelci@groups.io \
--cc=matthew.hart@linaro.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.