starred/dehydrated
1
0
Fork 0
mirror of https://github.com/dehydrated-io/dehydrated.git synced 2026-01-11 22:30:44 +01:00
Code Issues 79 Packages Projects Releases 10 Wiki Activity

Please make releases #39

New Issue
Closed
opened 2025-12-29 00:23:02 +01:00 by adam · 4 comments
adam commented 2025-12-29 00:23:02 +01:00
Owner
Copy Link

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?
adam closed this issue 2025-12-29 00:23:02 +01:00
adam commented 2025-12-29 00:23:03 +01:00
Author
Owner
Copy Link

@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...

@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...
adam commented 2025-12-29 00:23:04 +01:00
Author
Owner
Copy Link

@ymc-dabe commented on GitHub (Jan 21, 2016):

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.
adam commented 2025-12-29 00:23:04 +01:00
Author
Owner
Copy Link

@lukas2511 commented on GitHub (Mar 25, 2016):

I've just released version 0.1.0 of this script.

@lukas2511 commented on GitHub (Mar 25, 2016): I've just released version 0.1.0 of this script.
adam commented 2025-12-29 00:23:05 +01:00
Author
Owner
Copy Link

@ymc-dabe commented on GitHub (Mar 30, 2016):

That's just great - thanks a lot!

@ymc-dabe commented on GitHub (Mar 30, 2016): That's just great - thanks a lot!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Complicated
bug
enhancement
help wanted
pull-request
Mirrored from GitHub Pull Request
 suggestions wanted
testing
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/dehydrated#39
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?