[Numpy-discussion] Issue tracking
Tue Oct 23 11:23:29 CDT 2012
On Tue, Oct 23, 2012 at 5:13 PM, Travis Oliphant <email@example.com>wrote:
> On Oct 23, 2012, at 9:58 AM, David Cournapeau wrote:
> > On Tue, Oct 23, 2012 at 5:05 AM, Thouis (Ray) Jones <firstname.lastname@example.org>
> >> On Fri, Oct 19, 2012 at 9:34 PM, Thouis (Ray) Jones <email@example.com>
> >>> On Fri, Oct 19, 2012 at 4:46 PM, Thouis (Ray) Jones <firstname.lastname@example.org>
> >>>> On Fri, Oct 19, 2012 at 11:20 AM, Thouis (Ray) Jones <
> email@example.com> wrote:
> >>>>> I started the import with the oldest 75 and newest 125 Trac issues,
> >>>>> and will wait a few hours to do the rest to allow feedback, just in
> >>>>> case something is broken that I haven't noticed.
> >>>>> I did make one change to better emulate Trac behavior. Some Trac
> >>>>> usernames are also email addresses, which Trac anonymizes in its
> >>>>> display. I decided it was safer to do the same.
> >>>> The import is running again, though I've been having some failures in
> >>>> a few comments and general hangs (these might be network related).
> >>>> I'm keeping track of which issues might have had difficulties.
> >>>> @endolith noticed that I didn't correctly relink #XXX trac id numbers
> >>>> to github id numbers (both trac and github create links
> >>>> automatically), so that will have to be handled by a postprocessing
> >>>> script (which it probably would have, anyway, since the github # isn't
> >>>> known before import).
> >>> Import has finished.
> >>> The following trac #s had issues in creating the comments (I think due
> >>> to network problems): 182, 297, 619, 621, 902, 904, 909 913, 914, 915,
> >>> 1044, 1526. I'll review them and see if I can pull in anything
> >>> missing
> >>> I'll also work on a script for updating the trac crossrefs to github
> >>> In the "no good deed goes unpunished" category, I accidentally logged
> >>> in as myself (rather than numpy-gitbot) and pushed about 500 issues,
> >>> so now I receive updates whenever one of them gets changed. At least
> >>> most of them were closed, already...
> >> I just updated the cross-issue-references to use github rather than
> >> Trac id numbers. Stupidly, I may have accidentally removed comments
> >> that were added in the last few days to issues moved from trac to
> >> github. Hopefully not, or at least not many.
> >> It's probably a good idea to turn off Trac, soon, to keep too many new
> >> bugs from needing to be ported, and old bugs being commented on. The
> >> latter is more of a pain to deal with.
> > I will look into making the NumPy trac read-only. It should not be too
> > complicated to extend Pauli's code to redirect the tickets part to
> > github issues.
> > Have we decided what to do with the wiki content ?
> I believe there is a wiki dump command in trac wiki. We should put that
> content linked off the numpy pages at github.
Please don't do that. Most of the content is either links to what was
already moved into the numpy git repo, or very outdated stuff.
I see at least two better options:
- just leave the wiki pages as is, make them read only and add a clear
warning "outdated" at the top.
- move the rest of the useful content into the git repo, remove the rest
> Thanks for helping with this.
> > David
> > _______________________________________________
> > NumPy-Discussion mailing list
> > NumPy-Discussion@scipy.org
> > http://mail.scipy.org/mailman/listinfo/numpy-discussion
> NumPy-Discussion mailing list
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the NumPy-Discussion