[REBOL] Rebol Bug-List Re:
Hi, I don't understand, why your mail didn't get through (I received your previous mail normally). > Hi, Ladislav. > > I'm replying through the Rebol list, because my ISP says: > > This Message was undeliverable due to the following reason: > > Your message was not delivered because the return address was refused. > > The return address was '<[EMAIL PROTECTED]>' > > > It seems your email service doesn't like me. :-( > > You wrote (directly to me): > > How about the bug list organization - all bugs in one file, or a file for > every bug? > > One bug = one file. One file to list them, one file to describe them, and > one file to link them all! :-) > > Apart from sounding like a line from Tolkien, it's a reasonable plan I > believe. > > Suggestions > Directories like this: > /Core > /View > /Apache > /Command > > Each of the above having: > /New - This is for new bugs. > /Fixing - Bugs being fixed (hopefully). > /Fixed - For fixed bugs. > > [Your suggestions here.] How about /Patched? > > Andrew Martin > ICQ: 26227169 > http://members.nbci.com/AndrewMartin/ > -><- > >
[REBOL] Rebol Bug-List Re:(3)
[EMAIL PROTECTED] wrote: > pekr wrote: > > Andrew wrote: > > > Each of the above having: > > > /New - This is for new bugs. > > > /Fixing - Bugs being fixed (hopefully). > > > /Fixed - For fixed bugs. > > > > > > > Seem to be fine strategy, as it comply with your > component/plug-in/enhancement/patch system. > > > Btw: any progress here? :-) > > Still working on system. I've realised I need a simpler system to store them > to my site, and to retrieve them from other locations. > What's the problem with storage? /components/component-name.r's header contains 'home or 'file, the fields to store the storage, e.g. www.somesite.com/rebol/components/component-name.r. Or are you talking about anything else? > > > > [Your suggestions here.] > > > you should buy me a beer ;-) > > === > | This voucher permits the bearer:| > | one (1) beer | > | at any virtual bar on the internet. | > | Signed: Andrew Martin. | > === > :-))) Well, thanks, I will enjoy it. Anyone to join me? :-) > > Andrew Martin > ICQ: 26227169 > http://members.nbci.com/AndrewMartin/ > -><-
[REBOL] Rebol Bug-List Re:(2)
pekr wrote: > Andrew wrote: > > Each of the above having: > > /New - This is for new bugs. > > /Fixing - Bugs being fixed (hopefully). > > /Fixed - For fixed bugs. > > > > Seem to be fine strategy, as it comply with your component/plug-in/enhancement/patch system. > Btw: any progress here? :-) Still working on system. I've realised I need a simpler system to store them to my site, and to retrieve them from other locations. > > [Your suggestions here.] > you should buy me a beer ;-) === | This voucher permits the bearer:| | one (1) beer | | at any virtual bar on the internet. | | Signed: Andrew Martin. | === Andrew Martin ICQ: 26227169 http://members.nbci.com/AndrewMartin/ -><-
[REBOL] Rebol Bug-List Re:
[EMAIL PROTECTED] wrote: > > One bug = one file. One file to list them, one file to describe them, and > one file to link them all! :-) > > Apart from sounding like a line from Tolkien, it's a reasonable plan I > believe. > > Suggestions > Directories like this: > /Core > /View > /Apache > /Command > > Each of the above having: > /New - This is for new bugs. > /Fixing - Bugs being fixed (hopefully). > /Fixed - For fixed bugs. > > [Your suggestions here.] > Does the /New /Fixing /Fixed trichotomy imply that a bug report would migrate between directories as its status changes? This would imply that I couldn't, for example, bookmark a bug report and return periodically (or via a REBOL 'bot ;-) to check for changes in status. Would it be simpler to have a "status" datum for each report, and have a variety of list/link files to categorize them in various useful ways (platform, status, who reported, version in which it appeared, version in which it was exterminated...)? -jn-
[REBOL] Rebol Bug-List Re:
[EMAIL PROTECTED] wrote: > Hi, Ladislav. > > I'm replying through the Rebol list, because my ISP says: > > This Message was undeliverable due to the following reason: > > Your message was not delivered because the return address was refused. > > The return address was '<[EMAIL PROTECTED]>' > > > It seems your email service doesn't like me. :-( > > You wrote (directly to me): > > How about the bug list organization - all bugs in one file, or a file for > every bug? > > One bug = one file. One file to list them, one file to describe them, and > one file to link them all! :-) > > Apart from sounding like a line from Tolkien, it's a reasonable plan I > believe. > > Suggestions > Directories like this: > /Core > /View > /Apache > /Command > > Each of the above having: > /New - This is for new bugs. > /Fixing - Bugs being fixed (hopefully). > /Fixed - For fixed bugs. > Seem to be fine strategy, as it comply with your component/plug-in/enhancement/patch system. Btw: any progress here? :-) -pekr- > [Your suggestions here.] > you should buy me a beer ;-) > > Andrew Martin > ICQ: 26227169 > http://members.nbci.com/AndrewMartin/ > -><-
