[EMAIL PROTECTED] wrote:
> Hi all,
>
> Having trouble wrapping my head around how to really use versions
> well. Specifically in this example:
>
> I have we need to create for next week. There are some "demo
> specific" tickets created to "mock screen x up with this fake thingy"
> and add menu stubs..etc. that's the technical thingy, btw, not the
> superfluous kind :D
>
> {snip}
> Any thoughts on the right/ best way to trac this and set target dates,
> etc? A milestone seems to be the best answer, although I am not sure
> it is the perfect one.
>
>
I'm always interested in how others run Trac as well. I think it depends
a lot on the project type. Here's our set up which I know can be
improved and will be when we set up .11.
Project:
Our project is an MMO.
We might plan 3 to 4 releases (versions) per year. These are major
content upgrades. There might be 25 milestones in a realease and as many
beta releases of the project. We do not use milestones as release
targets though. That may be in part because we do daily internal builds
and know if things are broken. It may also be because we don;t really
care if something non-critical is broken in a test build.
We use version to indicate release version, not reported version for
easiest searching and history tracking.
We use milestones as compartmentalized task sets. Like sprints, except
they might not be short in time. All milestones have due dated that span
our planned task time. There are problems here. The major one is that
ticket owners almost never look at milestones so they have to rely on
priority to know what to do next. This requires constant oversight by
the producer to keep milestones and priorities synched. In a way this is
a good thing as well as it keeps communication ongoing and the producer
always knows the status of just about everything in the project.
For ticket due dates we tried using the T&E plug in. We now mostly use
it simply to update hours worked by the owner and instead use the weekly
updating of the priorities and review of assigned to sketch in an
expected completion of a particular ticket. As you say, you can put a
date on anything you want, as long as it is being diligently worked on,
it will get done when it gets done and if that isn;t fast enough you
probably need to redesign to make the task achievable. Still, the little
PM in me wishes for a better way totask things verse time.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac
Users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/trac-users?hl=en
-~----------~----~----~----~------~----~------~--~---
begin:vcard
fn:Dana V. Baldwin
n:Baldwin;Dana
org:Playnet Inc.;WWIIOL - Battleground Europe
adr;dom:;;1901 Central Drive Suite 400;Bedford;Texas;76021
email;internet:[EMAIL PROTECTED]
title:Senior Producer
x-mozilla-html:TRUE
url:http://www.wwiionline.com
version:2.1
end:vcard
