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

Regarding release cycle of this project #22

Closed
dreamer-coding opened this issue Jan 10, 2021 · 5 comments
Closed

Regarding release cycle of this project #22

dreamer-coding opened this issue Jan 10, 2021 · 5 comments

Comments

@dreamer-coding
Copy link
Contributor

I was wondering if there is a plan to have more releases of the CException project or is 1.3.1 the only release available? Simply asking because I would like to add this to the Dragon WrapDB service and am just wondering if I should subscribe to this repository for any potential releases.

https://dragon-wrap.github.io/

@mvandervoord
Copy link
Member

We occasionally add improvements or fixes... but they are few and far between. This is definitely the most stable project I'm part of... it does its one thing and it does it fairly well. No frills ;)

@dreamer-coding
Copy link
Contributor Author

Alright then but most of those fixes would not go to the end user unfortunately do to how WrapDB databases work.

https://mesonbuild.com/Using-the-WrapDB.html

@mvandervoord
Copy link
Member

Am I understanding correctly that you're suggesting official releases are better because they will trigger updates for people?

I agree with that. I try to push an official release whenever ceedling has a release and this project has had changes in that time. Maybe I've missed some of those opportunities? ;)

@dreamer-coding
Copy link
Contributor Author

With an official release of a project such as this one, it is guaranteed that the author of the package made sure everything was stable before making that release.

Hopefully, there will be new releases soon or whenever you guys feel like throwing the switch, there is at least one to work with.

@mvandervoord
Copy link
Member

:) released. Thanks for the advice, @michaelbrockus . I appreciate it.

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

2 participants