We are proud to announce the second Beta release of the upcoming version 3.0.0 of ChiliProject. Since the release of the 3.0.0beta1 we have fixed some bugs mainly in the areas of caching and the theme.

We also added some new awesome features. We now have more flexible issue filters which allow to filter date ranges and restrict the project scope of queries. We also added a more flexible handling  of emails which is a bit more secure and will allow us to add some more advanced e-mail integration later.

The watchers functionality was heavily extended. It is now possible to add watchers to wiki pages , forum threads, and documents. And you can now bulk-edit watchers of issues.

As previously, we have already updated our own ChiliProject to the new Beta. That said, please be advised that this release is neither feature-complete nor considered stable. Instead it is considered an old-style Beta, not a Beta-cause-it’s-cool (I’m looking at you, Google…) Please download this release, install it in a testing environment, play with it, and report any bugs or missing features. But please don’t install it on your production environment right now without knowing what you are doing (and having a backup).

Download ChiliProject 3.0.0beta2

What’s included

3.0.0beta2 fixes some bugs  and add various features found in the previous Beta. It also contains all features and bugfixes of the previous 2.6.0 release as well as several features and bugfixes of the upcoming 2.7 release.

The full list of changes are below:

• Bug #558: Reduce version information from Help link
• 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 #827: Group issues by the Status field
• 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 #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

Included from the upcoming 2.7.0 release are the following changes:

• Bug #819: RAILS_ENV is not properly set if running under thin
• Bug #822: Initial journal creation fails because of the missing log_encoding of Repositories
• Bug #823: Plugin in new directory not picking up Gemfile

Contributors to 3.0.0beta2

• Eric Davis
• Holger Just
• Gregor Schmidt
• Jérôme BATAILLE
• And everyone I forgot… You are all awesome!

In closing, go and download ChiliProject 3.0.0beta2 now.

GanttProject will be covered by GPLv3 starting from version 2.5. We made this update from GPLv2 mostly for the sake of license compliance with the libraries which we use. For most GanttProject users this requires absolutely no action. GanttProject remains both gratis and libre, you can use it for any purposes, including commercial, given that they are legal per se. Only those who link code of their public proprietary web applications with GanttProject code should be worried, but I really doubt that we have such users.

Thanks to the brave souls who are using GanttProject 2.5 and to the great guys who translate the interface, we now have a new beta with a number of important bugfixes and new translations to German, Spanish, Italian, Dutch and Portuguese.

GanttProject 2.5 beta V download page with packages for Windows, Mac OSX, Linux and platform-independet ZIP distribution.

If you're running a previous beta of GP 2.5, go ahead and download it now, and tell us if it fixes any problems or creates new. If you're a newbie or die-hard, definitely consider at least trying beta V

We hope that the next public build will be a release candidate.

ChiliProject 2.6.0 has just been released. It includes some new features and bugfixes for ChiliProject 2.5.0. It is suitable for use on production websites.

Download ChiliProject 2.6.0

What’s included

2.6.0 includes 6 new features and 8 bug fixes for 2.5.0. None of the bug fixes is security related. The major highlights of this release are:

• ChiliProject is now fully compatible with Ruby 1.9.3
• Plugins needed by the core and user-provided plugins should now be separated. Users are advised to install their custom plugins into vendor/chiliproject_plugins from now on. This helps to distinguish plugins during updates. Existing installations with all plugins in vendor/plugins will continue to work as they used to be.
• Admins using LDAP as an authentication backend can now define arbitrary LDAP filters to further narrow down the elements eligible for authentication.
• rdm-mailhandler.rb which is used for receiving mails is usable again after fixing a regression introduced in 2.5.0
• Small bug fixes and translation improvements.

All users of ChiliProject are encouraged to update their installations as fits. This release contains no security related fixes.

The full list of changes are below:

