Home » 2.x series

Tag: 2.x series

ChiliProject 2.6.0 released

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.

ChiliProject 2.5.0 Released

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.

ChiliProject 2.4.0 Released

ChiliProject 2.4.0 has just been released. It includes some bugfixes for ChiliProject 2.3.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.4 release which includes the security fix.

Download ChiliProject 2.4.0

What’s included

2.4.0 includes 3 new features and 8 bug fixes for 2.3.0. The major highlights of this release are:

  • The bundled Textile library which is used to transform the markup used in issues and wiki pages contained a bug which prevented it from properly escaping certain characters URLs for image tags. This allowed for a persistent cross-site-scripting vector (XSS). The fix for this bug prevents its exploitation for newly entered content as well as for already present text.
  • We tremendously improved our Ruby 1.9 compatibility. While our test suite completely passes for 1.9 we had several reports of encoding issues in the past. With this release we are very confident that these issues should be fixed by now – to the extend possible by the current Rails and Rack implementations. However we still recommend Ruby 1.8.7 or Ruby Enterprise Edition as the most widely deployed ruby variants for ChiliProject.
  • Users running MySQL and Ruby 1.9 should be aware that the mysql database adapter seems not to play nice with Ruby 1.9. We strongly recommend to use mysql2 with Ruby 1.9.
  • Users using the rmagick group to export the Gantt chart as a PNG mentioned that Ruby 1.9 requires rmagick 2.0.0 or newer. Thus we adapted our Gemfile to allow newer versions to be installed. In future versions of ChiliProject we will require rmagick 2 which currently requires rather new distributions. We will announce the deprecation time frame once it has been decided.
  • The project identifier can now automatically be created based on the project name saving project managers some keystrokes.

All users of ChiliProject are strongly advised to update their installations as soon as possible as the resolved security issue allows users able to add or edit content to inject persistent Javascript code into pages.

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.2-stable branch in the repository. You should either upgrade or apply the fix in the issue manually.

The full list of changes are below:

  • Bug #277: News list is missing Avatars
  • Bug #458: rmagick specified in the Gemfile doesn’t build in Ubuntu 11.04
  • Bug #591: ArgumentError (invalid byte sequence in US-ASCII)
  • Bug #640: internal error on journals for deleted custom fields
  • Bug #647: XSS: User input for images is not properly sanitized
  • Bug #652: wrong redirect after login when url contains umlaute
  • Bug #667: Label all input field and control tags
  • Bug #668: Duplicate “Modules” section on Copy Project
  • Feature #221: Use the git sha for the revision
  • Feature #240: Link to global news on projects list
  • Feature #615: Generate project identifier automatically with JavaScript

Contributors to 2.4.0

  • Eric Davis
  • Felix Schäfer
  • Greg Mefford
  • Holger Just
  • Jan Schulz-Hofen
  • Pieter Nicolai
  • Romano Licker
  • Toshi MARUYAMA
  • Etienne Massip
  • Karel Picman
  • Mischa The Evil

We would like to especially thank Mischa The Evil 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.

In closing, go and download ChiliProject 2.4.0 now.

ChiliProject 2.3.0 released

ChiliProject 2.3.0 has just been released. It includes some bugfixes for ChiliProject 2.2.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.3 release which includes the security fix.

Download ChiliProject 2.3.0

What’s included

2.3.0 includes 3 new feature and 4 bug fixes for 2.2.0. The major highlights of this release are:

  • Our Gemfile is more compatible to Windows deployments.
  • The bundled Redmine.pm adapter for connection Subversion repositories to ChiliProjects Authentication and Authorization model now checks that the anonymous user has the actual browser_repository right on public projects. This should only affect very few people. It exposed repositories of public projects where the anonymous user has not given the browse_repository right read-access. Non-public projects were not affected and their content was not exposed.

