Ticket #57 (Fixed)Thu Oct 19 19:35:51 UTC 2006
Batch One sources need keyword scan and fix
| Reported by: | Severity: | Major | |
| Part: | Repository: CVS | Release: | Batch One code release |
| Milestone: | Batch One code release completed | Status | Fixed |
Details by :
Need to scan all sources in Batch One for any questionable keywords. These will require fixing in the repository files themselves.
Changelog:
Modified by Steve Revill (20) Thu, January 18 2007 - 00:12:22 GMT
We have a tool which will look for the keywords that we’re most interested in (e.g. swearing, GPL, etc). This has been tested quite extensively on the whole repository, not just the subset for Batch One.
Actually fixing problems will remain a manual task and as always, it’s going to be the tokenised BASIC programs which cause the most grief, especially if we want to keep revisions older than the head.
Modified by Steve Revill (20) Tue, May 15 2007 - 16:17:26 GMT
- Severity changed from Blocker to Major
We now have two lots of scanning tools available. These appear to do pretty much what we need so it’s just a case of scanning some sources.
I’m down-grading the severity because we’re going to release the easiest stuff earliest so the impact of searching for keywords and correcting stuff shouldn’t be too severe to start with.
Modified by Andrew Hodgkinson (6) Sat, May 19 2007 - 07:31:10 GMT
- Status changed from Open to Fixed
Scanning tools work; used in anger for Batch One release.
