openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Ed Tanous <ed@tanous.net>
To: OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Gerrit owners plugin coming
Date: Wed, 20 Jan 2021 11:23:25 -0800	[thread overview]
Message-ID: <CACWQX821ADQCrekLj_bGAu=1SSLCv5pTee7jaoVo2Zs6havgnA@mail.gmail.com> (raw)

Over the last few weeks, we've been slowly getting the gerrit owners
plugin deployed and tested, and got the OWNERS files merged into their
respective meta layers.

This has been leading up to a process change that has been on the
roadmap for some time now.  Once the plugin is enabled (and some other
housekeeping is done) meta-layer changes will be able to be submitted
to the normal openbmc/openbmc repository, simplifying one portion of
our review/merge process.  Submitting to openbmc/openbmc is something
most newcomers to the project expect, and we've had numerous gerrit
reviews submitted to the wrong repo in error.  Hopefully, this change
makes meta-layer changes much more normalized.

Once this goes in, this means that functionally:
1. We no longer have a bottleneck on creating new meta-layers,
renaming meta layers, or moving files between meta layers.  New meta
layers can be submitted through gerrit similar to any other patchset,
and will be reviewed with the same process we already have for any
other type of code, and don't require requesting a new repo in
advance.
2. Changes that require mods to all meta layers (yocto compat fields
for example) can be done in a single commit, across all systems at
once, reducing the possibility of breaking builds for meta-layer
combinations that aren't covered by CI.
3. No more waiting for your meta-X changes to get merged into
mainline, which should reduce the amount of time between recipe bumps
and the main build reflecting the changes.

Ownership of the various meta-layer folders is still enforced by
gerrit through the owners plugin using the OWNERS files.  Today, they
contain the same mapping as the content in the MAINTAINERS files, so
no files in the repo actually change ownership.

The final review to add the OWNERS file to the root of the repo is here:
https://gerrit.openbmc-project.xyz/c/openbmc/openbmc/+/39379
And has already had some discussion and looks to be good to go.
Assuming there's no other objections, I'd like to get this change made
on this coming Sunday.

Overall, I hope that this will be a great improvement in the overall
structure and usability of openbmc, and remove at least one stumbling
block people new to the project tend to hit.

-Ed

             reply	other threads:[~2021-01-20 19:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-20 19:23 Ed Tanous [this message]
2021-01-20 23:20 ` Gerrit owners plugin coming Andrew Jeffery
2021-01-21 16:07 ` Andrew Geissler
2021-01-25 13:47   ` Brad Bishop
2021-01-25 13:49 ` Brad Bishop
2021-01-25 18:04 ` Klaus Heinrich Kiwi
2021-01-25 21:27   ` Ed Tanous
2021-01-25 21:26 ` Ed Tanous
2021-01-27 11:59   ` Alexander Amelkin
2021-01-27 17:09     ` Ed Tanous
2021-01-28  0:37       ` Brad Bishop
2021-01-28  2:06       ` Thang Q. Nguyen
2021-01-28 17:23         ` Ed Tanous
2021-01-29  2:09           ` Thang Q. Nguyen

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='CACWQX821ADQCrekLj_bGAu=1SSLCv5pTee7jaoVo2Zs6havgnA@mail.gmail.com' \
    --to=ed@tanous.net \
    --cc=openbmc@lists.ozlabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).