Adium 1.4b18/1.3.11?

Christopher Forsythe chris at growl.info
Sat Apr 24 00:41:47 UTC 2010


I think what needs to happen first is to identify what can be moved out of
the 1.4 milestone. So, if someone could do that, that's probably the best
thing to do first.

So, answer this question:

What would cause problems if 1.4 was released today? As in, must release
1.4.1 or else! type of problems.

In other words, what on this list can go?

http://trac.adium.im/query?status=assigned&status=new&group=severity&milestone=Adium+1.4


Chris

On Fri, Apr 23, 2010 at 3:54 PM, Alan Humpherys <alangh at adium.im> wrote:

> I'm game for that.   I really want to get back into things and help out.
>  I'm totally up for it if you just want to throw something my way.
>
> - Alan
>
>
>
> On Apr 23, 2010, at 1:37 PM, Colin Barrett wrote:
>
>  This plan sound good to me. I've moved and my schedule has calmed down
>> enough that I can probably squeeze in some time. I'll track down Steve Holt
>> and we can knock our brains together.
>>
>> -Colin
>>
>> On Apr 23, 2010, at 8:27 AM, Evan Schoenberg, M.D. wrote:
>>
>>
>>> On Apr 22, 2010, at 8:03 AM, Alan Humpherys wrote:
>>>
>>>  I must confess to being a complete novice when it comes to integration
>>>> of a new libpurple version into our code base, but seeing the relatively
>>>> large numbers of patches which are necessary to fix security and
>>>> compatibility issues in our existing version, I wonder if it wouldn't be
>>>> better to pull the new version of the library and do both a 1.3.11 and a
>>>> 1.4B18 release with it.  (Of course, I defer to the experts on the wisdom of
>>>> that path).
>>>>
>>>
>>> Doing a major libpurple version upgrade on the 1.3 branch would be a
>>> large undertaking; I definitely don't think it's worth doing.  A minimal
>>> release with the plucked changes to fix some protocol breakages seems
>>> reasonable, and it should easy enough to do.
>>>
>>>  I know that I haven't been active in the project, but have some time
>>>> over the next weeks that I can invest.  (It would also be great if I had a
>>>> more experienced expert to collaborate with.)  I really think we need to
>>>> push hard and get a completed 1.4 out the door.
>>>>
>>>
>>> I fully agree.  What we need is a deadline; 1.4 has languished long
>>> enough, and the fact of the matter is that fixing every bug is simply an
>>> impossible goal.
>>>
>>> I propose Thursday, May 13.  It's a largely selfish date: I'll have a
>>> couple days prior in which I am free to focus on nothing but hacking on
>>> Adium, and since I have company in town that weekend (and every other
>>> weekend in May) I don't want to release on or immediately before the
>>> weekend.
>>>
>>> Let's ship.  The momentum we gain - both for ourselves, seeing a major
>>> release finally moving, and from the outside as folks see how much we've
>>> accomplished - will make 1.4.1 a much easier goal than 1.4 was.
>>>
>>> Thoughts?
>>>
>>> -Evan
>>>
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://adium.im/pipermail/devel_adium.im/attachments/20100423/df9affd4/attachment-0002.html>


More information about the devel mailing list