[Adium-devl] 1.4a1 planning

[Eric Richie]

On Fri, Apr 10, 2009 at 2:34 PM, David Smith <catfish.man at gmail.com> wrote:
>        After Evan's commits this morning adding listobject proxies (hooray),
> the issue list is getting pretty small. I'm curious what people think must
> be fixed before we can do an alpha. Personally I think
> http://trac.adiumx.com/ticket/11888 is the most important. Next up (but we
> have to figure out how to reproduce them) are probably
> http://trac.adiumx.com/ticket/11828 and http://trac.adiumx.com/ticket/11813.
> I'm  inclined to *not* block a1 on those. Similarly, the UI part of
> http://trac.adiumx.com/ticket/500 needs doing, but I think we can get away
> with leaving it out for a1. Nothing else on
> http://trac.adiumx.com/query?status=new&status=assigned&status=reopened&milestone=Adium+1.4 seems
> critical.
>        Thoughts? Am I pushing the definition of "alpha" too far by
> suggesting leaving those three out?

I think the first thing we need to do is get 1.3.4 out.  We still have
those facebook ID fixes and such to go out and probably something else
that I'm forgetting before we move to the 1.4 branch and have an alpha
floating around there as well.  But yeah, a lot of awesome work has
been done lately on 1.4 and I think it's probably coming quickly, but
I'd really like to see us wrap up 1.3.x before releasing an alpha for
1.4, especially now that we have nightlies in place for trunk builds
(so if someone wanted to they could already be testing 1.4 without
even building it themselves.)

In terms of the tickets, I guess I'm kind of in the same camp as you
are about not blocking a1 on them.  However I do still think that
1.3.4 should be a blocker on a1.

-Eric