[Adium-devl] Adium 1.2.1 and beyond

[Jordan Schelew]

Regarding the last part - can't you see that just by viewing closed  
tickets for that version in Trac?

Jordan

On 11-Jan-08, at 9:37 AM, Colin Barrett wrote:

> Excellent ideas!
>
> Perhaps we should have a milestone called "1.2.x" where we can just  
> throw tickets that we want to get done in the 1.2 timeframe, and  
> developers could grab tickets from there and target them at the next  
> open milestone.  One thing that tends to happen is people just  
> throwing tickets into a later milestone, and never really re- 
> triaging those tickets when that milestone rolls around.
>
> I also propose we start using a keyword for tickets that land on the  
> branch, so we can easily see how many we've fixed so far for each  
> release.
>
> -Colin
>
> On Jan 9, 2008, at 3:22 PM, Evan Schoenberg wrote:
>
>> I'd like to release Adium 1.2.1 in the near future, preferably this  
>> weekend some time.  We introduced more than a couple bugs and leaks  
>> in 1.2 which have been fixed for 1.2.1.
>>
>> After that, we have some decisions to make.  Milestone Adium 1.2.1  
>> currently has a ginormous hodgepodge of tickets, far beyond the  
>> scope I'd like to set for future releases.  The open tickets on  
>> that milestone will shift to 1.2.2 (and the existing 1.2.2 to  
>> 1.2.3) once we release 1.2.1.
>>
>> Here's what I propose for releases moving forward:
>>  - Regressions should always be targeted for the next minor  
>> version.  We'll try to fix all known regressions before releasing  
>> the next minor version.
>>  - We'll assign no more than 15 bugs and/or minor enhancements to  
>> each minor revision.  Anyone choosing to accept a ticket -- that  
>> is, declare themselves to be working on it -- can do so and move a  
>> ticket to the next minor revision beyond that number.
>>  - I'd like for each person who considers himself an active  
>> developer to have a hand in each release.  You all know that  
>> despite my insanity I know as well as anyone the demands of Real  
>> Life; let's not make a stressful or problematic change in that  
>> direction. How about we say that each active developer should try  
>> to have accepted and truly be working on (or completed) at least  
>> one ticket in a given milestone?
>>  - We'll release when a milestone is completed with no known  
>> regressions or 1 month has passed since the previous release,  
>> whichever comes first.
>>  - Major new features and significant rewrites (such as the buddy  
>> icon management rewrite I recently did) should end up in the trunk  
>> for release as the next major version.  When feasible, use  
>> microbranches for work which you expect to break trunk while it is  
>> in progress.  (That last bit, of course, will be likely be easier  
>> when we resolve the DVCS question.)
>>
>> What do y'all think about this, in general and in specific?
>>
>> Cheers,
>> Evan
>> _______________________________________________
>> Adium-devl mailing list
>> Adium-devl at adiumx.com
>> http://adiumx.com/mailman/listinfo/adium-devl_adiumx.com
>
> _______________________________________________
> Adium-devl mailing list
> Adium-devl at adiumx.com
> http://adiumx.com/mailman/listinfo/adium-devl_adiumx.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://adium.im/pipermail/devel_adium.im/attachments/20080111/3a82c564/attachment-0001.html>