[tahoe-lafs-trac-stream] [Tahoe-LAFS] #2457: bring 1.8.3 branch into git/trac
Tahoe-LAFS
trac at tahoe-lafs.org
Tue Jul 7 19:04:41 UTC 2015
#2457: bring 1.8.3 branch into git/trac
------------------------------------+--------------------------------
Reporter: warner | Owner: daira
Type: defect | Status: assigned
Priority: normal | Milestone: soon (release n/a)
Component: dev-infrastructure | Version: 1.8.3
Resolution: | Keywords: git darcs
Launchpad Bug: |
------------------------------------+--------------------------------
Changes (by daira):
* status: new => assigned
* owner: => daira
* version: n/a => 1.8.3
* milestone: eventually => soon (release n/a)
* keywords: => git darcs
Old description:
> 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 it's NEWS file.
New description:
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.
--
--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2457#comment:1>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage
More information about the tahoe-lafs-trac-stream
mailing list