Bunto

Hey there! We have a important update of Bunto for you to enjoy this year. Packed full of bug fixes as usual, thanks to the tireless efforts of our exceptional Bunto community. Three changes to call out:

1. If you’re a big fan of where_by_exp, you’ll be an even bigger fan of group_by_exp.
2. Using a custom timezone in Bunto on Windows? Yeah, sorry that hasn’t ever worked properly. We made it possible to accurately set the timezone using IANA timezone codes.
3. Documentation has been improved, notably on themes, includes and permalinks.

And lots and lots more!

This update was made possible by the dedicated efforts of our excellent contributors.

As always, if you encounter bugs, please do search the issues and file an issue if you aren’t able to find a resolution. We also have our Bunto Talk forum for those of you with general questions about how to accomplish certain tasks with Bunto.

Happy Buntoing!

Well, 3.2.0 has been a success, but with one fatal flaw: it doesn’t work on Windows! Sorry, Windows users. Hot on the trail of 3.2.0, this release should squash that :bug:. Sorry about that!

This release also fixes an issue when using gem-based themes where the theme was rejected if it existed behind a symlink. This is a common setup for the various ruby version managers, and for Ruby installed via Homebrew. Props to @benbalter for fixing that up.

As always, you can see our full changelog on the History page.

Happy Buntoing!

The much-anticipated Bunto 3.0 has been released!

We also added a Code of Conduct to encourage a happier, nicer community where contributions and discussion is protected from negative behaviour.

As always, check out the full history for more details.

Our contributors are the core of what makes Bunto great!

Happy Buntoing!

The pre-release is available!

We also added a Code of Conduct to encourage a happier, nicer community where contributions and discussion is protected from negative behaviour.

Happy developing!

Bunto is an open source project, built one contribution at a time by community members just like you. These community contributions can come in many forms beyond just writing code, from reporting an issue or suggesting a new feature to improving documentation or providing feedback on proposed changes.

If you’ve been looking to get involved with the Bunto community, but didn’t know, we’ve recently made it easier to contribute to Bunto in two ways:

First, we’ve completely rewritten the project’s contributing guidelines, outlining the various ways you can contribute, and including better instructions for submitting proposed changes via GitHub.com or for submitting your first code improvement. And if you have any feedback, we’d love to hear it! Simply click the “improve this page” button in the top right corner of the contributing documentation.

Second, this week, we created six community interest groups, we’re calling Bunto affinity teams. If you’re interested in a particular aspect of the project (or just want to learn more), you can join any one of these teams (or two, or three), to participate in discussions about potential bugs and proposed improvements. And the best part is there’s no commitment. If you just want to listen, or if at any point you want to leave (or switch teams), that’s totally fine. We won’t say a thing. To learn more about the various affinity teams, or to join one (please do!), just head on over to teams.buntowaf.tk.

We hope these changes will make it easier for you to make your first (or second, or third) contribution to Bunto today. Thanks for helping to make Bunto awesome!

Hey! After many months of hard work by Bunto’s contributors, we’re excited to announce the first major release of the project in a long while. v1.0.0 is finally here!

Take a look at the Upgrading page in the docs for more detailed information.

Hey! The first pre-release of the project is finally here!