Difference between revisions of "WesnothGIT"

From The Battle for Wesnoth Wiki
m (Bug tracker)
(Bug tracker)
 
Line 10: Line 10:
 
** https://www.chiliproject.org/projects/chiliproject/wiki/Why_Fork
 
** https://www.chiliproject.org/projects/chiliproject/wiki/Why_Fork
 
* Counterpoint: Googling "redmine vs chiliproject" reveals some alternative viewpoints, for example http://colans.net/blog/redmine-and-chiliproject-are-great-issue-trackers-which-one-should-i-install
 
* Counterpoint: Googling "redmine vs chiliproject" reveals some alternative viewpoints, for example http://colans.net/blog/redmine-and-chiliproject-are-great-issue-trackers-which-one-should-i-install
 +
* Chiliproject is dead: http://en.wikipedia.org/wiki/Redmine#Fork
  
 
==lift up the bug tracker's contents==
 
==lift up the bug tracker's contents==

Latest revision as of 00:11, 17 June 2014

The move to git from Subversion has been done (see WesnothRepository for details).

TODO list

Bug tracker

Redmine, hosted locally on wesnoth.org, using the https://bugs.wesnoth.org name.

  1. set up a redmine instance on wesnoth.org

lift up the bug tracker's contents

scraping via https? getting bug repository dump? what about the files?

  • try to get database dump first
  • forgeplucker doesn't look ready
  • grab the database and run a local version of savannah?
  • import the data into the new bug tracker

connect the bugtracker with the source repository

Shouldn't be a problem - http://www.redmine.org/projects/redmine/wiki/RedmineSettings#Referencing-issues-in-commit-messages We should think about changing the old commit messages in the bug tracker to point to new repository.

This page was last edited on 17 June 2014, at 00:11.