The full list of changes are below:

  • Bug #594: Wiki Diff somehow off
  • Bug #617: Gemfile: Missing database related platform block for Windows + RubyInstaller
  • Bug #619: Redmine.pm allows anonymous read access to repositories even if Anonymous role prohibits it
  • Bug #633: Update from 1.x to 2.x impossible under rare but valid circumstances
  • Feature #355: Turn on/off the if the start date will autofill by default
  • Feature #566: The “Watcher” filter should show all users.
  • Feature #644: Add Check/Uncheck all links to project form

Contributors to 2.3.0

  • Felix Schäfer
  • Gregor Schmidt
  • Holger Just
  • Igor Zubkov
  • Jan Schulz-Hofen
  • Nick Peelman

A special thanks goes out to Jan Schulz-Hofen for finding and responsibly disclosing the Redmine.pm issue.

In closing, go and download ChiliProject 2.3.0 now.

ChiliProject 2.2.0 Released

ChiliProject 2.2.0 has just been released. It includes many bug fixes for ChiliProject 2.2.0 as well as a couple of security fixes. It is suitable for use on production websites and we recommend that all users download the release as soon as possible.

Download ChiliProject 2.2.0

What’s included

2.2.0 includes 1 new feature and 9 bug fixes for 2.2.0. The major highlights of this release are:

  • Update to Rails 2.3.14 which contains a couple of security fixes:
    • SQL Injection Vulnerability in quote_table_name: (CVE-2011-2930)
    • XSS Vulnerability in strip_tags helper: (CVE-2011-2931)
    • XSS Vulnerability in the escaping function in Ruby on Rails in Ruby 1.9: (CVE-2011-2931)
    • Response Splitting Vulnerability in Ruby on Rails : (CVE-2011-3186)
  • A smarter algorithm to resolve plugin dependencies

The full list of changes are below:

  • Bug #256: requires_redmine_plugin should defer loading plugins if not all dependencies are met
  • Bug #517: Remove included lib/faster_csv.rb
  • Bug #551: Hardcoded French string in wiki/diff.rhtml
  • Bug #552: Hardcoded English string in RepositoriesHelper
  • Bug #557: Calendar links for previous/next month contains double escaped characters
  • Bug #561: PDF export of issue gives TypeError (can’t convert nil into String)
  • Bug #573: acts_as_searchable definition in WikiPage may be insufficient and cause SQL errors
  • Bug #577: Invalid watcher user error when adding an invalid user as watcher
  • Bug #586: TabularFormBuilder doesn’t work with subforms
  • Feature #275: Implement requires_chiliproject and requires_chiliproject_plugin methods
  • Task #584: Upgrade to Rails 2.3.14

Contributors to 2.2.0

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

  • Eric Davis
  • Felix Schäfer
  • Gregor Schmidt
  • Holger Just
  • Jean-Philippe Lang
  • Tom Rochette

The upgrading and installation documentation has already been updated for 2.2.0. If you have not yet upgraded to ChiliProject 2, make sure to follow the upgrading instructions in the release notes.

What’s Next?

This is the fourth release in our 2.0.0 series so we will continue to support it with monthly bugfix releases until around December 2011. Around that time the next major ChiliProject version will be released (3.0.0).

We are working on making ChiliProject leaner by removing custom code and using standard functionality from various gems instead. Based on that we are going to make ChiliProject much easier to install and upgrade. We are also going to introduce the new default theme which — besides looking great — will provide a much better user experience.

If you’re interested in participating or contributing to ChiliProject, please leave a comment below or post to our forums. This time is a great time to start contributing to the project and we would love to have your help with all aspects of ChiliProject.

In closing, go and download ChiliProject 2.2.0 now.

ChiliProject 2.1.1 Released

ChiliProject 2.1.1 has just been released. This release is a security release to fix numerous major security bugs that were discovered in ChiliProject 2.1.1. It contains no other bug fixes or new features. It is suitable for use on production websites and we recommend that all users download the release as soon as possible.

Download ChiliProject 2.1.1

What’s included

2.1.1 includes 1 major security fix for a set of XSS vulnerabilities that the core team discovered late last Friday after the release of 2.1.0.

  • Bug #557: Multiple XSS vulnerabilities

