On Apr 16, 2011, at 8:15 AM, Robert Vehse wrote: > > Am 05.03.2011 um 19:42 schrieb Robert Vehse: > >> <snip> >> >> I'm not sure about Facebook XMPP migration because I'm unclear as to where >> we're stuck. But what I've learnt from updates that involved migrations in >> the past is that they to require a good deal of testing so I agree with >> others who said we should do that before putting a beta with it out >> (provided, we'll wait on Facebook XMPP migration for 1.4.2). >> >> >> Am 05.03.2011 um 00:21 schrieb Colin Barrett: >> >>> There's a 50% chance I'll get to work on Adium this weekend. If on Monday I >>> haven't finished it, the train can leave w/o it. >>> >>> -Colin >> >> >> Let's hope Colin gets there. Otherwise, I think we should release a beta of >> 1.4.2 with the fixes we already have and libpurple 2.7.11. > > I think we should consider releasing 1.4.2 now. It has a large selection of > important fixes - 37 fixes in total - by now: > - MSN UPnP crash: http://trac.adium.im/ticket/14650 > - MSN connection issue: http://trac.adium.im/ticket/13654 > - MSN issue adding contacts: http://trac.adium.im/ticket/14965 > - ICQ losing connection without showing: http://trac.adium.im/ticket/14229 > - Hang when opening chat window to a contact with a malformed log: > http://trac.adium.im/ticket/14627 > - The focus indication people complained about a lot: > http://trac.adium.im/ticket/14420 > - The broken Events table: http://trac.adium.im/ticket/14629. > > Facebook XMPP migration isn't finished and even then it still needs to be > merged to the default branch for more testing so I believe we should really > move that item to 1.4.3. > > I'd like to suggest cutting a 1.4.2 beta this weekend. The only thing that > needs to be done until then is this: > http://trac.adium.im/ticket/15000#comment:7 which doesn't seem too > complicated.
I agree, at this point there's too much that's ready to go to justify holding up a release for the facebook stuff. Facebook definitely needs to be a priority, but I think it needs to be pushed to 1.4.3. Here's what I'd like to propose: Most of us have a long weekend coming up due to the Easter holiday next weekend. Is there anything else that we could squeeze in for 1.4.2 if we waited to release a beta next week? If the answer is no, let's go ahead build a beta tomorrow night or Monday. (Thijs said he's working on getting ticket 15000 wrapped up this weekend if possible so we can roll after he gives us the ok.) However, if the long weekend WILL be beneficial to getting a few more things finished up, we can hold the beta until then. Once we've got the beta released, I'd like to shoot for a release of 1.4.2 by the 1st of May. That could easily go a week in either direction if circumstances dictate it, but let's target May 1st. After we have 1.4.2 released, the focus really needs to turn to finishing up the Facebook XMPP stuff with the intention of a quick release shortly thereafter. I'd appreciate if anyone who was able to lend a hand could please do so. Unless I'm forgetting something, resolving that should be the last major issue holding us back from directing all of our attention to 1.5 and onward. Does this sound reasonable to everyone else? Questions/comments/suggestions? -Eric
