well, it would need some tweaking indeed, but yes, THANKS to the XML system, we can add a tag without breaking anything! :) so a new tag would be nice, being able to sort by revision number would be nice.. when setting something to fixed, be able to set which revision it was fixed on (now it uses the date of modif, be we can't use that anymore)... when we set something to fixed, we should keep one bug report in it, and delete all other reports...
KaKaRoTo On Mon, 29 May 2006 19:18:00 -0400, Karol Krizka <[EMAIL PROTECTED]> wrote: > On Mon, 2006-29-05 at 15:39 -0400, Youness Alaoui wrote: >> Yes, but the file is not read... you should read the svn_rev file, if it >> doesn't exist, then try the svn command, if it doesn't exist, then use >> the >> $::date >> also, the revision number is not a date, so watch out for that, it may >> crash the bug reporting if the DB assumes it should receive a date, not >> a >> string... >> > It won't crash it, just bug reports will be very old. A simple fix would > be to update the version of the bug report being sent and add the > revision # in a new "<svn_revision>" tag. I'll have the bug report > figure out by version which field it should look into. > >> KaKaRoTo >> >> On Mon, 29 May 2006 15:15:00 -0400, Sander Hoentjen <[EMAIL PROTECTED]> >> wrote: >> >> > On Tue, 2006-05-30 at 00:19 +1000, Arieh Schneier wrote: >> >> Aren't you assuming that the user has svn support installed and is >> >> using the >> >> svn version? What about all the users that use the packages, or the >> >> tarball? >> >> >> > Yes I am asuming that. In packages and the tarball there should be >> this >> > info included. >> >> >> > > > > _______________________________________________ > Amsn-devel mailing list > Amsn-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/amsn-devel -- KaKaRoTo _______________________________________________ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
