All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] 2013.07-rc1 plans?
Date: Mon, 10 Jun 2013 19:18:18 -0400	[thread overview]
Message-ID: <20130610231818.GS26693@bill-the-cat> (raw)
In-Reply-To: <CAP9ODKqQhqkbEMCa3Wj+AEP+w-SJ3ejx2RsNRQhbJ2L568i9Rw@mail.gmail.com>

On Mon, Jun 10, 2013 at 01:05:42PM -0300, Otavio Salvador wrote:
> On Mon, Jun 10, 2013 at 12:55 PM, Tom Rini <trini@ti.com> wrote:
> 
> > On Mon, Jun 10, 2013 at 08:43:20AM -0300, Otavio Salvador wrote:
> >
> > > On Mon, Jun 10, 2013 at 6:26 AM, Albert ARIBAUD
> > > <albert.u.boot@aribaud.net>wrote:
> > >
> > > > Hi Otavio,
> > > >
> > > > On Sun, 9 Jun 2013 12:54:31 -0300, Otavio Salvador
> > > > <otavio@ossystems.com.br> wrote:
> > > >
> > > > > Hello,
> > > > >
> > > > > I'd like to know what the plains regarding rc releases?
> > > >
> > > > Dunno right now what Tom is planning, but before it goes out, I would
> > > > like to first finish going through my current todo on patchwork (and
> > > > also sort out the current TI PR) so that rc1 has all ARM changes known
> > > > to be meant for 2013.07.
> > > >
> > >
> > > Right; I am specially interested on this but I also believe a more clear
> > > schedule or plan would be good.
> > >
> > > Maybe U-Boot could adopt a more or less 'rc' release as kernel. I don't
> > > think it needs to be weekly but every two weeks could be interesting?
> >
> > My intention has been to do more frequent rc releases.  I started out
> > doing that, but have slipped a bit.  I've honestly intented to do a rc1
> > for a while, but have just kept telling myself "one more thing", and not
> > tagging and pushing.  I will do -rc1 this week as a reminder to everyone
> > that hasn't posted pull requests that the time is coming for things
> > being just too late.
> >
> 
> Great; maybe we could have some cadence here? every two week? personally I
> think it'd be a good time window but any cadence works for me.

Yes, going forward from v2013.07 I'll try and do -rc1 at the end of the
traditional merge window (hey folks, if you haven't tried to get me or
your custodian to pull, shake a leg!) followed by ~2 week increments.

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20130610/f2117839/attachment.pgp>

      reply	other threads:[~2013-06-10 23:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-09 15:54 [U-Boot] 2013.07-rc1 plans? Otavio Salvador
2013-06-10  9:26 ` Albert ARIBAUD
2013-06-10 11:43   ` Otavio Salvador
2013-06-10 15:55     ` Tom Rini
2013-06-10 16:05       ` Otavio Salvador
2013-06-10 23:18         ` Tom Rini [this message]

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=20130610231818.GS26693@bill-the-cat \
    --to=trini@ti.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.