Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
Bug/feature reqeust move to Sourceforge
oBFusCATed:
--- Quote from: dmoore on November 08, 2013, 07:21:08 pm ---I think this send a negative signal to our bug reporters.
--- End quote ---
Our reporters are already getting negative signals or to be more correct they get no signals, because almost no one bothers to follow or answer the reports.
dmoore:
PS: I do think github's issue tracker is pretty good (and avoids redundancy of having separate features/support/patch/bug report trackers) and it seems to be relatively easy to import and export data to/from.
dmoore:
--- Quote from: oBFusCATed on November 08, 2013, 08:08:14 pm ---
--- Quote from: dmoore on November 08, 2013, 07:21:08 pm ---I think this send a negative signal to our bug reporters.
--- End quote ---
Our reporters are already getting negative signals or to be more correct they get no signals, because almost no one bothers to follow or answer the reports.
--- End quote ---
Agree. Step 1 after the migration should be triaging the bugs reported at least in the last year. (About 100 by my count?)
ToApolytoXaos:
In case you decide to go with github's issue tracker, please count me in as Quality Assurance.
Cheers.
ollydbg:
FYI: I get one Reply from a SF guy:
--- Quote ---Hi, we don't have an import process available specifically for Berlios, but you can import tickets based on a certain JSON format. That format is not fully documented but you can create a test project/tracker and export its data and use that as a complete example. See Admin > Export, and Admin > Import > Allura Import. So if you have a way to extract the data from Berlios then you can create that json file and import it.
--- End quote ---
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version