Contributors to 2.1.1

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

  • Eric Davis
  • Holger Just

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

Download ChiliProject 2.1.1

ChiliProject 2.1.0 Released

ChiliProject 2.1.0 has just been released. It includes many bug fixes for ChiliProject 2.0.0 as well as two security bugfixes. It is suitable for use on production websites and we recommend that all users download the release as soon as possible.

Download ChiliProject 2.1.0

What’s included

2.1.0 includes 4 new features and 15 bug fixes for 2.0.0. The major highights of this release are:

  • Fix for a potential XSS vulunerabily on the issue details page
  • Stronger protection from CSRF attacks (CVE-2011-0447)

The full list of changes are below:

  • Bug #191: Add Next/Previous links to the top of search results
  • Bug #467: uninitialized constant Journal::Journaled
  • Bug #498: Wrong filters for int and float custom fields
  • Bug #511: Encoding of strings coming out of SQLite
  • Bug #512: reposman.rb do not work properly in Gentoo Linux.
  • Bug #513: Attached files in “comment” no longer link to file
  • Bug #514: Multiple emails for each forum post
  • Bug #523: Gzipped history of wiki pages is garbeled during an update of an older version to 2.0
  • Bug #530: Start date default should consider timezone
  • Bug #536: CSRF Protection
  • Bug #537: Accessing version of newly created WikiContent results in NoMethodError
  • Bug #540: Hook helper_issues_show_detail_after_setting gets different parameters in Chili 1.x and 2.0
  • Bug #542: Double initial journal for migrated wiki history
  • Bug #543: Journalized touch on journal update causes StaleObjectErrors
  • Bug #544: XSS in app/views/issues/show.rhtml
  • Feature #499: Due date sort order should sort issues with no due date to the end of the list
  • Feature #506: Support for “local” Gemfile – Gemfile.local
  • Feature #526: Bulgarian translation
  • Feature #539: Remove dead code in IssueHelper

Contributors to 2.1.0

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

  • Eric Davis
  • Felix Schäfer
  • Gregor Schmidt
  • Holger Just
  • Ivan Cenov
  • Jan Schulz-Hofen
  • Joernchen of Phenoelit

I would especially like to thank Joernchen of Phenoelit and Jan Schulz-Hofen for reporting the security bugs to us through the correct channels.

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

Upgrading

The upgrading and installation documentation has already been updated for 2.1.0. If you have not yet upgraded to ChiliProject 2.0.0, make sure to follow the upgrading instructions in the release notes.

What’s Next?

This is the second release in our 2.0.0 series so we will continue to support it with monthly bugfix releases until around December 2011. Around that time the next major ChiliProject version will be released (3.0.0). The development team is getting ready to work on the major features for ChiliProject 3.0.0 now. The first one I’m going to work on will be a new theme and layout based on the popular theme from Shane and Peter.

If you’re interested in participating or contributing to ChiliProject, please leave a comment below or post to our forums. This time is a great time to start contributing to the project and we would love to have your help with all aspects of ChiliProject.

In closing, go and download ChiliProject 2.1.0 now.

ChiliProject 2.0.0 Released

Here in the US we are starting our Independence Day weekend. It isn’t normal to give gifts during this holiday but I have a special treat for the ChiliProject community tonight.

ChiliProject 2.0.0 has been released.

The development team has been working hard on this release since Feburary and with the help and support of the community, we’ve finally finished the release candidate process. 2.0.0 is a major release and we’ve done many upgrades to the code.

Please be sure to read this entire annoucement carefully (especially the Upgrade section), as there are some important instructions in here.

What’s included

2.0.0 includes 17 new features and 45 bug fixes over 1.5.0. The major highights of this release are:

