On Mar 4, 2011, at 5:53 PM, Evan Schoenberg, M.D. wrote: > > On Mar 4, 2011, at 12:19 PM, Paul Wilde wrote: > >> There's also http://trac.adium.im/ticket/14965 which is quite a problem and >> therefore getting constant complaints over Twitter and many duplicate >> tickets. That, and 3 other tickets would be closed with an updated >> Libpurple, leaving a few (mainly isolated) tickets and Facebook left for the >> 1.4.2 milestone. >> >> So yeah, I couldn't agree more with getting a beta out assuming Facebook is >> going to take a while, could always just push it to 1.4.3 until it gets >> done. Doesn't seem very logical blocking a release of some annoying issues >> if no one is actively working on Facebook at the moment. > > I'm fine with 1.4.2 with just the libpurple fixes, as FBXMPP is clearly > taking longer than we'd originally imagined.
The downside to pushing FBXMPP to 1.4.3 is that we've been telling users for several weeks now that the facebook fixes would come as part of 1.4.2. Do we currently have a realistic estimate of how much work is left to finish it up? Is it far enough away that we really don't have any option but to push it to 1.4.3? > >> >> Not much harm in adding FBXMPP during the beta period, as well. > > I disagree. The beta period should be for testing of the intended release. > Once we go into beta, the only changes made should be bug fixes. I am > certainly very guilty of sneaking last minute enhancements in, but that's > really not the intention. If we go to beta now, we should plan to release > 1.4.2 and then shift FBXMPP to 1.4.3. Agreed. New features (especially big ones like FBXMPP) don't get added in the middle of a beta. -Eric
