Posts in category installation

Version 0.5.0 now available

NEW RELEASE - 0.5.0

Based on  Trac 0.11.7 this release adds some significant improvements.

  • #904 - Tickets can now be added to an iteration using a ticket action.
  • #27 - An assigned ticket is shown as orange for the next incomplete completion stage. This provides a fast visual indication of whether someone is working on a ticket or not.

  • #905 - Progress bar legends and completion stage status is now shown correctly in Chrome (recently Chrome's rendering broke and stopped displaying these items correctly).

To Upgrade Your Installation

1. Upgrade the Agile-Trac plugin

easy_install -U http://svn.agile-trac.org/BRANCH/AGILE-TRAC/SOURCE/0.11/REL/

2. Update the patch

You must also use svn to update your agile-trac patch.

Note: The location of your  Trac install will depend on the version number, for example you might have  Trac 0.11 or a newer version like  Trac 0.11.7.

Windows

This will depend on your installation, for example with  Trac 0.11, this may work.

cd C:\Python25\Lib\site-packages\Trac-0.11-py2.5.egg

Linux

Do these commands as a user of sufficient privileges, for example as root.

This will depend on your distribution. For example in Debian Testing for  Trac 0.11 you might type:

cd /usr/lib/python2.6/site-packages/Trac-0.11-py2.6.egg/

Now run svn update from the current location, for example,

svn update

3. Restart you web server

For example if you are using apache you might need to execute,

apache2ctl graceful

Version 0.4.0 now available

NEW RELEASE - 0.4.0

Based on  Trac 0.11.7 this release adds two notable features.

  • Predicted completion dates for milestones of the same priority are now determined based on their relative weighting (defaulted to the same). This means that milestones of the same priority are considered to run in parallel with the observed points per period value spread across the milestones based on their relative weights. See also Milestone Priority and Relative Weight
  • It is now possible specify the number and weights of previous iterations that should be considered when determining the observed points per iteration. The default is for the current and previous four iterations to be used with each treated as having an equal weight. In other words the average is taken. This can be added to the trac.ini file as:
    [agile-trac]
    historical_iteration_weights = 1 1 1 1 1
    
    The number of weights specified is the number of iterations considered and the weights can be any values and may be floats. See also Determining how past Iterations are used to Calculate Points Per Iteration

To Upgrade Your Installation

1. Upgrade the Agile-Trac plugin

easy_install -U http://svn.agile-trac.org/BRANCH/AGILE-TRAC/SOURCE/0.11/REL/

2. Update the patch

You must also use svn to update your agile-trac patch.

Note: The location of your  Trac install will depend on the version number, for example you might have  Trac 0.11 or a newer version like  Trac 0.11.1.

Windows

This will depend on your installation, for example with  Trac 0.11, this may work.

cd C:\Python25\Lib\site-packages\Trac-0.11-py2.5.egg

Linux

Do these commands as a user of sufficient privileges, for example as root.

This will depend on your distribution. For example in Debian Testing for  Trac 0.11 you might type:

cd /usr/lib/python2.5/site-packages/Trac-0.11-py2.5.egg/

Now run svn update from the current location, for example,

svn update

3. Restart you web server

For example if you are using apache you might need to execute,

apache2ctl graceful

4. Upgrade your trac environment

Since this release includes a schema change you will need to run,

trac-admin upgrade /path/to/your/trac/project

so that the schema changes required can be applied.

Version 0.3.0 now available

NEW RELEASE - 0.3.0

The 0.3.0 release marks some significant back-end changes and some general improvements overall. It is recommended that all users upgrade to this latest release.

  • Notably an important schema change was introduced to allow efficient mapping between tickets and iterations. This mapping is now visible on the Roadmap and on each Ticket where you can see which Iterations a ticket is associated with. This association is achieved through the addition of a new iteration_ticket table in the database.
  • This release is up-to-date with the latest stable release of  Trac, at the time of release that is  Trac 0.11.5.
  • Finally it important to note that this release would not have been possible without the help of dfraser who recently joined the development team and has already made a significant impact on the project. Long time users will remember his name from the 0.2.0 release where he provided at least one patch and other valuable feedback.

To Upgrade Your Installation

1. Upgrade the Agile-Trac plugin

Upgrade your plugin using easy_install as shown. Ensure you have administrative privileges, for example if using Linux you might need to run this as root or prepend the command with sudo.

easy_install -U http://svn.agile-trac.org/BRANCH/AGILE-TRAC/SOURCE/0.11/REL/

2. Update the patch

You must also use svn to update your agile-trac patch.

Note: The location of your  Trac install will depend on the version number, for example you might have  Trac 0.11 or a newer version like  Trac 0.11.1.

Windows

This will depend on your installation, for example with  Trac 0.11, this may work.

cd C:\Python25\Lib\site-packages\Trac-0.11-py2.5.egg

Linux

Do these commands as a user of sufficient privileges, for example as root.

This will depend on your distribution. For example in Debian Testing for  Trac 0.11 you might type:

cd /usr/lib/python2.5/site-packages/Trac-0.11-py2.5.egg/

Now run svn update from the current location, for example,

svn update

3. Restart you web server

For example if you are using apache you might need to execute,

apache2ctl graceful

4. Upgrade your trac environment

Since this release includes a schema change you will need to run,

trac-admin upgrade /path/to/your/trac/project

so that the schema changes required can be applied.

Refer to Installing Agile-Trac for more details.

Version 0.2.0 now available

NEW RELEASE - 0.2.0

This is an important release with several noteworthy points.

  • we've created a release branch starting with 0.2.0 to allow more aggressive changes to be made on the development branch. For those who don't mind the odd breakage then you are free to install and update from the development branch. Details for the release branch can be found on the installation page. Branch details are summarised at the end of this post.
  • we've moved to a single unified patch for all 0.11.x trac installs. This will significantly reduce the overhead of making updates. We held off doing this as there were some version specific issues that are now all resolved. In essence the unified patch will be against the latest trac release on the 0.11 branch.
  • we've fixed quite a few annoyances, some of which were considered critical. These are listed below. Some great community support has made these fixes possible.
  • we've ironed out database back-end issues so that we work with both Sqlite and Postgresql (including 8.3). If you have an Sqlite install and would like to migrate to Postgresql then you can read more on the Migration from Sqlite to Postgresql page.
  • we've added some improved documentation for the configuration options currently supported by Agile-Trac.

Some Stories and Defects addressed in 0.2.0

There have been more changes than those listed and some incremental changes for stories which are not yet complete, however some of the highlights are shown in the list below.

  • #91 - Error when an iteration contains a story that does not belong to a milestone. Many thanks go to augustinus for reporting this and providing a patch!
  • #101 - Previewing a ticket when progressing a completion stage resulted in an error. Many thanks go to dfraser for reporting this and providing a patch!
  • #67 - Ticket changes were not being saved when a ticket had custom fields
  • #75 - Workflow bug where a completed story because of resizing to 0 is not DONE
  • #76 - No notification email sent when a story is partially complete
  • #97 - Makes it possible to reset the calculation of points per iteration to account for large team size changes.
  • #98 - Provides an indication what the date calculations on the Roadmap are based on.
  • #105 - Documents and provides working support for custom completion stages

To Upgrade Your Installation

Upgrade your plugin using easy_install as shown. Notice the new URL for this release,

sudo easy_install -U http://svn.agile-trac.org/BRANCH/AGILE-TRAC/SOURCE/0.11/REL/

You must also use svn to checkout the new unified patch, replacing your previous patch.

sudo svn co http://svn.agile-trac.org/BRANCH/AGILE-TRAC/SOURCE/0.11/REL/patch/trac/ trac

Refer to Installing Agile-Trac for more details.

New Trac-0.11.x Agile-Trac Branches

There is now a development and release branch for the Trac-0.11.x version of Agile-Trac.

The URL for the development branch is:

The URL for the release branch is:

Starting with SVN revision 270 it is now possible to install Agile-Trac onto a trac install using Postgresql 8.3

svn update required

As many of you might know, using trac with an  SQLite database on the back-end is not a very scalable solution. With a very large database and or many users you'll get a slow trac or even database lockups. Moving to  PostgreSQL will address most of these problems. However, starting with  PostgreSQL 8.3 type checking became stricter and many plugins do not work well. Included in those was Agile-Trac. However since r270 Agile-Trac now works as expected with  PostgreSQL 8.3.

Starting with SVN revision 247 it is now possible to install Agile-Trac onto an exisitng environment

svn update required

Previously it was not clear how best to install Agile-Trac onto an existing trac environment - with existing tickets. After sufficient experience of Agile-Trac in the real world a simple strategy has been adopted to handle this scenario and has allowed ticket:44 to be finally addressed.

There are two key areas that have caused difficulties. First Agile-Trac relies on the data stored in the ticket_completion table to calculate information relevant to ticket groups (like milestones and iterations), and second, the milestones themselves have an additional priority field in Agile-Trac which is used to help order milestones on the Roadmap view.

Starting with SVN revision 247 ticket completion fields and milestone priorities are lazily created so it is not required that they exist in the database. For milestones this has actually not been an issue for some time now, but for ticket completion fields it was unclear what an appropriate default set of values were.

The approach taken is this:

  • If a ticket does not yet have a status of closed then the initial size values are considered to be undefined.
  • If a ticket has been resolved to a status of closed then the size values for the ticket are considered to be 0.

The reason for considering closed tickets to have a sizing of 0 is actually quite simple. We use the sizing only to associate the progress of a ticket with a time duration - an iteration, and since these tickets were closed previously that association does not exist. Hence we treat as having a 0 size. This aligns well with the notion of a fixed ticket being simply available. The recommendation in fact is to rename the fixed resolution to available and make another resolution, for example split or invalid the default resolution.