Issue numbers from the sourceforge bug tracking system prior to migration did not migrate in project upgrade, and description of upgrade consequences did not warn of this.
As a test of the project upgrade path, I upgraded the sarmanager project. The consequences of upgrade appear to be poorly documented in the requests for projects to upgrade. One severe side consequence is the renumbering of issues in the sourceforge issue tracking system.
For example, what was issue: 3484452 has become issue 21, breaking crossreferences between the issue tracker and svn commit messages. Thus the commit message in https://sourceforge.net/p/sarmanager/code/35/ can no longer be related to the relevant issue: https://sourceforge.net/p/sarmanager/bugs/21/
A requirement of the migration of an issue tracking system which exposes issue numbers is the retention of issue numbers. Issue numbers may be referenced in many arbitrary places outside of the issue tracking system itself.
I'm not going to be able to upgrade other projects until this issue has been resolved.
Log in to post a comment.