From: Tom Rini <trini@konsulko.com>
To: Martin Bonner <martingreybeard@gmail.com>
Cc: Claudius Heine <ch@denx.de>, u-boot@lists.denx.de
Subject: Re: [PATCH 4/4] doc: Migrate Process wiki page to sphinx
Date: Fri, 8 Jul 2022 13:44:58 -0400 [thread overview]
Message-ID: <20220708174458.GQ1146598@bill-the-cat> (raw)
In-Reply-To: <CACHZXAQ-zr1A5+E77Y4ainWyuEP-H2ji7ar13OQK8LAuar9jmA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 4518 bytes --]
On Fri, Jul 08, 2022 at 08:22:12AM +0100, Martin Bonner wrote:
> Martin
>
>
> On Fri, 8 Jul 2022 at 08:06, Claudius Heine <ch@denx.de> wrote:
>
> > Hi Tom,
> >
> > On 2022-06-27 19:17, Tom Rini wrote:
> > > Move the current Process wiki page to doc/develop/process.rst. The
> > > changes here are for formatting or slight rewording so that it reads
> > > well when linking to other sphinx documents.
> > >
> > > Signed-off-by: Tom Rini <trini@konsulko.com>
> > > ---
> > > doc/develop/index.rst | 1 +
> > > doc/develop/process.rst | 182 ++++++++++++++++++++++++++++++++++++++++
> > > 2 files changed, 183 insertions(+)
> > > create mode 100644 doc/develop/process.rst
> > >
> > > diff --git a/doc/develop/index.rst b/doc/develop/index.rst
> > > index c0f4f0ba413a..eab00a55382a 100644
> > > --- a/doc/develop/index.rst
> > > +++ b/doc/develop/index.rst
> > > @@ -11,6 +11,7 @@ General
> > >
> > > codingstyle
> > > designprinciples
> > > + process
> > >
> > > Implementation
> > > --------------
> > > diff --git a/doc/develop/process.rst b/doc/develop/process.rst
> > > new file mode 100644
> > > index 000000000000..dd279fb9eff1
> > > --- /dev/null
> > > +++ b/doc/develop/process.rst
> > > @@ -0,0 +1,182 @@
> > > +.. SPDX-License-Identifier: GPL-2.0+:
> > > +
> > > +U-Boot Development Process
> > > +==========================
> > > +
> > > +Management Summary
> > > +------------------
> > > +
> > > +* Development happens in Release Cycles of 3 months.
> > > +* The first 2 weeks are called Merge Window, which is followed by a
> > > + Stabilization Period.
> > > +* Patches with new code get only accepted while the Merge Window is
> > open.
> > > +* A patch that is generally in good shape and that was submitted while
> > the
> > > + Merge Window was open is eligible to go into the upcoming release,
> > even if
> > > + changes and resubmits are needed.
> > > +* During the Stabilization Period, only patches that contain bug fixes
> > get
> > > + applied.
> > > +
> > > +Phases of the Development Process
> > > +---------------------------------
> > > +
> > > +U-Boot development takes place in `Release Cycles
> > > +<https://www.denx.de/wiki/U-Boot/ReleaseCycle>`_. A Release Cycle
> > lasts
> > > +normally for three months.
> > > +
> > > +The first two weeks of each Release Cycle are called *Merge Window*.
> > > +
> > > +It is followed by a *Stabilization Period*.
> > > +
> > > +The end of a Release Cycle is marked by the release of a new U-Boot
> > version.
> > > +
> > > +Merge Window
> > > +------------
> > > +
> > > +The Merge Window is the period when new patches get submitted
> > > +(and hopefully accepted) for inclusion into U-Boot mainline.
> > > +
> > > +This is the only time when new code (like support for new processors or
> > new
> > > +boards, or other new features or reorganization of code) is accepted.
> > > +
> > > +Twilight Time
> > > +-------------
> > > +
> > > +Usually patches do not get accepted as they are - the peer review that
> > takes
> > > +place will usually require changes and resubmits of the patches before
> > they
> > > +are considered to be ripe for inclusion into mainline.
> > > +
> > > +Also, the review often happens not immediately after a patch was
> > submitted,
> > > +but only when somebody (usually the responsible custodian) finds time
> > to do
> > > +this.
> > > +
> > > +In the result, the final version of such patches gets submitted after
> > the
> >
> Should be: "The result is that the final version..." or "This can mean the
> final version..."
>
>
> > > +merge window has been closed.
> > > +
> > > +It is current practice in U-Boot that such patches are eligible to go
> > into the
> > > +upcoming release.
> > > +
> > > +In the result, the release of the ``"-rc1"`` version does not
> > immediately follow
> >
> Should be "The result is that the release..." or "Thus the release..."
>
> The first of both my two choices is closer to the original wording, the
> second feels to me (as a British English speaker) to be more idiomatic.
> (Beware, idiomatic English is not necessarily good - not everyone here is a
> native speaker, and it can be overly complex.)
Thanks for the feedback. I suspect that Wolfgang wrote these pages
initially. I'll cc you both on patches to adjust the wording slightly.
I'm doing the read-aloud test on these sections now.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2022-07-08 17:45 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-27 17:17 [PATCH 0/4] Migrate some wiki pages to sphinx Tom Rini
2022-06-27 17:17 ` [PATCH 1/4] doc: Migrate CodingStyle wiki page " Tom Rini
2022-06-30 10:06 ` Simon Glass
2022-07-09 6:15 ` Heinrich Schuchardt
2022-07-09 6:12 ` Heinrich Schuchardt
2022-07-09 12:32 ` Tom Rini
2022-07-09 12:36 ` Tom Rini
2022-06-27 17:17 ` [PATCH 2/4] doc: Migrate DesignPrinciples " Tom Rini
2022-06-30 10:06 ` Simon Glass
2022-07-08 7:22 ` Claudius Heine
2022-07-09 6:37 ` Heinrich Schuchardt
2022-07-09 12:39 ` Tom Rini
2022-06-27 17:17 ` [PATCH 3/4] doc: codingstyle: Remove comment about '//' style comments Tom Rini
2022-06-30 10:06 ` Simon Glass
2022-07-09 6:40 ` Heinrich Schuchardt
2022-06-27 17:17 ` [PATCH 4/4] doc: Migrate Process wiki page to sphinx Tom Rini
2022-06-30 10:06 ` Simon Glass
2022-07-08 7:06 ` Claudius Heine
2022-07-08 7:22 ` Martin Bonner
2022-07-08 17:44 ` Tom Rini [this message]
2022-07-09 6:55 ` Heinrich Schuchardt
2022-07-09 12:41 ` Tom Rini
2022-07-09 15:02 ` Tom Rini
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=20220708174458.GQ1146598@bill-the-cat \
--to=trini@konsulko.com \
--cc=ch@denx.de \
--cc=martingreybeard@gmail.com \
--cc=u-boot@lists.denx.de \
/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.