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
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ devicetree-discuss mailing list devicetree-discuss@lists.ozlabs.org https://lists.ozlabs.org/listinfo/devicetree-discuss