The full list of changes are below:

  • Bug #262: Fix line endings
  • Bug #341: Remove English strings from RepositoriesHelper
  • Bug #343: Review Gantt and Calender links from 07cf681
  • Bug #345: Entering large numbers for ‘Estimated Time’ fails with ‘Invalid big Decimal Value’
  • Bug #346: I18n YAML files not parsable with psych yaml library
  • Bug #383: Fix broken tests in unstable caused by conflicting to_utf8 method names
  • Bug #389: Context menu doesn’t work in Opera
  • Bug #390: mysql2 incompatibility in WikiPage model
  • Bug #397: FIXME in generalize_journals migration
  • Bug #398: Remove helper calls from IssuesController
  • Bug #400: Review and fix the Activity event types
  • Bug #401: Move JournalsHelpers from aaj to the core
  • Bug #403: [AAJ] Attachment has it’s files and documents activity provider removed but only documents added
  • Bug #404: Move aaj/app/* to core
  • Bug #405: Move aaj/test/* to core
  • Bug #406: Check for missing Journal code from the AAJ merge
  • Bug #407: Add Journal#visible
  • Bug #408: Check IssueTest#test_saving_twice_should_not_duplicate_journal_details
  • Bug #409: [AAJ] Check that bugfix 784bbccf was merged
  • Bug #411: Issue Notes Preview
  • Bug #412: Test errors on 1.9.2 after acts_as_journalized merge
  • Bug #413: Test errors on 1.8.6 after acts_as_journalized merge
  • Bug #414: Remove returning since it causes deprecation warnings
  • Bug #415: Wikipages don’t store/show the comment correctly
  • Bug #419: Issue list context menu not working in IE9
  • Bug #422: cvs test are not working
  • Bug #423: Remove explicit render from WikiController#show
  • Bug #437: Encoding error on Ruby 1.9 in pdf exports
  • Bug #441: Creating a Journal does not update the journaled record’s updated_at/on attribute
  • Bug #442: Issue atom feed shows “issue creation” journal, didn’t before
  • Bug #443: IssuesControllerTest.test_show_atom test failure on 1.9.2
  • Bug #444: ChangesetTest and RepositoryGitTest test failures on 1.9.2
  • Bug #445: Track initial attributes in a Journal when created
  • Bug #453: Update to Rails 2.3.12 to fix some bugs
  • Bug #466: SVN: Apache initialization error
  • Bug #467: uninitialized constant Journal::Journaled
  • Bug #468: Lost WIKI history timestamps during 2.0.0rc1 upgrade.
  • Bug #469: Wong URL for WIKI activity entries in 2.0.0rc2
  • Bug #474: Changesets are displaying the wrong user and commit date in the Activity
  • Bug #475: News, docs, changesets and time activities were not migrated to 2.0.0rc2
  • Bug #477: Getting rid of “rake/rdoctask is deprecated.” warning
  • Bug #479: Generalize Journals migrations does too much
  • Bug #480: Issue Journal replies get ignored
  • Bug #493: uninitialized constant TimeEntryJournal
  • Bug #501: Updating a ticket that was created by email forces a “change” of description
  • Bug #503: 2.0.0RC3 – YAML Parser fails in ruby 1.9
  • Feature #112: Provide a library function to detect the database type used
  • Feature #123: Review and Merge acts_as_journalized
  • Feature #196: Upgrade to Rails 2.3-latest
  • Feature #197: Rake task to manage copyright inside of source files
  • Feature #216: Remove the rubygems hack from boot.rb
  • Feature #217: Remove the hack to require a specific i18n version in boot.rb
  • Feature #269: Refactor lib/redmine/menu_manager.rb to increase extensibility
  • Feature #279: Optional start date on Versions
  • Feature #288: Review latest Redmine commits
  • Feature #289: Switch to helper :all
  • Feature #290: Add bundler
  • Feature #310: Option to skip mail notifications on issue updates
  • Feature #350: Setting model should use Rails.cache instead of class variable
  • Feature #416: Refactor watcher_tag and watcher_link to use css selectors for the replace action
  • Feature #436: Clean up trailing whitespace and tabs
  • Feature #462: pt-BR translation update
  • Feature #473: pt-BR translation fix
  • Task #123: Review and Merge acts_as_journalized
  • Task #197: Rake task to manage copyright inside of source files
  • Task #288: Review latest Redmine commits
  • Task #291: Update documentation to phase out Ruby 1.8.6
  • From Redmine v1.1.2
    • Defect #3132: Bulk editing menu non-functional in Opera browser
    • Defect #6090: Most binary files become corrupted when downloading from CVS repository browser when Redmine is running on a Windows server
    • Defect #7280: Issues subjects wrap in Gantt
    • Defect #7288: Non ASCII filename downloaded from repo is broken on Internet Explorer.
    • Defect #7317: Gantt tab gives internal error due to nil avatar icon
    • Defect #7497: Aptana Studio .project file added to version 1.1.1-stable
    • Defect #7611: Workflow summary shows X icon for workflow with exactly 1 status transition
    • Defect #7625: Syntax highlighting unavailable from board new topic or topic edit preview
    • Defect #7630: Spent time in commits not recognized
    • Defect #7656: MySQL SQL Syntax Error when filtering issues by Assignee’s Group
    • Defect #7718: Minutes logged in commit message are converted to hours
    • Defect #7763: Email notification are sent to watchers even if ‘No events’ setting is chosen
    • Feature #7608: Add “retro” gravatars
    • Patch #7598: Extensible MailHandler
    • Patch #7795: Internal server error at journals#index with custom fields

