Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Please do a release #941

Open
someone-somenet-org opened this issue Jul 30, 2024 · 8 comments
Open

Please do a release #941

someone-somenet-org opened this issue Jul 30, 2024 · 8 comments

Comments

@someone-somenet-org
Copy link

It has been almost 2 years since the last release and people will feel like this project died

(Please do at least 1 release every 6 months, even if nothing seriously changed)

@bllfr0g
Copy link

bllfr0g commented Jul 30, 2024 via email

@polyzen
Copy link

polyzen commented Jul 30, 2024

It would be nice not to have to backport 4fd777e.

The reasoning you have given, however, is not a good reason for cutting releases, and creates needless churn and work for people packaging this software.

@lukas2511
Copy link
Member

Project is not abandoned, I'm regulary checking that everything still works and keep up to date with changes with the ACME protocol.

I'm in a weird position where I started rewriting dehydrated a few times in different styles, but abandoned those rewrites because they just didn't seem good enough, but unfortunately that took away time to actually make changes to the original codebase... The reason for the rewrites is that a) I want to implement some features that would be really messy to implement in the current code (mostly automation and logging stuff) and b) I want something more modular, so changes could be easier tracked and parts of the code tested using automated means.

I guess I should just re-prioritize working on the existing code instead... at least that's something that's proven stable.

@someone-somenet-org
Copy link
Author

I know that feeling ... I had sooo many projects which I wanted to fully rewrite ... and ... I abandoned all of the rewrites.

The reasoning you have given, however, is not a good reason for cutting releases, and creates needless churn and work for people packaging this software.

We will have to agree to disagree, its imo much more important to look alive, to attract new users and possibly contributors and package-maintainers.

@bllfr0g
Copy link

bllfr0g commented Jul 30, 2024 via email

@someone-somenet-org
Copy link
Author

My experience is incremental change is more likely to succeed. If you plan to rewrite the whole thing from scratch — it’s unlikely to happen. Instead, refactor parts of it at a time. Little by little — and before you know it, the whole thing will be done!

This doesnt work if you want to change the language, tho. :(

@lukas2511
Copy link
Member

My experience is incremental change is more likely to succeed. If you plan to rewrite the whole thing from scratch — it’s unlikely to happen. Instead, refactor parts of it at a time. Little by little — and before you know it, the whole thing will be done!

This doesnt work if you want to change the language, tho. :(

Language and dependencies will definitively stay the same. I have no interested in writing an ACME client in a different language, even though that would probably be a lot easier than doing it in bash 🙃

@j3g
Copy link

j3g commented Sep 16, 2024

I have to admit I am here looking at issues to see if this project is abandoned. Any small release gives everyone assurances that the project is active. Thanks for all your work! I'm a fan!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants