Hi Jerome,
It looks like you've been away for too long, and I know it's impossible to
catch up with everything (you probably did a 'select all emails'->'mark as
read' :P ), so let me brief you in really fast on what we currently have :
I don't know if you were still here but we dropped CVS and we're now using
SVN, Subversion is so much better, there is no more delay between
anonymous and developer repositories and it's nice to say to a user "this
was fixed in revision XXXX" (without talking about all the functionality
SVN gives us, like 'svn blame', take a look at it, I just love it! :) )
We did have a TODO, but we used your method for 0.95, which means an email
that we always update with added/removed items and the subject being "0.96
TODO".. I think if we want to add something to a 'todo', we should simply
create a new task item for it...
About the release, the rc1 and the development : good news, we're finally
using branches!!! this means, no more feature freeze, we have a 0_96
branch where we put only 0.96 related commits, in the trunk/ (no branch)
we can commit whatever we want, it's already "0.97b" in there... when we
commit a bug fix, we directly patch the 0.96 branch copy of it and commit
the same bugfix to the 0.96 branch...
This means, if you decide to take care of that, you can still do it in the
trunk/ and not worry about the 0.96 release at all..
this also means if you commit a bugfix to the trunk/, you should worry
about merging it to the branch too if it applies.. but we have some people
(vivia/billiob/harry I think) who periodically check every commit log and
see if it should go to the branch too or not.
I hope it answers your questions, if any more questions arise, ask me.
KaKaRoTo
On Sun, 25 Jun 2006 02:40:11 -0400, Jérôme Gagnon-Voyer
<[EMAIL PROTECTED]> wrote:
> Yeah the thing is I don't want that to be added after RC1 and before
> the release. Backward compatibility seems to be an issue and this
> kind of patch probably needs a lot of testing, that's not the time to
> add bugs in that kind of important feature (keeping cached pictures).
>
> I think it's better to wait for the feature and having a small issue
> than adding a big chance in a release candidate and risking to add a
> big bug (or risking to delay the release too much)
>
> Can we add it to the TODO for next release? Is there still someone
> taking care of that?
>
> Do we keep a list of known issues somewhere? We can add that in that
> list..."if you have too many cached pictures, amsn can be very slow,
> will be fixed in next release".
> Le 25 juin 2006 à 01:37, Youness Alaoui a écrit :
>
>> Yes, I agree, there is a patch that was sent that allows amsn to
>> store the
>> cached DP in a per user subdirectory, it's still pending for commit
>> because we're not sure we want to put it in 0.96, and we're not
>> sure if
>> the patch is complete, if it doesn't introduce a bug, amsn should
>> also be
>> backward compatible, so we should maybe do a
>> if { [llength [glob *.dat]] > 0 } {
>> ShowAPleaseWaitMessage
>> moveDPFilesToSubdirs
>> }
>>
>> something like that in the start of amsn... anyways, noone wanted
>> to take
>> care of that, so it's still pending.. if you want to take care of
>> it, I
>> could try to find the patch, you're up to it ?
>
--
KaKaRoTo
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel
