[Adium-devl] Shoot for a 1.2.5b1 on Sunday 13th April

[Eric Richie]

On Apr 8, 2008, at 10:10 AM, Jordan Schelew wrote:

> Agreed - 1.2.5 should definitely be the last release before 1.3.
>
> This week/weekend would be a good time for people working on any bugs
> or enhancements that they plan to include in 1.2.5, to finish them up
> and get them in to the beta for early testing. Since this is the last
> of the 1.2 branch, it would be great to grab some of the ones from the
> 1.2.x milestone as well.
>
> Any that are left over in the 1.2.x milestone after 1.2.5 is released
> will simply be pushed - I plan to rename 1.2.x to 1.3.x so it can
> serve the same purpose for the 1.3 branch, and leave the remaining
> tickets in there. This should work fine, since the tickets that are
> currently there are mostly general enhancements or minor bugs -
> certainly nothing imminent that I can see.
>
> Jordan
>
>
> On 8-Apr-08, at 11:01 AM, Zachary West wrote:
>
>> On Tue, Apr 8, 2008 at 9:09 AM, Jordan Schelew <jas8522 at gmail.com>
>> wrote:
>>> Hey everyone, I'd like to propose to get a beta out for 1.2.5 by  
>>> this
>>> coming weekend. My reasons for doing so are not due to any  
>>> particular
>>> imminent bug fix, but instead in an attempt to get 1.2.5 out by the
>>> current date in Trac. I believe that 1.2.4 was a week later than
>>> originally planned mostly because we didn't get a beta out in time
>>> for
>>> general user regression testing - the sooner we do so, the more
>>> likely
>>> we will be on track for the release of 1.2.5.
>>>
>>> Obviously this wouldn't be a huge concern if this was an earlier
>>> point
>>> release, but as this is going to be the last of the 1.2 branch, the
>>> more testing the better! Plus, if we have no delays in the release  
>>> of
>>> 1.2.5, the sooner we can shift all development to 1.3.
>>
>> Agreed, but let's add another addition to this release, other than
>> trying to push for 1.3:
>>
>> No more releases until 1.3 beta. We need to get 1.3 branched before
>> GSoC even becomes an issue, I think.
>>
>> Zac
>>
>

Yes, as Evan and I both stated at the last meeting, 1.2.5 should be  
the cutoff for the 1.2.x branch.  Devs: if anyone has any particularly  
nagging issues that you would like to have resolved before 1.3, please  
consider taking some time to look them over and get a fix in.  If  
possible I'd like to see us get 1.3 out by the beginning of the  
summer, but if not we definitely still need to at least have it  
branched by the start of GSoC coding as Zac mentioned.  I'd like to  
call a meeting for next week so watch your inboxes for that as I won't  
muddy the thread here.

-Eric