From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id B0000E0084A; Mon, 26 Jun 2017 21:18:25 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,HTML_MESSAGE, RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low * trust * [195.74.38.228 listed in list.dnswl.org] * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 0.0 HTML_MESSAGE BODY: HTML included in message Received: from bin-vsp-out-01.atm.binero.net (bin-mail-out-05.binero.net [195.74.38.228]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 1F1F9E00524 for ; Mon, 26 Jun 2017 21:18:22 -0700 (PDT) X-Halon-ID: a60353ae-5aef-11e7-b24c-005056917a89 Authorized-sender: petter@technux.se Received: from petterarch (unknown [78.78.81.189]) by bin-vsp-out-01.atm.binero.net (Halon) with ESMTPA id a60353ae-5aef-11e7-b24c-005056917a89; Tue, 27 Jun 2017 06:18:19 +0200 (CEST) Message-ID: <1498537093.5949.5.camel@technux.se> From: Petter Mabacker To: Andrei Gherzan Date: Tue, 27 Jun 2017 06:18:13 +0200 In-Reply-To: References: X-Mailer: Evolution 3.24.3 Mime-Version: 1.0 Cc: "yocto@yoctoproject.org" Subject: Re: [meta-chip] Jenkins, reviews and mailing list X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Jun 2017 04:18:25 -0000 Content-Type: multipart/alternative; boundary="=-5C+QzSndO38VrJuk7J0z" --=-5C+QzSndO38VrJuk7J0z Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit On Mon, 2017-06-26 at 17:12 +0100, Andrei Gherzan wrote: > On Mon, Jun 26, 2017 at 2:29 PM, Trevor Woerner > wrote: > > On Mon, Jun 26, 2017 at 9:21 AM, Andrei Gherzan > > wrote: > > > > > We've been testing a setup with meta-raspberrypi which seems to > > work fine: > > > > > PR to github integrated with a jenkins server and use mailing > > list for > > > > > discussions. > > > > > > > > > > I propose to copy the same setup to meta-chip too. > > > > > > > > That's all fine. As the maintainer (thank you!) you're welcome to > > use > > > > whatever workflow with which you're the happiest... as long as you > > > > update the "Contributing" section of the README :-) > > > > Sure. That makes sense. Hi Andrei, I fully agree with Trevor, just update the README and lets rock! :) But like you say I also believe it's good if people can take the time to also send the patches to mailing list, so we don't risk losing those valuable discussions that often is initated through the mailing list (since more people will track the changes that way). My opinion is that this have work good for meta-raspberrypi, so cannot see any reasons why it should work great for meta-chip as well. Let us know when jenkins is up-and-running! Cheers Petter > --Andrei Gherzan > --=-5C+QzSndO38VrJuk7J0z Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: 7bit
On Mon, 2017-06-26 at 17:12 +0100, Andrei Gherzan wrote:
On Mon, Jun 26, 2017 at 2:29 PM, Trevor Woerner <twoerner@gmail.com> wrote:
On Mon, Jun 26, 2017 at 9:21 AM, Andrei Gherzan <andrei@gherzan.ro> wrote:
> We've been testing a setup with meta-raspberrypi which seems to work fine:
> PR to github integrated with a jenkins server and use mailing list for
> discussions.
>
> I propose to copy the same setup to meta-chip too.

That's all fine. As the maintainer (thank you!) you're welcome to use
whatever workflow with which you're the happiest... as long as you
update the "Contributing" section of the README :-)

Sure. That makes sense.

Hi Andrei,

I fully agree with Trevor, just update the README and lets rock! :) But like you say I also believe it's good if people can take the time to also send the patches to mailing list, so we don't risk losing those valuable discussions that often is initated through the mailing list (since more people will track the changes that way). My opinion is that this have work good for meta-raspberrypi, so cannot see any reasons why it should work great for meta-chip as well.

Let us know when jenkins is up-and-running!

Cheers Petter


--
Andrei Gherzan
--=-5C+QzSndO38VrJuk7J0z--