On Tue, May 27, 2008 at 03:24:44PM +0100, Tom Hennigan wrote: > On 27 May 2008, at 08:48, Boris Faure (aka billiob) wrote: > > On 5/27/08, Youness Alaoui <[EMAIL PROTECTED]> wrote: > >> Hi, > >> > >> I would like to suggest something : > >> 1 - merge all the bug fixes from the trunk to the 0.97 > >> branch and release 0.97.1 bugfix release > > Good idea, > > I think this WE, i'll have time to look into that. > I'm in exams at the moment, so don't have time to (learn how +) do the > merges.. Sorry! > np, same with phil, I'm just suggesting, not saying we should start doing it right now (unless someone has time right now).
> >> 2 - once I fix (or anyone else who volunteers) 2 remaining > >> bugs on MSNP15, do a release of a 0.98 alpha version for > >> people to play with > > why not but we need to release both at the same time. > Excellent, what are the bugs? > First bug : a contact connects, changes his nickname, disconnects, you logout, login, in your CL, you'll see his old nickname.. seems we need to update the addressbook with the contact's nickname whenever they change it or something... Second bug (most important) : try adding '[EMAIL PROTECTED]' to your AL list and you'll get it... if our AL or BL list contains someone which passport account doesn't exist anymore, then the server refuses him, resulting in a 206 response to our ADL. problem is that 206 is now a payload command which gives us the email refused. same for error 511, 240, 241, etc.. and any other error code that we might think of... I need to have a handler for our ADL, so we can get *any* response (error code or whatever) and the core will know it's a response to the ADL and will not pop a "invalid username" out of thin air. Problem is that the current code assumes that any command with a 'handler' does not contain any payload... (which btw prevents us from reading the next protocol line received) > >> 3 - announce and officialize what we've been doing for aMSN2 > >> so far... > >> > >> I think the current work being done on aMSN2 is evolving > >> nicely so far, so I think we can soon announce what it is, > >> how it will work and move the code into the public SVN so > >> everyone can start working on it. > > maybe i should do more "svn up". > Good idea about publicizing it.. It would be nice to set up Trac > (http://trac.edgewall.org/ > ) for aMSN2 as a bug reporting system. It seems to work well for other > projects, and could benifit us... > The problem is not the tools, it's how you use it.. we already have 'task manager' and 'bug trackers', etc.. tools from SF, we just don't use them, so having trac set up will be useless too if we don't use it... We'll see how it goes, for now, I don't think we're in the "bug reporting" phase of the project yet... KaKaRoTo ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
