From: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
To: Mike Frysinger <vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>,
devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
Subject: Re: RFC: New release for DTC?
Date: Sun, 18 Nov 2012 00:00:13 +0000 [thread overview]
Message-ID: <20121118000013.6964A3E08F7@localhost> (raw)
In-Reply-To: <201211171250.08597.vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
On Sat, 17 Nov 2012 12:50:07 -0500, Mike Frysinger <vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org> wrote:
> On Thursday 23 August 2012 21:36:25 David Gibson wrote:
> > On Thu, Aug 23, 2012 at 08:15:39PM +0200, Yann E. MORIN wrote:
> > > Following advice from Jon Loeliger, I would suggest that a new release
> > > of DTC be tagged and packaged.
> > >
> > > It is important for some projects to rely on a released version, rather
> > > than use a random cset from the repository. Comes to mind, the automated
> > > build-systems, such as buildroot.
> > >
> > > Of course, I can help, if need be! ;-)
> > >
> > > Are there any others who think that a release would make sense?
> >
> > This has been a bit of a perrenial problem. dtc development has been
> > sufficiently gradual that there haven't been many obvious points for
> > making new releases. dtc developers (i.e. Jon and my, mostly) don't
> > feel much pain from the lack of releases, since the git snapshots
> > generally work well (thanks to limited scope and a good testsuite).
> >
> > I wonder if we should move to a model of just making a release every 3
> > or 6 months from whatever happens to be in the tree at the time
> > (barring obvious known breakage, of course).
>
> yes please. even just a version that uses datestamps would be fine.
> -mike
Fine by me.
g.
next prev parent reply other threads:[~2012-11-18 0:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-23 18:15 RFC: New release for DTC? Yann E. MORIN
[not found] ` <201208232015.39613.yann.morin.1998-GANU6spQydw@public.gmane.org>
2012-08-24 1:36 ` David Gibson
[not found] ` <20120824013625.GA8067-W9XWwYn+TF0XU02nzanrWNbf9cGiqdzd@public.gmane.org>
2012-11-17 17:50 ` Mike Frysinger
[not found] ` <201211171250.08597.vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
2012-11-18 0:00 ` Grant Likely [this message]
2012-12-10 22:40 ` Simon Glass
[not found] ` <CAPnjgZ23ofzihzCMb-i6NMDFuMrYabfo2JGeSPKz+E3gzqDnLA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-12-11 14:55 ` Jon Loeliger
[not found] ` <E1TiREr-0004Mk-IP-CYoMK+44s/E@public.gmane.org>
2012-12-11 18:59 ` Simon Glass
2013-05-30 17:45 ` Stephen Warren
[not found] ` <51A79033.7080800-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-06-15 0:17 ` Grant Likely
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=20121118000013.6964A3E08F7@localhost \
--to=grant.likely-s3s/wqlpoipyb63q8fvjnq@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.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).