Define processes for osdn tickets
OSDN ticket system has its limitations compared to what we had in hrm (or in gna before that). Figure out processes to work with these limitations.
1) There seems to be no good tools for defining ticket relations with each other
2) There's no ticket status suitable for marking patch/fix to be in "Review Period"
why not go all in github , which may not be perfect but is far better than osdn, and directly linked to code, and other branches like freeciv-web ?
Or add a redmine instance on the same server as freeciv-web ?
Reply To alain_bkr
why not go all in github
I love redmine, but as of today 2022 , in github you have 4 ways to sorts things, this seems to be enough
A quick look at wesnoth (which is similar complexity to freeciv, maybe a bit bigger, more bugs, mores branches, more developers)
In the redmine link you care about Review period
I think you cannot get much more than 1 guy tested it, and it is in one branch, alpha, beta ...
Using github forks can be very useful, and much simpler and efficient than attached patched like in the 90's
Freeciv is not a compiler, maybe we could relax , and simplify the workflow, to make it easier and faster for everyone, including newcomers.