Contributors to 2.0.0

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

  • Adam Soltys
  • Ales Zabala Alava
  • Alessio Franceschelli
  • Artem Naluzhnyy
  • Beat Jörg
  • Behrang Noroozinia
  • Ben Gunter
  • Claudio Acciaresi
  • Enderson Maia
  • Eric Davis
  • Etienne Massip
  • Felix Schäfer
  • Gary Verhaegen
  • Gregor Schmidt
  • Holger Just
  • Jean-Philippe Lang
  • Jens Ulferts
  • Jim Naslund
  • Jun NAITOH
  • MAEDA, Go
  • Michal Gebauer
  • Price M
  • Rodrigo Rosenfeld Rosas
  • Simon COURTOIS
  • Tim Felgentreff
  • Tom Kersten
  • Toshi MARUYAMA
  • Wieland Lindenthal
  • Yuki Sonoda
  • Yuya Nishihara
  • and everyone in the ChiliProject community

Upgrading

The upgrading and installation documentation has already been updated for 2.0.0 but I want to mention three major points with this upgrade.

Backup your database… seriously

There are some major data changes in this release, so make sure you backup your database before even attempting the upgrade. The database migration process has been tested by many people but there is always a chance that there will be unexpected bugs we haven’t discovered. A full database backup will give you the option to rollback and undo the upgrade if problems arise.

Give the upgrade time to run

Also due to the data changes, the database migration part of the upgrade could take a long time to run. I’ve personally seen it take 30 and 40 minutes to finish. One user (with a ton of data) reported it taking 4 hours to complete. If you want a rough estimate of how long the migration will take, we found that it takes 1 minute per 1,000 records in the journals table.

Tip: I’d recommend that you run the upgrade in a screen session (or similar) so you can detach from it without stopping the process.

Save a list of any ERROR messages

The upgrade code will do it’s best to convert your old history to the new format but there might be some non-critical errors that are printed to the console. They will be prefixed by “Error” and will have a message like “Error saving: IssueJournal#123 – Start date is invalid”. The upgrade process will automatically continue past these minor errors but you should save a list of them for us to review after the upgrade. Many of them can be safely ignored but I’d like to review the others to make sure there aren’t any bugs in the upgrade. Please start a new thread in the forum and post a copy of any errors you see so we can review them for you.

What’s Next?

This is the first release in our 2.0.0 series so we will continue to support it with monthly bugfix releases until around December 2011. Around that time the next major ChiliProject version will be released (3.0.0). Since everyone has been working so hard on getting 2.0.0 out, we will be holding off on some of the major features for 3.0 in order to help support everyone through the 1.x -> 2.0.0 upgrade process.

