[Adium-devl] Adium 1.2.1 and beyond

[Robert Vehse]

Hey,

like Shawn Khan, I am not an active developer. In fact, as some of  
you may know, I am not a developer at all. I just enjoy following  
Adium's development and would like to add my two cents.

First of all, I think every single one of Evan's propositions makes  
sense.


Am 10.01.2008 um 00:22 schrieb Evan Schoenberg:

> 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 was about to suggest this kind of releasing scheme, assigning only  
a certain amount of tickets to a milestone and releasing minor  
revisiins more often but I didn't dare to in the end. ;) As far as  
I've noticed, this is the way they do it at Pidgin and I can remember  
thinking: "Why not do it this way at Adium?".
I can imagine that it's discouraging to see a three figure amount of  
tickets in a minor milestone...

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

I won't allow myself to say much about it being a good idea to have  
more active developers on the project as I can't contribute any code  
myself but I certainly consider it reasonable to relieve our valued  
Lead Developer of some coding stress.

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


I'd like use this email also to thank to everybody working on Adium  
once again for providing another excellent new version (1.2)! :)


Regards, Robby

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