Hi Andreas, Am 28.05.19 um 23:24 schrieb Andreas Pretzsch: > Looking into RAUC for a customer project, I decided to go with git HEAD > instead of the last official release. > > The "Christmas present" release 1.0 was tagged on 20.12.2018. > Since then, some 57 commits came in. A few of them I'd like to have. > > Now, while I am comfortable with referring to some git commit id, > project managers and software department heads are not (always). > > Might I suggest a more regular version tagging policy ? > Like every few months latest, or rather when it makes some sense. > Doesn't need to be that regular like ptxdist or barebox, but still... > > We all know the technical value of version numbers, and their apparent > promise of stability, yes. But from a "product selling" point of view, > I'm sure it would do more good than harm to RAUC as a project.
of course there was no intention behind the 'long' time that passed since the last RAUC release, but I agree with you that it was time for a new release. Up to now this was only prevented by other workload. As you might have seen already, we just released RAUC v1.1 today. Thus you can use all the great new patches without having to refer to git master state :) > Thanks for providing this great piece of concept and software, Thanks to you! Best regards, Enrico -- Pengutronix e.K. | Enrico Jörns | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-5080 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | _______________________________________________ RAUC mailing list
