-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Where is 3.0? #656
Comments
There is no explicit v3.0 branch or release. |
This comment was marked as resolved.
This comment was marked as resolved.
Any reason we can't create a 3.0 branch and release? |
This comment was marked as resolved.
This comment was marked as resolved.
. |
This comment was marked as resolved.
This comment was marked as resolved.
Three years since the last tagged release. Will it ever be time? |
I'd also really appreciate a proper release of the newest state! 👀 |
This comment was marked as resolved.
This comment was marked as resolved.
Someone please exclude this issue from @jekyllbot's staleness check. Until there is a new release, it will never be stale. |
This comment was marked as resolved.
This comment was marked as resolved.
. |
😴 Zzzz |
This comment was marked as resolved.
This comment was marked as resolved.
*hits the snooze button again* |
idk if the |
Is there a roadmap of the outstanding work for 3.0? The community might be a little more proactive in helping get it out the door if there were... |
For follks that want the 3.0 version of minima, is there something preventing you from using https://github.com/benbalter/jekyll-remote-theme and specifying |
Are there workarounds? Of course. There's that remote theme plugin, and there's also fetching the gem from GitHub ( But going so long without a release brings into question the maintenance status of this theme, i.e. should we start making plans to migrate onto something else lest a future major Jekyll version update break something? If 3.0 is "done" and just not tagged, we still must wonder whether maintenance will happen when there isn't even enough bandwidth among the maintenance team to tag a release. And if the work for 3.0 is unfinished, that goes doubly so. |
Hi! Some days ago I started a new Jekyl site, I used the It took me some time to discover the minima 2.5 version was last updated 5 years ago. When I noticed that, I switched to branch master and AFAIS, everything looks good. What do you need to do the 3.0 release? I volunteer myself to help you with the 3.0 release. I already submitted a PR #797 to fix a deprecation warning I found on the minima master branch. I can get my hands dirty here, but I'll need some guidelines to do the work properly. BTW, I am looking for a new job. I am offering myself as a volunteer to do this task because I want to gain experience on doing releases, it is something I've never done before on a popular open source project. |
I propose to release the version 3.0 as it is. Just writing a changelog / tag with the breaking changes, fix the deprecation messages and release. |
It is pretty clear 3.0 will never be released unless someone wants to maintain a fork. |
Just release a 3.0 or something. this makes me sadness |
README.md says there is a version 3.0... But, where is such a release or branch ?
The text was updated successfully, but these errors were encountered: