1 | |
---|
2 | [August 15, 2007 - archived for future reference - newbery] |
---|
3 | ___________________________________________________________ |
---|
4 | |
---|
5 | |
---|
6 | ** I NEED HELP ON THIS STUFF!! ** |
---|
7 | |
---|
8 | Stuff to do before 1.0 release |
---|
9 | ------------------------------ |
---|
10 | [In order of decreasing priority] |
---|
11 | |
---|
12 | * DOCUMENTATION!! |
---|
13 | |
---|
14 | * Make conditional GET handling deal properly with force-GETs |
---|
15 | |
---|
16 | * Need a new class of cache rule that just takes a predicate |
---|
17 | as a selector. We then should add one of these at the end |
---|
18 | of the rule set that sets the private flag for all content |
---|
19 | when people are authenticated - Cookie Crumbler normally does |
---|
20 | this but it is overly zealous so the feature has been disabled |
---|
21 | |
---|
22 | * Need some functional tests for page cache manager (there are |
---|
23 | already some in in CacheSetup) |
---|
24 | |
---|
25 | Please keep in mind the rules: |
---|
26 | ------------------------------ |
---|
27 | |
---|
28 | ** You MUST run the unit tests before checking anything in. |
---|
29 | |
---|
30 | ** Unless you are checking in a unit test that demonstrates a bug, |
---|
31 | all unit tests must run before you do a check-in. |
---|
32 | |
---|
33 | ** If you add a new feature, you should add a unit test that |
---|
34 | exercises it. |
---|
35 | |
---|
36 | ** If you fix a bug, you should add a unit test that fails without |
---|
37 | your fix and passes with your fix. |
---|