If you’re interested in participating or contributing to ChiliProject, please leave a comment below or post to our forums. This time is a great time to start contributing to the project and we would love to have your help with all aspects of ChiliProject. Personally, I’m going to be working on a new design for 3.0.0 and I’d love to work with some web designers to guide the design.

In closing, go and download ChiliProject 2.0.0 now.

ChiliProject 2.0.0 RC3 Released

The third release candidate for ChiliProject 2.0.0 is now out. This release fixes several bugs found in the 2.0.0 RC2 release. While it has been tested already, it is not recommended for use on production websites yet.

Download ChiliProject 2.0.0 RC3

What’s included

The highlights of this release are the:

  • Fixes for the ActsAsJournalized activities and events
  • Fixes for the ActsAsJournalized migrations. You will need to restore a pre-2.0.0 database to test these changes.

The full list of changes are below:

  • Bug #383: Fix broken tests in unstable caused by conflicting to_utf8 method names
  • Bug #397: FIXME in generalize_journals migration
  • Bug #398: Remove helper calls from IssuesController
  • Bug #466: SVN: Apache initialization error
  • Bug #467: uninitialized constant Journal::Journaled
  • Bug #468: Lost WIKI history timestamps during 2.0.0rc1 upgrade.
  • Bug #469: Wong URL for WIKI activity entries in 2.0.0rc2
  • Bug #474: Changesets are displaying the wrong user and commit date in the Activity
  • Bug #475: News, docs, changesets and time activities were not migrated to 2.0.0rc2
  • Bug #477: Getting rid of “rake/rdoctask is deprecated.” warning
  • Bug #479: Generalize Journals migrations does too much
  • Bug #480: Issue Journal replies get ignored
  • Feature #473: pt-BR translation fix

Contributors to 2.0.0 RC3

I’d like to thank all of the contributors to the 2.0.0-RC3 release.

  • Artem Naluzhnyy
  • Enderson Maia
  • Eric Davis
  • Felix Schäfer
  • Gregor Schmidt

What’s Next?

Next we need feedback from you. We are looking for feedback on our documentation like the install or upgrade process and also if you spot any bugs. Then we will release a fourth release candidate or the final 2.0.0 release.
Download ChiliProject 2.0.0 RC3

ChiliProject 2.0.0 RC2 Released

We are happy to announce that the second release candidate for ChiliProject 2.0.0. This release fixes some bugs found in the 2.0.0 RC1 release as we get ready for the final 2.0.0 release. While it has been tested already, it is not recommended for use on production websites yet.

Download ChiliProject 2.0.0 RC2

What’s included

The highlights of this release are the:

  • Upgrade to Rails 2.3.12
  • Fixes for the new ActsAsJournalized feature

The full list of changes are below:

  • Bug #437: Encoding error on Ruby 1.9 in pdf exports
  • Bug #441: Creating a Journal does not update the journaled record’s updated_at/on attribute
  • Bug #442: Issue atom feed shows “issue creation” journal, didn’t before
  • Bug #443: IssuesControllerTest.test_show_atom test failure on 1.9.2
  • Bug #444: ChangesetTest and RepositoryGitTest test failures on 1.9.2
  • Bug #445: Track initial attributes in a Journal when created
  • Bug #453: Update to Rails 2.3.12 to fix some bugs
  • Feature #462: pt-BR translation update
  • Feature #436: Clean up trailing whitespace and tabs

Contributors to 2.0.0 RC2

I’d like to thank all of the contributors to the 2.0.0-RC2 release.

  • Ben Gunter
  • Eric Davis
  • Gregor Schmidt
  • Holger Just
  • Jean-Philippe Lang
  • Rodrigo Rosenfeld Rosas
  • Toshi MARUYAMA

What’s Next?

Next we need feedback from you. We are looking for feedback on our documentation like the install or upgrade process and also if you spot any bugs. Then we will release a third release candidate or the final 2.0.0 release.

Download ChiliProject 2.0.0 RC2