Re: [Scons-dev] SCons, Mercurial, BitBucket, Git, and GitHub

Dirk, Indeed I see value in the following: 1) getting to github 2) integrated git+issues+wiki+ all the 3rd part integrations which work with github, but not with bitbucket 3) Migrating all the issues (frankly I'm not sure tigris will be around as long as github). There is useful information

Re: [Scons-dev] SCons, Mercurial, BitBucket, Git, and GitHub

Bill, you're right about the issue ID...I stand corrected. I may have been dreaming, but I remember a time when these weren't available in the list of all issues. All the better then...;) Referring to Russel's latest post I'd like to state that I'm not against moving to Github as issue

Re: [Scons-dev] SCons, Mercurial, BitBucket, Git, and GitHub

> On Aug 30, 2017, at 05:31, Russel Winder wrote: > > > Given we are moving from Tigris to GitHub, I can't get worked up about > issue creation dates. To be honest I can't get that worked up about > transferring the issues, I'd just start from scratch on GitHub issues >

Re: [Scons-dev] SCons, Mercurial, BitBucket, Git, and GitHub

On Mon, 2017-08-28 at 23:02 +0200, Dirk Bächle wrote: > […] > > not so quick young grasshopper. ;)  (Sorry, I couldn't resist) Resistance is futile. (7of9) Do or do not, there is no try. (Yoda) > I already have a working and complete scraper for the Tigris > bugtracker.  > It's written in

Re: [Scons-dev] SCons, Mercurial, BitBucket, Git, and GitHub

Dirk, Here's an example on buildbot: https://github.com/buildbot/buildbot/issues/3564 I see the issue number in the URL.. Or am I missing something when you say you can't see the ID? -Bill On Tue, Aug 29, 2017 at 1:46 PM, Dirk Bächle wrote: > Bill, > > > On 29.08.2017 22:14,

Re: [Scons-dev] SCons, Mercurial, BitBucket, Git, and GitHub

Bill, On 29.08.2017 22:14, Bill Deegan wrote: Dirk, Does the script migrate attachments? yes, it also downloads all attachments. But, as mentioned in my other post, you can't upload them directly to Github. :( And we might create the issues one-by-one in their natural order as you

Re: [Scons-dev] SCons, Mercurial, BitBucket, Git, and GitHub

Hi Tim, On 29.08.2017 17:02, Tim Jenness wrote: If you can add labels during the import then you could conceivably add age-based labels such as “ancient”, “1year”, “2years” or whatever. Then you would be able to get some feel for which ones are the old ones that have been lingering. That

Re: [Scons-dev] SCons, Mercurial, BitBucket, Git, and GitHub

Dirk, Does the script migrate attachments? -Bill On Tue, Aug 29, 2017 at 1:11 PM, Bill Deegan wrote: > People may not know what Tigris is in the near future (or even now)... ;) > > > On Tue, Aug 29, 2017 at 1:00 PM, Tim Jenness wrote: > >> Good

Re: [Scons-dev] SCons, Mercurial, BitBucket, Git, and GitHub

People may not know what Tigris is in the near future (or even now)... ;) On Tue, Aug 29, 2017 at 1:00 PM, Tim Jenness wrote: > Good idea. Or “Tigris” even. > > On Aug 29, 2017, at 12:34 , Bill Deegan wrote: > > and also "Migrated" tag? > > On

Re: [Scons-dev] SCons, Mercurial, BitBucket, Git, and GitHub

and also "Migrated" tag? On Tue, Aug 29, 2017 at 8:02 AM, Tim Jenness wrote: > If you can add labels during the import then you could conceivably add > age-based labels such as “ancient”, “1year”, “2years” or whatever. Then you > would be able to get some feel for which ones

Re: [Scons-dev] SCons, Mercurial, BitBucket, Git, and GitHub

If you can add labels during the import then you could conceivably add age-based labels such as “ancient”, “1year”, “2years” or whatever. Then you would be able to get some feel for which ones are the old ones that have been lingering. That combined with ordering by issue number should be

Re: [Scons-dev] SCons, Mercurial, BitBucket, Git, and GitHub

Looks like you can't specify the issue #, but it's a safe bet their sequential, so if we create each and every bug which is on tigris... https://developer.github.com/v3/issues/#create-an-issue On Tue, Aug 29, 2017 at 12:00 AM, Dirk Baechle wrote: > Bill, > > I haven't checked

Re: [Scons-dev] SCons, Mercurial, BitBucket, Git, and GitHub

Bill, I haven't checked this. But I'd expect to have this 1:1 mapping for Tigris->NewTracker anyway. If Github wouldn't support this it'd be a nogo for me. I'll try to have another look at the API today. If someone here knows more, chime in please. Regards, Dirk -- Sent from my Android

Re: [Scons-dev] SCons, Mercurial, BitBucket, Git, and GitHub

Dirk, Re bug scraper If we migrate all bugs to GitHub, isn't there an issue # associated with github issues? If so, can we migrate the bugs such that the issue #'s stay the same? -Bill On Mon, Aug 28, 2017 at 2:02 PM, Dirk Bächle wrote: > Hi Russel, > > > On 28.08.2017 09:43,

Re: [Scons-dev] SCons, Mercurial, BitBucket, Git, and GitHub

Hi Russel, On 28.08.2017 09:43, Russel Winder wrote: [...] The question then has to be how to bring the issues from Tigris to GitHub. GitHub issues has an API. If Tigris Issues also has an API then it is a question of writing a program, I guess in Python3, since that is likely easier than

[Scons-dev] SCons, Mercurial, BitBucket, Git, and GitHub

Whist I can't commit to working on anything in the next few weeks, I wanted to chip this in to the discussions. With bookmarks, remote head tracking and hgview working (at least on Debian Sid, not Fedora Rawhide), I have a renewed real like of Mercurial. It is better than Git for me. However