[Letsencrypt-devel] Packaging next steps - release tags?
francois at debian.org
Mon Sep 21 03:59:21 UTC 2015
I've just re-tested the Debian packages we have in the debian branch of the
client repo and I think we're getting close, many thanks to Harlan's great
Once my last batch of fixes  are merged, I think it's time to start
thinking about an upload to Debian unstable. It can take a while to be
accepted into the archive, so it would be better to start soon.
With that in mind, can we start tagging releases of the letsencrypt client?
No need to produce tarballs, maintain a changelog or anything like that, but
tagging releases and incrementing the version number would help us finalize
the package and ensure that everything is fine workflow-wise.
What is the desired versioning scheme for the client? For Debian (and I
assume most distros), the most important thing is that version numbers are
always incrementing. So these work great:
0.1, 0.2, 0.3
0.1.0, 0.1.1, 0.2.0, 0.3.0
20150920, 20151001, 20160101
but these are painful:
More information about the Letsencrypt-devel