tahoewapi: Verify against the CAJA verifier. #656

Open
opened 2009-03-05 17:01:10 +00:00 by nejucomo · 1 comment

MarkM contributed a patch to make tahoewapi.js pass the CAJA verifier, but Nathan has not gone through this process.

This ticket will be resolved by:

  1. Running the verifier on both tahoewapi.js and the demo (in "./trunk/poc").

  2. Fix issues reported by the verifier.

  3. Test the result.

  4. For each bug found in testing, after altering the code, jump to the initial step.

  5. After verified, tested, and fixed, make a release.

All future releases will follow this process.

MarkM contributed a patch to make tahoewapi.js pass the CAJA verifier, but Nathan has not gone through this process. This ticket will be resolved by: 1. Running the verifier on both tahoewapi.js and the demo (in "./trunk/poc"). 2. Fix issues reported by the verifier. 3. Test the result. 4. For each bug found in testing, after altering the code, jump to the initial step. 5. After verified, tested, and fixed, make a release. All future releases will follow this process.
nejucomo added the
contrib
major
task
unknown
labels 2009-03-05 17:01:10 +00:00
nejucomo added this to the undecided milestone 2009-03-05 17:01:10 +00:00
nejucomo self-assigned this 2009-03-05 17:01:10 +00:00
Author

bumping this issue so that I remember it.

This code now has a new home: https://bitbucket.org/nejucomo/tahoewapi.js

bumping this issue so that I remember it. This code now has a new home: <https://bitbucket.org/nejucomo/tahoewapi.js>
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Reference: tahoe-lafs/trac-2024-07-25#656
No description provided.