Hi all, I've tried to get a nice bug import mechanism going to go from the existing Trac to BitBucket nicely. But, the API for BitBucket's bug creation mechanism doesn't (currently) let you set the resolution of a bug, or the milestone info. With the new development of Reason, Cameron and I talked about how to track future changes, and the idea of using the bug tracker came up. I'm a little bit skittish about using the bitbucket one unless we have a full import. But I'm willing to get over that. So far the bug tracker has really only ever been a mechanism to keep track of things, never for actual bug reports. (Maybe this will change?) I see three options for moving to bitbucket: 1) Import what I can, for history's sake, and then close down Trac. 2) Wait for the API to be improved, and for now, don't use the bugtracker anywhere. 3) Give up, just start over on BitBucket, and leave Trac up but hidden. Can I get a real quick vote, 1/2/3? I know that the bug tracker is really never used, but I think transitioning to the BB one might change that, so I want to make sure we do it right. Importing the Wiki is a lot easier, because we have very little content in the wiki that needs to be retained. And if we end up moving the bugs out of Trac, that whole infrastructure can be shuttered. -Matt
1. -- Stephen Skory s@skory.us http://stephenskory.com/ 510.621.3687 (google voice)
3 then 1. I don't know what exists on the Trac site, but unless there is an outcry to not break with history, there's no reason for you to bust your butt trying to import a bunch of old stuff. Maybe just import the relevant/important stuff. On 04/05/2011 06:00 PM, Matthew Turk wrote:
Hi all,
I've tried to get a nice bug import mechanism going to go from the existing Trac to BitBucket nicely. But, the API for BitBucket's bug creation mechanism doesn't (currently) let you set the resolution of a bug, or the milestone info.
With the new development of Reason, Cameron and I talked about how to track future changes, and the idea of using the bug tracker came up. I'm a little bit skittish about using the bitbucket one unless we have a full import. But I'm willing to get over that. So far the bug tracker has really only ever been a mechanism to keep track of things, never for actual bug reports. (Maybe this will change?) I see three options for moving to bitbucket:
1) Import what I can, for history's sake, and then close down Trac. 2) Wait for the API to be improved, and for now, don't use the bugtracker anywhere. 3) Give up, just start over on BitBucket, and leave Trac up but hidden.
Can I get a real quick vote, 1/2/3? I know that the bug tracker is really never used, but I think transitioning to the BB one might change that, so I want to make sure we do it right.
Importing the Wiki is a lot easier, because we have very little content in the wiki that needs to be retained. And if we end up moving the bugs out of Trac, that whole infrastructure can be shuttered.
-Matt _______________________________________________ Yt-dev mailing list Yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
-- Cameron Hummels PhD Candidate, Astronomy Department of Columbia University Public Outreach Director, Astronomy Department of Columbia University NASA IYA New York State Student Ambassador http://outreach.astro.columbia.edu PGP: 0x06F886E3
i'm with cameron, don't use too much time. 3 then 1. On Tue, Apr 5, 2011 at 6:54 PM, Cameron Hummels <chummels@astro.columbia.edu
wrote:
3 then 1. I don't know what exists on the Trac site, but unless there is an outcry to not break with history, there's no reason for you to bust your butt trying to import a bunch of old stuff. Maybe just import the relevant/important stuff.
On 04/05/2011 06:00 PM, Matthew Turk wrote:
Hi all,
I've tried to get a nice bug import mechanism going to go from the existing Trac to BitBucket nicely. But, the API for BitBucket's bug creation mechanism doesn't (currently) let you set the resolution of a bug, or the milestone info.
With the new development of Reason, Cameron and I talked about how to track future changes, and the idea of using the bug tracker came up. I'm a little bit skittish about using the bitbucket one unless we have a full import. But I'm willing to get over that. So far the bug tracker has really only ever been a mechanism to keep track of things, never for actual bug reports. (Maybe this will change?) I see three options for moving to bitbucket:
1) Import what I can, for history's sake, and then close down Trac. 2) Wait for the API to be improved, and for now, don't use the bugtracker anywhere. 3) Give up, just start over on BitBucket, and leave Trac up but hidden.
Can I get a real quick vote, 1/2/3? I know that the bug tracker is really never used, but I think transitioning to the BB one might change that, so I want to make sure we do it right.
Importing the Wiki is a lot easier, because we have very little content in the wiki that needs to be retained. And if we end up moving the bugs out of Trac, that whole infrastructure can be shuttered.
-Matt _______________________________________________ Yt-dev mailing list Yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
-- Cameron Hummels PhD Candidate, Astronomy Department of Columbia University Public Outreach Director, Astronomy Department of Columbia University NASA IYA New York State Student Ambassador http://outreach.astro.columbia.edu PGP: 0x06F886E3
_______________________________________________ Yt-dev mailing list Yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
I'm with Cam'ron and Skillz Dat Killz. On Tue, Apr 5, 2011 at 7:37 PM, Sam Skillman <samskillman@gmail.com> wrote:
i'm with cameron, don't use too much time. 3 then 1.
On Tue, Apr 5, 2011 at 6:54 PM, Cameron Hummels < chummels@astro.columbia.edu> wrote:
3 then 1. I don't know what exists on the Trac site, but unless there is an outcry to not break with history, there's no reason for you to bust your butt trying to import a bunch of old stuff. Maybe just import the relevant/important stuff.
On 04/05/2011 06:00 PM, Matthew Turk wrote:
Hi all,
I've tried to get a nice bug import mechanism going to go from the existing Trac to BitBucket nicely. But, the API for BitBucket's bug creation mechanism doesn't (currently) let you set the resolution of a bug, or the milestone info.
With the new development of Reason, Cameron and I talked about how to track future changes, and the idea of using the bug tracker came up. I'm a little bit skittish about using the bitbucket one unless we have a full import. But I'm willing to get over that. So far the bug tracker has really only ever been a mechanism to keep track of things, never for actual bug reports. (Maybe this will change?) I see three options for moving to bitbucket:
1) Import what I can, for history's sake, and then close down Trac. 2) Wait for the API to be improved, and for now, don't use the bugtracker anywhere. 3) Give up, just start over on BitBucket, and leave Trac up but hidden.
Can I get a real quick vote, 1/2/3? I know that the bug tracker is really never used, but I think transitioning to the BB one might change that, so I want to make sure we do it right.
Importing the Wiki is a lot easier, because we have very little content in the wiki that needs to be retained. And if we end up moving the bugs out of Trac, that whole infrastructure can be shuttered.
-Matt _______________________________________________ Yt-dev mailing list Yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
-- Cameron Hummels PhD Candidate, Astronomy Department of Columbia University Public Outreach Director, Astronomy Department of Columbia University NASA IYA New York State Student Ambassador http://outreach.astro.columbia.edu PGP: 0x06F886E3
_______________________________________________ Yt-dev mailing list Yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
_______________________________________________ Yt-dev mailing list Yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
3 On Tue, Apr 5, 2011 at 4:37 PM, Sam Skillman <samskillman@gmail.com> wrote:
i'm with cameron, don't use too much time. 3 then 1.
On Tue, Apr 5, 2011 at 6:54 PM, Cameron Hummels <chummels@astro.columbia.edu> wrote:
3 then 1. I don't know what exists on the Trac site, but unless there is an outcry to not break with history, there's no reason for you to bust your butt trying to import a bunch of old stuff. Maybe just import the relevant/important stuff.
On 04/05/2011 06:00 PM, Matthew Turk wrote:
Hi all,
I've tried to get a nice bug import mechanism going to go from the existing Trac to BitBucket nicely. But, the API for BitBucket's bug creation mechanism doesn't (currently) let you set the resolution of a bug, or the milestone info.
With the new development of Reason, Cameron and I talked about how to track future changes, and the idea of using the bug tracker came up. I'm a little bit skittish about using the bitbucket one unless we have a full import. But I'm willing to get over that. So far the bug tracker has really only ever been a mechanism to keep track of things, never for actual bug reports. (Maybe this will change?) I see three options for moving to bitbucket:
1) Import what I can, for history's sake, and then close down Trac. 2) Wait for the API to be improved, and for now, don't use the bugtracker anywhere. 3) Give up, just start over on BitBucket, and leave Trac up but hidden.
Can I get a real quick vote, 1/2/3? I know that the bug tracker is really never used, but I think transitioning to the BB one might change that, so I want to make sure we do it right.
Importing the Wiki is a lot easier, because we have very little content in the wiki that needs to be retained. And if we end up moving the bugs out of Trac, that whole infrastructure can be shuttered.
-Matt _______________________________________________ Yt-dev mailing list Yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
-- Cameron Hummels PhD Candidate, Astronomy Department of Columbia University Public Outreach Director, Astronomy Department of Columbia University NASA IYA New York State Student Ambassador http://outreach.astro.columbia.edu PGP: 0x06F886E3
_______________________________________________ Yt-dev mailing list Yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
_______________________________________________ Yt-dev mailing list Yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
3 On Apr 5, 2011 8:00pm, js oishi <jsoishi@gmail.com> wrote:
3
On Tue, Apr 5, 2011 at 4:37 PM, Sam Skillman samskillman@gmail.com> wrote:
i'm with cameron, don't use too much time. 3 then 1.
On Tue, Apr 5, 2011 at 6:54 PM, Cameron Hummels
chummels@astro.columbia.edu> wrote:
3 then 1. I don't know what exists on the Trac site, but unless there
is an outcry to not break with history, there's no reason for you to
bust your butt trying to import a bunch of old stuff. Maybe just import
the relevant/important stuff.
On 04/05/2011 06:00 PM, Matthew Turk wrote:
Hi all,
I've tried to get a nice bug import mechanism going to go from the
existing Trac to BitBucket nicely. But, the API for BitBucket's bug
creation mechanism doesn't (currently) let you set the resolution of a
bug, or the milestone info.
With the new development of Reason, Cameron and I talked about how to
track future changes, and the idea of using the bug tracker came up.
I'ma little bit skittish about using the bitbucket one unless we have
a full import. But I'm willing to get over that. So far the bug
tracker has really only ever been a mechanism to keep track of things,
never for actual bug reports. (Maybe this will change?) I see three
options for moving to bitbucket:
1) Import what I can, for history's sake, and then close down Trac.
2) Wait for the API to be improved, and for now, don't use the
bugtracker anywhere.
3) Give up, just start over on BitBucket, and leave Trac up but hidden.
Can I get a real quick vote, 1/2/3? I know that the bug tracker is
really never used, but I think transitioning to the BB one might
change that, so I want to make sure we do it right.
Importing the Wiki is a lot easier, because we have very little
content in the wiki that needs to be retained. And if we end up
moving the bugs out of Trac, that whole infrastructure can be
shuttered.
-Matt
_______________________________________________
Yt-dev mailing list
Yt-dev@lists.spacepope.org
http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
--
Cameron Hummels
PhD Candidate, Astronomy Department of Columbia University
Public Outreach Director, Astronomy Department of Columbia University
NASA IYA New York State Student Ambassador
PGP: 0x06F886E3
_______________________________________________
Yt-dev mailing list
Yt-dev@lists.spacepope.org
http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
_______________________________________________
Yt-dev mailing list
Yt-dev@lists.spacepope.org
http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
_______________________________________________
Yt-dev mailing list
Yt-dev@lists.spacepope.org
http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
participants (7)
-
Britton Smith -
Cameron Hummels -
chris.m.malone＠gmail.com -
j s oishi -
Matthew Turk -
Sam Skillman -
Stephen Skory