| Commit | Date | |
|---|---|---|
| 2007-03-23 07:52:19 | Tree | |
| 2007-03-22 19:31:28 | Tree | |
|
[r5114]
by
cboos
The new repository caching scheme is exclusive to the old one. If by mistake an old code gets to be used and therefore an old style sync, the `youngest_rev` metadata will become inaccurate and the processes will be stuck showing the repository at that `youngest_rev` revision, believing that a sync is in progress... In order to make sure this can't happen, a version bump is needed. |
2007-03-22 19:27:24 | Tree |
| 2007-03-22 12:58:11 | Tree | |
| 2007-03-22 09:46:26 | Tree | |
|
[r5111]
by
cboos
Blame: some changes discussed in #4985: |
2007-03-22 08:06:41 | Tree |
|
[r5110]
by
mgood
reports should not refer to milestones as "Release" since this is not true for all users (fixes #4963) |
2007-03-21 21:13:21 | Tree |
| 2007-03-20 22:01:17 | Tree | |
| 2007-03-20 20:49:16 | Tree | |
|
[r5107]
by
ecarter
WorkFlow: Use an OrderedExtensionsOption for configuring the active ticket |
2007-03-20 20:48:46 | Tree |