[Adium-devl] Roadmap changes
chris at growl.info
Sun Jul 30 03:10:34 UTC 2006
On Jul 29, 2006, at 9:53 PM, Juan Manuel Palacios wrote:
> Replies inline, trimmed ;-)
> On Jul 29, 2006, at 10:19 PM, Christopher Forsythe wrote:
>> Replies inline:
>> In general, let the devs handle this portion of it.
> Which would mean...? You guys decide in the first place what's a
> regression and what not?
Basically ya. We do need help finding those though, I don't think any
of us have a 10.3 box for instance.
> If so, we mere trac contributors mortals would have to steer
> totally clear from the 1.0 milestone, unless specifically
> instructed by a dev to modify a given ticket. Is that how you want
> us to handle it? (you'd get to reassign all those pesky non blocker
> tickets to other milestones yourself :-P)
Comment in tickets and alert a dev if it needs to be in 1.0, and let
them decide. That's probably the best action to take.
>>> -) Where do non-blockers go? Some to "sometime after 1.0" or all
>>> to the new 1.0.1? How do we decide?
>> Good question. For those who are just working on tickets, it's
>> probably best to just stick things into "Sometime after 1.0".
>> Anything that should be done, but isn't something that is being
>> worked on currently, will probably sit there if it's not already
>> milestoned somewhere else.
> Heard ya! But bearing my previous question, this would currently
> apply to all tickets.. except for those in the 1.0 milestone, right?
Well, not really. I guess I should be less vague about the way things
are done rather than just assuming.
1.0 is just for regressions right now, 1.0.1 is for regressions/
security fixes/bug fixes/crash fixes. The same with 1.0.2, 1.0.3, so
forth until 1.1. We are going to keep just to that.
The "Sometime after 1.0" milestone is more just for stuff that we
basically can't get to yet, or things like that. But if someone wants
to work on it without it being assigned to a milestone, and it gets
fixed up, then it gets assigned to the next direct milestone, as of
right now that's 1.0. After 1.0 is out, that'd be 1.0.1, etc. This is
why in .81 and .82 and so forth you saw some things changed that
didn't follow the specific rule above.
Or, at least in theory. This is also something we've just started
In general, the biggest help you guys can do is to catch the new
tickets and see if they are dupes, and follow up with users in the
"Needs Feedback" milestone. Those have been really neglected until
you 3 showed up all at once on it.
With the later milestones, we're still kind of up in the air about
what exactly is going into some of them. But for instance, with 1.5,
that's just pure group chat. 1.1 will be as much jabber as can be,
1.2 for 2-3 of the other SoC projects, 1.3 for the last bit, and so
We've been pretty random about what goes into a release and what
doesn't up until now, that isn't going to change much. What is going
to change is that milestones should hopefully be focused on one or
two things, and that's really it.
And on a side note, we're not going to do a huge release like 1.0
>> As a side note, the large amount of tickets being touched this
>> week was due to both edr1084 and matt2. Both have done an
>> outstanding job in clearing out the New tickets. They aren't done
>> yet, but have promised to finish it up shortly.
> /me feels left out, weeps a lonely tear :'-( Seriously though, end
> of semester, the imminent OpenDarwin shutdown and, on top of it all
> to ice the cake up a bit ;-), the DarwinPorts 1.3.1 release all
> have me quite tied up at the moment. Sorry for not taking a more
> integral part in what I came here to do, hope to change that in the
> near future!
Don't worry about it man, long term we need ticket techs. I feel
really awful about the fact that we had tickets that were 9 months
old and weren't touched at all, but everyone was already too busy to
even touch them. You guys have done a rock solid job on that.
We're all doing this on our own, if something in life comes up go to
it, Adium will be here when you get back. :)
More information about the Adium-devl