On Sat, Mar 5, 2011 at 11:09, Shawn Khan <shawn.k...@gmail.com> wrote: > Hello all, > > I agree with all of this but we should start to push FBXMPP a bit more so > that this doesn't take awhile longer to fix. What is the current status of > this? Is there a lot of work left?
Uh, I thought it was pretty self-evident that we think it's important to get done, that we lack the time to get it done, and that it doesn't really matter how much is left because nobody is actively working on it. > > As for MSN and Libpurple, John is there a way to say that we want these MSN > bugs fixed before 2.7.12 comes out? Is there a timeline for that release? > This way Adium can have a time date on a release of first beta. Adium does not control the libpurple release cycle, and he's made it pretty clear that they keep pushing the fixes because (1) nobody cares about MSN, and (2) nobody has fixed it. And it's _very_ clear that, much like Adium does, libpurple will not give a date for a release. Ever. It's just a bad idea. > > Thanks, > Shawn > > On Mar 4, 2011 11:33 PM, "Evan Schoenberg, M.D." <eva...@dreskin.net> wrote: >> >> On Mar 4, 2011, at 5:21 PM, Colin Barrett wrote: >> >>> On Mar 4, 2011, at 2:53 PM, Evan Schoenberg, M.D. wrote: >>> >>>> If we go to beta now, we should plan to release 1.4.2 and then shift >>>> FBXMPP to 1.4.3. >>> >>> 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. >> >> Awesome, Colin. >> >> It sounds like the train is going to hang out at the station for a bit >> anyways; libpurple as-is has regressions, and there's no way I'm reverting >> the merge-to-current and then playing guess-the-pluck. I would, however, >> happily revert and ship FBXMPP only ;) >> >> -Evan > -- Zachary West
