[Starlingx-discuss] Proposal: Basic development guidelines / rules

Xie, Cindy cindy.xie at intel.com
Thu Jun 21 06:19:18 UTC 2018

I am not quite sure if I understand below:

Code submissions for bug fixes do not need to be reviewed before pushing to gerrit. Bug reports should be posted to Storyboard.

Are you saying that patches for bug fixing do not required code-review + 1, +2 before it merged? Or you just are saying no [RFC] requests in mailing list shall be reviewed before bug-fixing patch got submitted?

Thx. - cindy

-----Original Message-----
From: Arce Moreno, Abraham [mailto:abraham.arce.moreno at intel.com] 
Sent: Thursday, June 21, 2018 11:14 AM
To: Jones, Bruce E <bruce.e.jones at intel.com>; starlingx-discuss at lists.starlingx.io
Subject: Re: [Starlingx-discuss] Proposal: Basic development guidelines / rules

> Rule 7: Code submissions for larger development tasks shall be 
> discussed on the mailing list _prior_ to code submission, to allow for 
> community review and feedback.  Post early and often.  Please review 
> (and test!) each other's code.

What is the usual way in OpenStack to review a proposal of a change? 
I have 2 files, one script that downloads from a text file a list tar compressed files, is it ok to post the patch as [RFC] in this mailing list? Etherpad?
Any other?

Thanks for your guidance!
Starlingx-discuss mailing list
Starlingx-discuss at lists.starlingx.io

More information about the Starlingx-discuss mailing list