[SciPy-Dev] issues trac migration review
Wed Apr 24 13:26:09 CDT 2013
On Wed, Apr 24, 2013 at 2:12 PM, Ralf Gommers <firstname.lastname@example.org> wrote:
> On Wed, Apr 24, 2013 at 8:00 PM, Skipper Seabold <email@example.com>
>> Round 2. I got github to temporarily up the rate limit for this, so
>> it's great if we can finish in the next 2 days. Since I'm using oauth
>> now, I moved the issues to
>> Some issues that were raised upthread about traclinks. These should be
>> fixed now. Let me know if you see any that aren't. I assume the hash
>> will be a correct link in the scipy repo, but I can change it to be an
>> absolute URL to be sure if needed.
> Hash should work.
> If it's easy to do, can we use gh-1234 instead of #1234 for issue numbering
> on Github? Otherwise things are more confusing, since comments in the code
> using # refer to Trac now. We should keep that habit also for future
Should be easy enough to do in the migration. Can't speak for changing
>> r5205 in second to last comment
>> ticket: in issue body here
>> changset: in first comment
>> #1394 in last comment here
>> A decent amount of the SVN revision numbers are not in git.
> Any idea how that happened?
No idea. Some look like commits for things that were removed from
github - maybe deprecated modules. Some were commits that may have
been later backed out. Some svnmerge commits. Some were commits
without a commit message. I filter on the commit dates, so I should
even be picking up the ambiguous commit messages from the early days
though. I can post some examples if it's worth it.
>> If you still see a rXXXX, it was either not in git or had some formatting
>> issue in the commit message that I didn't properly escape for when
>> calling git log --grep. Let me know if you think it's the latter.
>> I had some problems with PyGithub that should now be fixed. To make
>> sure nothing comes up during the real deal, I'll do one more dry-run
>> this afternoon to be sure there are no hiccups, then hopefully we can
>> do the migration tonight or sometime tomorrow, though I'll need some
>> help on the on the scipy repo end.
> I can turn on Issues now, and give you push access (you need those I
> guess?). Anything else?
IIUC, I won't need push access through the web ui, I'll need someone
to get me a token for the oauth app running the code in the docstring
It's not clear to me how to do this without giving you the
client_secret, so we can figure this out off list.
>> For posterity, if anyone is also wanted to use this code, I had to
>> make some changes to the numpy migration code and patch PyGithub for
>> correctly doing oauth authentication.
>> SciPy-Dev mailing list
> SciPy-Dev mailing list
More information about the SciPy-Dev