Jump to: navigation, search

Difference between revisions of "Tigerstripe Release Notes"

Line 3: Line 3:
 
The team working on Tigerstripe uses an agile process to work towards a release.  Each release is typically made up of 5-6 iterations and each iteration is three weeks long.
 
The team working on Tigerstripe uses an agile process to work towards a release.  Each release is typically made up of 5-6 iterations and each iteration is three weeks long.
  
Iteration 22 is the last iteration of 0.6 release.  The following are the list of defect/enhancements that have been addressed for each iteration:
+
The following are the list of defect/enhancements that have been addressed for each iteration:
  
 
*'''[https://bugs.eclipse.org/bugs/buglist.cgi?classification=Technology;query_based_on=|;chfieldto=2010-09-03;query_format=advanced;chfieldfrom=2010-08-16;bug_status=RESOLVED;bug_status=VERIFIED;bug_status=CLOSED;product=Tigerstripe;known_name=|| I22 Release Notes]'''
 
*'''[https://bugs.eclipse.org/bugs/buglist.cgi?classification=Technology;query_based_on=|;chfieldto=2010-09-03;query_format=advanced;chfieldfrom=2010-08-16;bug_status=RESOLVED;bug_status=VERIFIED;bug_status=CLOSED;product=Tigerstripe;known_name=|| I22 Release Notes]'''

Revision as of 14:58, 3 September 2010

< To: Tigerstripe

The team working on Tigerstripe uses an agile process to work towards a release. Each release is typically made up of 5-6 iterations and each iteration is three weeks long.

The following are the list of defect/enhancements that have been addressed for each iteration:

Note: Not all the defects required code changes.  Some of them were marked as duplicates or they've already been fixed in the past.  However, everything has been listed to indicate what we've looked into.