| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
| |
administrative interfaces, etc.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Add a comment about how to generate the roadmap table from the
"schedule" input file.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Update roadmap with a stab at a schedule of releases leading up to 2.0.0.
|
| |
|
| |
|
|
|
|
| |
test case is good.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
submissions.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
on branches. Add a few clarifying comments.
|
| |
|
|
|
|
|
| |
Add a Branching page at tigris.org to describe the branch structure
and management.
|
|
|
|
| |
query page, and compress them into a sort-of table.
|