Re: RFC: New release for DTC?

On Thu, 30 May 2013 11:45:23 -0600, Stephen Warren [off-list ref] wrote:

On 08/23/2012 12:15 PM, Yann E. MORIN wrote:

quoted

Hello All!

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?

I'd love to see a new release. This would for example allow the U-Boot
project to say "dtc vXXX is required to build the DT files contained in
U-Boot", which might make agreeing on allowing the use of new dtc
features in U-Boot easier. While this could simply be done by referring
to a specific git commit ID, release versions or tags probably carry
more weight. Tagging a release might also act as a specific trigger for
distros to pick up and carry the new version.

Does it make sense to simply tag the current git HEAD as v1.4? If so,
can we do this?

If a new release can be done in the next week or so, then I will use
that to update the in-kernel dtc version.

g.