Migration From dev.java.net
Issue tracker migration
Due to lack of features, poor performance and outages, we are migrating our Issue Tracker from java.net Issuezilla to a JIRA instance.
Volunteer Mike Vorburger did this. References:
TODO
DONE
Subversion migration checklist
Due to an old SVN version, poor performance and outages, we migrated our Subversion repository from java.net to SourceForge.
TODO
set up backups of new repo
block commits at old (java.net) repo
DONE
request dump of java.net mifos repository from Eric Renaud (CollabNet)
used svnsync to pull down full mirror instead. Currently on birch at ~adamm/svn_mirror/mifos
svnsync init file://$HOME/svn_mirror/mifoshttps://mifos.dev.java.net/svn/mifoscreate mostly empty (but executable)
$HOME/svn_mirror/mifos/hooks/pre-revprop-changescriptsvnsync sync file://$HOME/svn_mirror/mifos
disable commit permissions on java.net to prevent commits to the old repository
point Hudson to the new subversion repo
have active committers sign up on sourceforge and get commit rights
John Woodlock, Keith Woodlock
Keith Randall
Udai Gupta
Sungard: Chandan Rao,
Keith Pierce
Adam Monsen, Adam Feuer, Adam Monsen, Van Mittal-Henkle, Jeff Brewster, Ryan Whitney
Johan Hilding
Kimloan Ho
Pootle auto-commit user
instruct anyone with a checkout to
svn switch --relocateto the new repomigrate merge tracking information
keep using svnmerge for now... we'll likely migrate to Mercurial instead of using built-in SVN merging
point mifos.org and other links to java.net svn to sourceforge svn
create "mifospootle" user on sourceforge
enable commit emails using a hook script
if using a new commit email alias, update mifoscommits google group and mifos.scm on gmane
connect with http://cia.vc
update fisheye url to http://fisheye3.atlassian.com/browse/mifos
Issues and Commits mailing lists
These lists contain automated emails only. We currently have no plans to migrate these lists.