• Bug #356: Clicking on login while logged-in logs you out
• Bug #463: REST API does not accept Basic HTTP auth when running through Apache mod_proxy
• Bug #708: AAJ does not create journals, when models are created using sub classes
• Bug #740: Revision page, new files are not displayed (Git Repo)
• Bug #746: Problems with rdm-mailhandler.rb
• Bug #748: ChiliProject::VERSION.revision doesn’t capture error output
• Bug #761: Fix quoting in shell-out (git adapter)
• Bug #812: Change references to Redmine
• Feature #298: Seperate core plugins and user plugins into different directories
• Feature #388: Add LDAP filter to ldap authentication
• Feature #486: Do not display edit link in annotation page when you don’t have permissions
• Feature #733: Add css class for issues that are due today
• Feature #785: pt-BR translation updates
• Feature #789: Provide a rackup file for Rack-only servers like pow.cx

Contributors to 2.6.0

• Enderson Maia
• Eric Davis
• Felix Schäfer
• Florian Mutter
• Gregor Schmidt
• Holger Just
• Jean Philippe Lang
• Moritz Breit
• Spencer Markowski
• Tom Rochette

What’s Next?

We are working on the final features and bug fixes for the next beta for ChiliProject 3.0.0. If you’re interested in participating or helping out the development, please leave a comment below or post to our forums.

This release marks the beginning of the end of the 2.x release cycle. Depending on how many bugs emerge until the release of 3.0.0 we will probably issue a last normal release shortly after 3.0.0 is released later this month. After that, the 2.x branch will enter maintenance mode and will only receive security updates until the release of 4.0.0 in summer.

After the release of 3.0.0 the 1.x branch will stop to be supported at all. We will not issue and more releases, bugfixes or security patches for this branch anymore. If you are still using ChiliProject 1.x, you are strongly advised to upgrade to either 2.6.0 or to 3.0.0 as soon as possible.

In closing, go and download ChiliProject 2.6.0 now.

We are proud to announce the first Beta release of the upcoming version 3.0.0 of ChiliProject. When you read this announcement it means that the new and shiny 3.0.0 release is not far away anymore. This Beta release gives a first mostly complete look at the new features in 3.0.0. We expect to have a first Release Candidate on 2011-12-31. The final 3.0.0 release is scheduled to be in early January.

Because of the really great improvements we have already updated our own ChiliProject to the new Beta. That said, please be advised that this release is neither feature-complete nor considered stable.  Instead it is considered an old-style Beta, not a Beta-cause-it’s-cool (I’m looking at you, Google…) Please download this release, install it in a testing environment, play with it, and report any bugs or missing features. But please don’t install it on your production environment right now without knowing what you are doing (and having a backup).

Download ChiliProject 3.0.0beta1

Now that you have survived the disclaimer, be prepared for awesomeness. This release includes the long awaited new design as well as a completely new wiki template engine which allows you to create dynamic wiki pages curated with your content. It also contains the foundation for a built-in tagging system.

The New Design

The new design is a first step into the complete overhaul of the ChiliProject user experience. It sports a modern look and a completely re-thought interaction model.

Gone are the days of the plethora of tabs that start to scroll on even medium-sized windows. We now have an ever-present navigation on the sidebar which allows for easier access and a better navigation model. Related functions are grouped together preventing a lost-in-space feeling.

We have greatly improved the contrast and font-sizes which makes ChiliProject more approachable to anyone. Blind or otherwise disabled people will love the new design as it greatly improves compatibility with screen readers and other support devices.

This beta release is the beginning of the end of a long journey to improve the user experience of ChiliProject which started about 2 years ago as it was still Redmine. A great deal of work from Eric Davis, the whole Finnlabs crew and some other contributors is going to mark this 3.0.0 release the biggest release in ChiliProject’s history.

The Liquid Template Language

ChiliProject inherited the old macro concept of Redmine which allowed to include a wiki page into another and to provide plugin authors with the ability to extend the standard textile markup language with additional functionality. This worked great at its time. However it became evident that a powerful templating system would provide users with much richer capabilities to display and organize content.

The Liquid template language completely replaces the old macro system and makes it even more mighty. It supports variables, includes facilities to display text based on conditions and even has loops. That allows users to create dynamic wiki pages based on many different data pieces in ChiliProject.

While it now brings minimal support for querying, remixing and displaying internal ChiliProject data, it allows us to easily extend the API. Users can then create custom issue or time reports inside a wiki without having to write a single line of Ruby code. It’s all inside the wiki editor.

