#18436 closed New feature (fixed)
Review references to Subversion given github move
| Reported by: | Marc Tamlyn | Owned by: | nobody |
|---|---|---|---|
| Component: | Documentation | Version: | |
| Severity: | Release blocker | Keywords: | svn, subversion, docs |
| Cc: | Triage Stage: | Accepted | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
There are a few process-docs (release cycle, contibuting etc) which are still making the assumption that the root repo for django is the svn source. Would be good to go through this and tidy them up.
Change History (6)
comment:1 by , 13 years ago
| Summary: | Overview references to Subversion given github move → Review references to Subversion given github move |
|---|
comment:2 by , 13 years ago
| Severity: | Normal → Release blocker |
|---|---|
| Triage Stage: | Unreviewed → Accepted |
| Type: | Cleanup/optimization → New feature |
comment:3 by , 13 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
comment:4 by , 13 years ago
| Resolution: | fixed |
|---|---|
| Status: | closed → reopened |
https://github.com/django/django/commit/90fb6a46485d4f3c70d3864ab0a0e2f619449d31
I jumped to the conclusion that the git commit referenced the wrong ticket number in the commit message, actually I can see they are related - I guess the proper thing in hindsight would have been that this should have been marked a dupe of #18307
Sorry for adding to the confusion.
comment:5 by , 13 years ago
| Resolution: | → fixed |
|---|---|
| Status: | reopened → closed |
Note:
See TracTickets
for help on using tickets.
Yes. This item is on the TODO list but I don't think we ever created a ticket. Here's what must be done: