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

[Policy] Thorium release schedule / process #637

Open
rubyFeedback opened this issue Apr 18, 2024 · 1 comment
Open

[Policy] Thorium release schedule / process #637

rubyFeedback opened this issue Apr 18, 2024 · 1 comment

Comments

@rubyFeedback
Copy link

Right now the last release has happened about a month ago, on March 15. Now we have 17th April.

So, thorium's release cycle is ok-ish I suppose, although I would perhaps prefer a three weeks schedule.

I understand time constraints, so no worries if this can not be done, but I was wondering whether it
would not be better for thorium to think about some kind of regular release schedule - be it 3 weeks,
6 weeks, 9 weeks - you name it. At such a regular time, a new release could be made. Of course more
than the minimum number could be made, so I am not at all against that. My idea here is that it
may be more useful for users to know when to update. Right now I update manually and randomly,
meaning whenever I visit the homepage here, I check for a new release, and then may download this.

If I am the only one who may prefer semi-regular updates then this could be disregarded, but perhaps
others may also prefer some kind of semi-recurring release of changes for thorium.

Right now this may not be so important, but perhaps if we have a small dev-team for thorium, we
could also have some kind of policy in regards to updating the thorium code base more frequently.
This could also help with encouraging people to help with regard to some code changes here and
there; right now the issue tracker contains many different suggestions, only some of which
relate to new code or changes to the code base as such. Specifying a policy in regards to the
release process could be useful, in my opinion.

@Alex313031
Copy link
Owner

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