[Adium-devl] Adium 1.2.1 and beyond

[Matt Handley]

No problem. One day, I may tell you the story of applmak, but that's  
certainly an offlist topic.

I do have time in the next week to be able to work on said  
regressions. Feel free to assign those tickets to me.

Matt

On Jan 9, 2008, at 5:49 PM, Jordan Schelew wrote:

> Perhaps we should have milestones up to 1.2.5 or 1.2.6 and spread  
> some of those tickets across them, with the regressions set to  
> nearer releases and everything else in further ones. There are also  
> many issues (such as crashes) that have been reported recently,  
> along with tickets with debug logging included that are 'ready' to  
> be analysed by someone who knows how to handle them.
>
> I'm curious as to how the applescript 'regressions' are to be  
> handled... since I never used AS (other than the built in scripts)  
> in any previous version of Adium, I can't tell what is a regression  
> and what is not, and where they should be placed (in terms of  
> Milestones). djmori was also commenting on this fact on IRC a  
> couple days ago. Perhaps those should be resolved prior to 1.2.1 as  
> well? Should we assign all of those to applemack? (Sorry if I  
> spelled that wrong).
>
> Jordan
>
> On 9-Jan-08, at 7: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/20080109/a594ff43/attachment-0001.html>