RjOllos
10 years ago
Trac 1.0.5 and 1.1.4 are scheduled for release on the 1st of March
according to the milestones that I've previously proposed. I propose to
wrap up changes to the codebase by 12:00 GMT on 1st of March. Later that
day I can prepare the packages and we can have a few days for testing
before releasing middle of, or late in the week. How does that work for
everyone else?
I've narrowed to 6 the number of owned tickets that I have scheduled for
the two milestones. If you own tickets assigned to the milestone that you
don't plan to complete for this release, please consider moving them to
1.0.6 and 1.1.5.
- Ryan
according to the milestones that I've previously proposed. I propose to
wrap up changes to the codebase by 12:00 GMT on 1st of March. Later that
day I can prepare the packages and we can have a few days for testing
before releasing middle of, or late in the week. How does that work for
everyone else?
I've narrowed to 6 the number of owned tickets that I have scheduled for
the two milestones. If you own tickets assigned to the milestone that you
don't plan to complete for this release, please consider moving them to
1.0.6 and 1.1.5.
- Ryan
--
You received this message because you are subscribed to the Google Groups "Trac Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to trac-dev+***@googlegroups.com.
To post to this group, send email to trac-***@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to the Google Groups "Trac Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to trac-dev+***@googlegroups.com.
To post to this group, send email to trac-***@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.