Plugin developers can extend the language and create new tags, filters, and data APIs called drops  to provide access to many different data sources. It gives them much more flexibility in what ways to represent their data and allows users to easily remix, combine, and display different pieces of data.

The Tagging foundation

Yes, that’s correct. ChiliProject will finally have a tagging engine. This will allow you to organize your data in any way you like. We will be able to create issue tags to group issues and to instantly find the important ones. Or you can organize your Wiki with tag clouds to have a free-form order schema.

The technical foundation is in place right now but is not exposed to the user. In future releases (and maybe even for the final 3.0.0 release) we will add features which use it to allow you to keep control over your data.

What’s included

3.0.0beta1 sports the new design and the Liquid template language as well as several smaller new features and bugfixes. It also contains several features and bugfixes of the upcoming 2.6 release.

The full list of changes are below:

• 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
• Feature #263: Feature #263: New layout
• Feature #329: Feature #329: Forum replies poorly highlighted
• Feature #604: Feature #604: Liquid Markup on top of Textile
• Feature #649: Feature #649: Update CodeRay to 1.0.0
• Feature #658: Feature #658: Include jquery and jquery ui
• Feature #672: Feature #672: Allow queries to include subproject issues
• Feature #692: Feature #692: new design with 263-new-layout-ready
• Feature #720: Feature #720: Tagging
• Feature #747: Feature #747: Include capybara for integration tests
• Feature #760: Feature #760: Update quick search to use a partial

Included from the upcoming 2.6.0 release are the following changes:

• Bug #356: Clicking on login while logged-in logs you out
• Bug #463: REST API does not accept Basic HTTP auth when running through Apache mod_proxy
• Bug #708: AAJ does not create journals, when models are created using sub classes
• Bug #740: Revision page, new files are not displayed (Git Repo)
• Bug #746: Problems with rdm-mailhandler.rb
• Bug #748: ChiliProject::VERSION.revision doesn’t capture error output
• Bug #761: Fix quoting in shell-out (git adapter)
• Feature #298: Seperate core plugins and user plugins into different directories
• Feature #388: Add LDAP filter to ldap authentication
• Feature #486: Do not display edit link in annotation page when you don’t have permissions
• Feature #733: Add css class for issues that are due today

Contributors to 3.0.0beta1

• elm
• Eric Davis
• Felix Schäfer
• Gregor Schmidt
• Holger Just
• Johannes Wollert
• Kornelius Kalnbach
• Moritz Breit
• Romano Licker
• Spencer Markowski
• And everyone I forgot… You are all awesome!

In closing, go and download ChiliProject 3.0.0-beta1 now.

I’ve just upgraded ChiliProject.org to use the new design we are releasing as part of ChiliProject 3.0. There is still a lot of fit and finish we will be adding but the overall structure is finalized.

If you want to see what is possible with this new design, my own ChiliProject installation is also running the new design but with a custom theme. The custom theme is 100% CSS and images. This shows how much flexibility you’ll have when creating your own theme, even if you don’t know Ruby or Rails.

If you haven’t seen the new design, head over to ChiliProject.org, check it out, and leave any comments for us here.

ChiliProject 1.5.5 has just been released. This release is a security release to fix a cache poisoning bug in the bundle Redmine.pm module which can be used for authenticating and authorizing subversion or git users for repositories served through Apache. It contains no other bug fixes or new features and is released for users who are unable to upgrade to ChiliProject 2.5.0. It is suitable for use on production websites running ChiliProject 1.x and we highly recommend that 1.x users download the release.

Download ChiliProject 1.5.5

What’s included

1.5.5 includes a security fix which was back ported from ChiliProject 2.5.0.

• Bug #709: Redmine.pm potential security issue with cache credential enabled and subversion

All users of ChiliProject who use the bundled Redmine.pm module are strongly advised to update their installations as soon as possible as the resolved issue potentially allows users to access restricted repository data.

Users of Redmine should be advised that the fixed issue is also present there. There is currently no Redmine release that fixes the it. Currently it is only addressed in the trunk and 1.3-stable branch in the repository. You should either upgrade or apply the fix in the issue manually.

Contributors to 1.5.5

