A birthday party is always very exciting, especially the very first one. We have achieved a lot in this year and we have seen a steady stream of new users and contributors to the project. We received great feedback from many people running ChiliProject for their small and medium projects as well as from people running very large instances like the KDE Projects site which hosts Git repositories and provides project management for thousands of developers in the various KDE subprojects.
This release marks a new height as we finally release the long awaited new look-and-feel (new desgin, better usability) into the wild. While we are always working on improving the user experience, this release lays the foundation for the future of ChiliProject.
In ChiliProject 3.0, we introduce a flexible templating system called Liquid. Liquid integration gives users and developers new ways to work with content from various sources and provides the foundation for unprecedented customization options and dynamic content without forcing users to write or deploy Ruby code.
Finally, ChiliProject 3.0 comes with a huge stack of smaller improvements making it more flexible, easy and fun to use.
We are very happy about what we have achieved this past year and confidently look forward to a very bright future.
With this release, the 2.x branch enters maintenance mode. From now on until the release of 4.0.0 (planned for this summer), the 2.x branch will receive security updates only. The final regular version of the 2.x branch is 2.7.0 which was released today.
The old ChiliProject 1.x branch will be considered unsupported from now on. We will not provide any new patches or releases for it. We strongly advise users still running ChiliProject 1.x to update to ChiliProject 3.0.0.
3.0.0 includes 24 new features and 15 bugfixes over 2.7.0. It includes all bug fixes and features of the 2.7.0 release.
The full list of changes is below:
- Bug #558: Reduce version information from Help link
- Bug #653: Multiple query related models defined in one file
- Bug #734: Liquid integration breaks on 1.9.2
- Bug #766: Broken formatting for TOCs
- Bug #774: Gravatar on issue#show is at a weird position
- Bug #778: Textile Caching breaks Liquid
- Bug #780: Setting Cache is not invalidated properly
- Bug #783: Link to new issue on issues list displayed although user is not allowed to create issue
- Bug #791: Allow SSL in POP3 in receive_pop3 task
- Bug #797: Wiki page list is shown as one long list and not a nested one
- Bug #798: Sidebar design looks bad
- Bug #807: History elements overlays revisions in Issues
- Bug #815: Inconsistent margin used for gravatars
- Bug #826: Top right toolbar items overlap for custom issues query
- Bug #827: Group issues by the Status field
- Feature #263: New layout
- Feature #329: Forum replies poorly highlighted
- Feature #604: Liquid Markup on top of Textile
- Feature #649: Update CodeRay to 1.0.0
- Feature #658: Include jquery and jquery ui
- Feature #672: Allow queries to include subproject issues
- Feature #674: Change outgoing email to be sent-per user and not as a single BCC email
- Feature #692: new design with 263-new-layout-ready
- Feature #720: Tagging
- Feature #747: Include capybara for integration tests
- Feature #760: Update quick search to use a partial
- Feature #790: Allow plugins to register custom static and lazy evaluated variables
- Feature #792: Confirmation emails when an incoming email is submitted
- Feature #796: Filter issues based on a date range
- Feature #799: Watch documents
- Feature #800: Allow non-members to watch issues
- Feature #801: Bulk adding issue watchers
- Feature #802: Allow groups to watch issues
- Feature #805: Set watchers on a wiki page
- Feature #806: Set watchers on a Forum or Forum Thread
- Feature #808: Show description changes on issues in a diff
- Feature #809: Bulk add and search for projects when adding a member
- Feature #843: Add config/setup_load_paths.rb to .gitignore
Contributors to 3.0.0
- Eric Davis
- Felix Schäfer
- Gregor Schmidt
- Holger Just
- Jérôme BATAILLE
- Johannes Wollert
- Kornelius Kalnbach
- Moritz Breit
- Romano Licker
- Spencer Markowski
- Toshi MARUYAMA
- And everyone I forgot… You are all awesome!
The upgrade and installation documentation has already been updated for 3.0.0. The update from 2.x to 3.0.0 will be very smooth as we changed very little of the underlying data-storage compared to the previous 2.0.0 release.
Nevertheless, we strongly encourage you to have a full backup in place before starting the upgrade. We do our best to make it a safe experience but there is always the possibility of uncovering yet hidden bugs.
This is the first release in our 3.x series which we will fully support with monthly bugfix releases until the next major ChiliProject version which is due around July 2012. The big goals for that major release are the upgrade to Rails 3.x and the further modularization of ChiliProject.
If you’re interested in participating or contributing to ChiliProject, please leave a comment below or post to our forums. We would love to have your help in polishing the usability or adding exciting new features. Once the upgrade process to Rails 3 has started, we will need as many tester as we can get to iron out the bumps along the way. If you are interested in helping us, just speak up.
In closing, go and download ChiliProject 3.0.0 now.