jekyll
Where is 3.0?
README.md says there is a version 3.0... But, where is such a release or branch ?
There is no explicit v3.0 branch or release.
The current master is considered as v3.0 even though the gemspec says differently.
This issue has been automatically marked as stale because it has not been commented on for at least two months.
The resources of the Jekyll team are limited, and so we are asking for your help.
If this is a bug and you can still reproduce this error on the master/main branch, please reply with all of the information you have about it in order to keep the issue open.
If this is a feature request, please consider whether it can be accomplished in another way. If it cannot, please elaborate on why it is core to this project and why you feel more than 80% of users would find this beneficial.
This issue will automatically be closed in two months if no further activity occurs. Thank you for all your contributions.
This issue has been automatically marked as stale because it has not been commented on for at least two months.
The resources of the Jekyll team are limited, and so we are asking for your help.
If this is a bug and you can still reproduce this error on the master/main branch, please reply with all of the information you have about it in order to keep the issue open.
If this is a feature request, please consider whether it can be accomplished in another way. If it cannot, please elaborate on why it is core to this project and why you feel more than 80% of users would find this beneficial.
This issue will automatically be closed in two months if no further activity occurs. Thank you for all your contributions.
This issue has been automatically marked as stale because it has not been commented on for at least two months.
The resources of the Jekyll team are limited, and so we are asking for your help.
If this is a bug and you can still reproduce this error on the master/main branch, please reply with all of the information you have about it in order to keep the issue open.
If this is a feature request, please consider whether it can be accomplished in another way. If it cannot, please elaborate on why it is core to this project and why you feel more than 80% of users would find this beneficial.
This issue will automatically be closed in two months if no further activity occurs. Thank you for all your contributions.
This issue has been automatically marked as stale because it has not been commented on for at least two months.
The resources of the Jekyll team are limited, and so we are asking for your help.
If this is a bug and you can still reproduce this error on the master/main branch, please reply with all of the information you have about it in order to keep the issue open.
If this is a feature request, please consider whether it can be accomplished in another way. If it cannot, please elaborate on why it is core to this project and why you feel more than 80% of users would find this beneficial.
This issue will automatically be closed in two months if no further activity occurs. Thank you for all your contributions.
Someone please exclude this issue from @jekyllbot's staleness check. Until there is a new release, it will never be stale.
This issue has been automatically marked as stale because it has not been commented on for at least two months.
The resources of the Jekyll team are limited, and so we are asking for your help.
If this is a bug and you can still reproduce this error on the master/main branch, please reply with all of the information you have about it in order to keep the issue open.
If this is a feature request, please consider whether it can be accomplished in another way. If it cannot, please elaborate on why it is core to this project and why you feel more than 80% of users would find this beneficial.
This issue will automatically be closed in two months if no further activity occurs. Thank you for all your contributions.
This issue has been automatically marked as stale because it has not been commented on for at least two months.
The resources of the Jekyll team are limited, and so we are asking for your help.
If this is a bug and you can still reproduce this error on the master/main branch, please reply with all of the information you have about it in order to keep the issue open.
If this is a feature request, please consider whether it can be accomplished in another way. If it cannot, please elaborate on why it is core to this project and why you feel more than 80% of users would find this beneficial.
This issue will automatically be closed in two months if no further activity occurs. Thank you for all your contributions.
idk if the pinned label will prevent the staleness check, but I'm throwing my hat in the ring as someone who wants 3.0 😁
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 jekyll/minima as the remote theme? My time and attention is limited and a 3.0 release of minima is very low on my priority list at the moment.
Are there workarounds? Of course. There's that remote theme plugin, and there's also fetching the gem from GitHub (gem "minima", :github => 'jekyll/minima', :ref => 'commit-ish_here').
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.