From: Andreas Pretzsch <apr@cn-eng.de>
To: rauc@pengutronix.de
Subject: [RAUC] RAUC version tagging policy
Date: Tue, 28 May 2019 23:24:15 +0200 [thread overview]
Message-ID: <d2b0b20eb02bb3df3f130ee5b3bb2949d1204f80.camel@cn-eng.de> (raw)
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.
Thanks for providing this great piece of concept and software,
Andreas
--
carpe noctem engineering
Ingenieurbuero fuer Hard- & Software-Entwicklung Andreas Pretzsch
Dipl.-Ing. (FH) Andreas Pretzsch Tel. +49-(0)7307-936088-1
Lange Strasse 28a Fax: +49-(0)7307-936088-9
89250 Senden, Germany email: apr@cn-eng.de
_______________________________________________
RAUC mailing list
next reply other threads:[~2019-05-28 21:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-28 21:24 Andreas Pretzsch [this message]
2019-06-05 17:27 ` Enrico Jörns
2019-07-01 17:15 ` Andreas Pretzsch
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=d2b0b20eb02bb3df3f130ee5b3bb2949d1204f80.camel@cn-eng.de \
--to=apr@cn-eng.de \
--cc=rauc@pengutronix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox