Opened at 2015-06-16T20:17:04Z
Closed at 2020-01-17T16:17:02Z
#2457 closed defect (wontfix)
bring 1.8.3 branch into git/trac
Reported by: | warner | Owned by: | daira |
---|---|---|---|
Priority: | normal | Milestone: | soon (release n/a) |
Component: | dev-infrastructure | Version: | 1.8.3 |
Keywords: | git darcs | Cc: | |
Launchpad Bug: |
Description (last modified by daira)
The wiki:Doc page wants to point to the NEWS.rst file in 1.8.3, but 1.8.3 doesn't exist in our git history (I think it was made from a darcs branch that never got imported when we switched to git) (1.9.1 was similar, but *was* imported).
Since all we really care about is having the code *somewhere*, it'd be sufficient to make a git "rel-1.8.3" branch (from the 1.8.2 tag, probably), dump the whole darcs tree into it, add a single commit, and add the allmydata-tahoe-1.8.3 tag. Then update the wiki:Doc page to point at its NEWS file.
Change History (2)
comment:1 Changed at 2015-07-07T19:04:39Z by daira
- Description modified (diff)
- Keywords git darcs added
- Milestone changed from eventually to soon (release n/a)
- Owner set to daira
- Status changed from new to assigned
- Version changed from n/a to 1.8.3
comment:2 Changed at 2020-01-17T16:17:02Z by exarkun
- Resolution set to wontfix
- Status changed from assigned to closed
Note: See
TracTickets for help on using
tickets.
This seems sufficiently old that it's not really relevant anymore. It's true the 1.8.3 docs are still not linkable but I have no idea where to find the darcs repo, nor how to migrate a branch from it anyway.
Feel free to re-open if you have the darcs repo and the expertise to do something useful with it.