Hello folks,

I finally had some time to finish going through unassigned trac
tickets.

I renamed the sage-3.0 milestone to sage-feature. The reason is that
sage-3.0 will happen sooner or later and we had lots of tickets
assigned that might or might not happen in that time frame.

Currently we have the following milestones with summaries written by
me:

## sage-2.8.4.2: due in two days.

Any ticket assigned to the milestone should be pretty straight
forward
since this is a pure bug fix release.

## Milestone: sage-2.9: Due in 1 week (09/19/2007)

Reassign tickets as needed. This milestone is getting crowded.

## Milestone: sage-2.9.1: Due in 2 weeks (09/26/2007)

This milestone will be used to clean up issues left over from the
2.9 milestone.

## Milestone: Sage-2.10: No date set

This is the release that will happen after 2.9.x.y. The name might
change, though.

## Milestone: sage-feature: No date set

This is the "big feature" milestone. Tickets assigned here should
have somebody responsible for the issue. Once a feature is ready
to go in please retag the ticket to the next appropriate milestone
and attach a patch/bundle/link to an spkg.

## Milestone: sage-wishlist: No date set

We have many tickets for enhancements in trac that depend on
somebody with time to make them happen. I order not to lose
them we collect them under this milestone. If you are interested
in working on one of the tickets in this category please let us
know or retag that ticket to an appropriate milestone.

## End of milestone list

The assignments I made are arbitrary, so feel free to reassign
any ticket you are interested in.

The 2.9 milestone seems to be very optimistic, especially without
some concentrated effort to close a lot of tickets, i.e. a bug day.
There are several possible days, whether we make this official or
not. I would prefer the 20th or the 22nd September, but obviously
my limited time shouldn't hold you back from choosing another date.

Cheers,

Michael


--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/
-~----------~----~----~----~------~----~------~--~---

Reply via email to