Merge lp://qastaging/~deeptik/linaro-ci/fix-bug1013611 into lp://qastaging/linaro-ci

Proposed by Deepti B. Kalakeri
Status: Merged
Approved by: Milo Casagrande
Approved revision: 73
Merged at revision: 72
Proposed branch: lp://qastaging/~deeptik/linaro-ci/fix-bug1013611
Merge into: lp://qastaging/linaro-ci
Diff against target: 222 lines (+192/-0)
6 files modified
node/init-fifo (+19/-0)
node/setup-natty-node (+23/-0)
node/setup-oneiric-node (+32/-0)
node/setup-precise-node (+38/-0)
node/setup_lib (+59/-0)
node/userdata-fifo (+21/-0)
To merge this branch: bzr merge lp://qastaging/~deeptik/linaro-ci/fix-bug1013611
Reviewer Review Type Date Requested Status
Paul Sokolovsky Approve
Milo Casagrande (community) Approve
Review via email: mp+110740@code.qastaging.launchpad.net
To post a comment you must log in.
Revision history for this message
Milo Casagrande (milo) wrote :

Hello Deepti,

thanks for working on this!
Merge proposal looks good to me, the only thing I will add is or a README file with a little bit of docs/description of the various scripts, or small comments per script that describe the script intents (even if they are not that complex, at least it will be easier for other to pick up faster what has been done).

Also, I see that two files have license headers, others do not: what is the policy in these cases? Should all source code files have a license header?

Another thing, but definitely minor: files use underscores or dashes in their names. There are file names with the latter and other with the former. Should we use just one?

review: Needs Fixing
73. By Deepti B. Kalakeri

Address review comments, added comments in every script, modified script names

Revision history for this message
Deepti B. Kalakeri (deeptik) wrote :

On Mon, Jun 18, 2012 at 2:47 PM, Milo Casagrande
<email address hidden>wrote:

> Review: Needs Fixing
>
> Hello Deepti,
>
> thanks for working on this!
> Merge proposal looks good to me, the only thing I will add is or a README
> file with a little bit of docs/description of the various scripts, or small
> comments per script that describe the script intents (even if they are not
> that complex, at least it will be easier for other to pick up faster what
> has been done).
>
> Thanks for the quick review.
I included lines in each of the scripts as its more easy to understand the
usage of the scripts.

> Also, I see that two files have license headers, others do not: what is
> the policy in these cases? Should all source code files have a license
> header?
>

The license header is for 2011 I will remove it for now, and would speak
with Danilo and the whole team on what is the appropriate header to be
included in the scripts.

>
> Another thing, but definitely minor: files use underscores or dashes in
> their names. There are file names with the latter and other with the
> former. Should we use just one?
>

AFAIK, there is no particular naming convention that I came across in
various tools in infrastructure.

>
> --
> https://code.launchpad.net/~deeptik/linaro-ci/fix-bug1013611/+merge/110740<https://code.launchpad.net/%7Edeeptik/linaro-ci/fix-bug1013611/+merge/110740>
> You are the owner of lp:~deeptik/linaro-ci/fix-bug1013611.
>

--
Thanks and Regards,
Deepti

Revision history for this message
Milo Casagrande (milo) wrote :

Hello Deepti,

thanks for adding some descriptions to the scritp!
As discussed on IRC, we can merge and in case fix later the other bits that need to be discussed.

review: Approve
Revision history for this message
Paul Sokolovsky (pfalcon) wrote :

This is definitely looks good, and thanks for quick turnaround! For custom AMI BP, we with Stevan might need to do further tweaks, but having this will allow us to concentrate on our code first of all instead of spreading thin.

I also appreciate flexibility on Milo's side - it's true that our codebases lack on consistency side quite a bunch, but fixing that in adhoc manner oftentimes only complicates and procrastinates functional work. What I dream of is of us getting a blueprint "Clean up our codebases consistently", settle on extra rules we currently miss (like '_' vs '-' dichotomy) have a good swipe over all our projects, and they maintain them on that level.

review: Approve

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
The diff is not available at this time. You can reload the page or download it.

Subscribers

People subscribed via source and target branches