Per Einar Ellefsen wrote:At 06:47 02.07.2002, Stas Bekman wrote:
Per Einar Ellefsen wrote:
At 22:48 01.07.2002, Per Einar Ellefsen wrote:
This is why we ask for your help: take some time to browse the site, and take note of: - errors with browsers (crashes and/or rendering problems) - usability: are you satisfied with the navigation and organization of the content? - your general satisfaction with how the site is.
I think I should add:
We also welcome "OK" reports with indication of the Operating System and Browser.
rationale: These reports might help us isolate potential issues to a specific Browser/platform.
yes, but do we want lots of duplicated emails to wade through? If we do that we need another file which maintains status, and people should be advised to visit it first and skip the report if reported already, no?
Yes, probably. I was thinking to keep track of those mails a little like the deprecated STATUS file we have now.. have a table to indicate what seems to work, and what not.
so should we then have: /site-issues.txt /site-status.txt?
I guess we will want to keep these files around after RC stage is over, so if any questions arise afterwards we will be able to per-use these files.
If we want to keep them, then we should add them to CVS and have them under release/ for now:
/release/ISSUES
/release/STATUS ? (we already have that one)
but we need to make sure that these are updated continuously to the site.. quicker than the 6 hour turnaround.. so I'll do that manually.
-- Per Einar Ellefsen [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
