Originally created by @ymc-dabe on GitHub (Jan 20, 2016).
I'm currently working on some Debian packaging for letsencrypt.sh and it would be really helpful to base this on releases (rather than some random commits in git).
Would you mind using some version schema and do a release from time to time?
Originally created by @ymc-dabe on GitHub (Jan 20, 2016).
I'm currently working on some Debian packaging for letsencrypt.sh and it would be really helpful to base this on releases (rather than some random commits in git).
Would you mind using some [version schema](https://en.wikipedia.org/wiki/Software_versioning) and do a release from time to time?
I find it really hard to decide at which point I'd want a new version release.
Things are changing all the time and it now slowly starts becoming a bit more structured and stable, but i still don't feel like marking the code as "released".
At some point I may give it a version number, but at the moment it just doesn't feel right...
@lukas2511 commented on GitHub (Jan 21, 2016):
I find it really hard to decide at which point I'd want a new version release.
Things are changing all the time and it now slowly starts becoming a bit more structured and stable, but i still don't feel like marking the code as "released".
At some point I may give it a version number, but at the moment it just doesn't feel right...
Okay, that's alright. I opened an ITP on bugs.debian.org for a "0.0.02016.01.21git23b0ef5" version. This hopefully will be a low enough version to not increase the Debian epoch, once you're doing releases of letsencrypt.sh.
For me it's okay, if you prefer to close this GitHub issue.
@ymc-dabe commented on GitHub (Jan 21, 2016):
Okay, that's alright. I [opened an ITP on bugs.debian.org](https://bugs.debian.org/812174) for a "0.0.0~2016.01.21~git23b0ef5" version. This hopefully will be a low enough version to not increase the Debian epoch, once you're doing releases of letsencrypt.sh.
For me it's okay, if you prefer to close this GitHub issue.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @ymc-dabe on GitHub (Jan 20, 2016).
I'm currently working on some Debian packaging for letsencrypt.sh and it would be really helpful to base this on releases (rather than some random commits in git).
Would you mind using some version schema and do a release from time to time?
@lukas2511 commented on GitHub (Jan 21, 2016):
I find it really hard to decide at which point I'd want a new version release.
Things are changing all the time and it now slowly starts becoming a bit more structured and stable, but i still don't feel like marking the code as "released".
At some point I may give it a version number, but at the moment it just doesn't feel right...
@ymc-dabe commented on GitHub (Jan 21, 2016):
Okay, that's alright. I opened an ITP on bugs.debian.org for a "0.0.0
2016.01.21git23b0ef5" version. This hopefully will be a low enough version to not increase the Debian epoch, once you're doing releases of letsencrypt.sh.For me it's okay, if you prefer to close this GitHub issue.
@lukas2511 commented on GitHub (Mar 25, 2016):
I've just released version 0.1.0 of this script.
@ymc-dabe commented on GitHub (Mar 30, 2016):
That's just great - thanks a lot!