I’d like to thank all of the contributors to the 1.5.5 release.

• Holger Just
• Jean-Philippe Lang

We would like to especially thank Niels Lindenthal who informed us of the security issue.

If you think you have found a security issue in ChiliProject please report it to the security team privately so we can follow responsible disclosure.

What’s Next?

The 1.x versions of ChiliProject are officially in maintenance mode and will only be getting security updates until the release of 3.0 in early January. After that date the 1.x branch is no longer supported in any way. We recommend upgrading to the current stable version of ChiliProject in order to get general bug fixes and features, currently ChiliProject 2.5.0.

ChiliProject 2.5.0 has just been released. It includes some bugfixes for ChiliProject 2.4.0 as well as one security fix. It is suitable for use on production websites and we recommend that all users download the release as soon as possible.

Users of the old 1.x release branch, please check the 1.5.5 release which includes the security fix.

Download ChiliProject 2.5.0

What’s included

2.5.0 includes 3 new features and 9 bug fixes including 1 security fix for 2.4.0. The major highlights of this release are:

• The provided perl module Redmine.pm for authenticating and authorizing subversion or git users for repositories served through Apache was vulnerable to a cache poisoning attack if caching was enabled. The vulnerability could result in a temporary permissions escalation giving a user write permission to a repository she normally had only read permission. The fix will be immediately active after installation and reboot of the Apache the Redmine.pm is installed on.
• Registered but not-yet activated users can now be deleted.
• ChiliProject will be transitioning to jQuery as the primary javascript library for client-side scripting. To ease the transition, plugin developers can query ChiliProject::Compatibility to decide if they want to use the to-be-bundled jQuery or use a version they bundle with their plugin. ChiliProject::Compatibility can also be queried to check for the presence or absence of Prototype.
• 2 view hooks have been added to the Project index.
• Still more Ruby 1.9 compatibility fixes.
• The vendored ruby-net-ldap gem has been removed and replaced by an updated version (now called net-ldap) in the Gemfile.
• Small bug fixes and translation improvements.

All users of ChiliProject are strongly advised to update their installations as soon as possible.

Users of Redmine should be advised that the fixed security issue of Redmine.pm is also present there. There is currently no Redmine release that fixes the it. Currently it is only addressed in the trunk and 1.3-stable branch in the repository. You should either upgrade or apply the fix manually.
The full list of changes are below:

• Bug #258: Upgrade from ruby-net-ldap to net-ldap gem
• Bug #554: Failed to migrate from 1.2.0 to 2.1.0 with Ruby 1.9.2
• Bug #688: doc/CHANGELOG.rdoc is very huge
• Bug #698: Searching in issue is broken on ruby 1.9
• Bug #707: Wiki diffs: incompatible character encoding error on Ruby 1.9.2
• Bug #709: Redmine.pm potential security issue with cache credential enabled and subversion
• Bug #711: translation missing: en, field_lock_version on issue edit on Ruby 1.9
• Bug #735: any user can edit time entries via context menu
• Bug #736: Adding users with a dash “-” in email address is broken sometimes
• Feature #124: User deletion
• Feature #706: Add hooks to view projects/index.rhtml
• Feature #725: Compatibility check for jQuery and Prototype availability

Contributors to 2.5.0

• David O
• Eric Davis
• Felix Schäfer
• Gregor Schmidt
• Holger Just
• Ivan Cenov
• Jan Schulz-Hofen
• Jean Philippe Lang
• Moritz Breit

We would like to especially thank Niels Lindenthal and Jan Schulz-Hofen who informed us of the (potential) security issues. If you think you have found a security issue in ChiliProject please report it to the security team privately so we can follow responsible disclosure.

In closing, go and download ChiliProject 2.5.0 now.

Now when GanttProject 2.5 "Praha" is approaching the release, we need to update translations, so that it could speak your native language. GanttProject 2.0.10 was translated to 28 languages and we'd love to keep all of them. However, at the moment being only 7 languages are in a good shape, and we need your help. If you have a few spare hours, some linguistic skills and a good will to help us, please join our translations team! We need German, Japanese, Spanish, Italian and Chinese translations most of all.

Learn how to translate GanttProject to your language