[Adium-devl] Roadmap changes

[Juan Manuel Palacios]

	Replies inline, trimmed ;-)

On Jul 29, 2006, at 10:19 PM, Christopher Forsythe wrote:

> Replies inline:
>
> On Jul 29, 2006, at 8:57 PM, Juan Manuel Palacios wrote:
>>
>> 	For us trac contributors, it'd be good to know what's the criteria 
>> to decide:
>>
>> -) At this point in the development of 1.0, what constitutes a 
>> blocker? Only regressions? (this seems logical);
>>
>
> At this point it's just regressions.

	Great.

> 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? 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)

>
>> -) 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?

>
> In general,  it should be up to the dev working on that feature to put 
> it into the milestone of their choosing, and assign/accept it to their 
> trac id. At least, that's how we've sorta been handling things up 
> until now.


	Yes sir!

>
>
> 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!

	Regards,....


		Juan