@Nightinggale ,
@devolution ,
@Mr. ZorG
Was
"develop" already merged into
"Release Candidate 3.0.2"?
If yes, then we could
simply consider "develop" closed and transfer the open todos into tickets.
To do so, we could try to figure out what the status of the todos above is?
(And then also decide what to do with them.)
A)
"Finished" and ready to be published with
"Release 3.0.2"
B)
"Finished" and ready to be published with
"Plains" (or later, not Release 3.0.2)
C)
"In Work" and to be finished and published with
"Release 3.0.2"
D)
"In Work" and to be finished and published with
"Plains" (or later, not Release 3.0.2)
E)
"Not Started" (or Failed) and to be documented as a
"Long Term Ticket" for future releases
----
My suggestion is more or less:
Finish what can be finished, shift what should be shifted, otherwise remove what can be removed.
There is no point to delay a release forever if things do not get implemented or finished.
(But we should also try to get an overview and clean up ticket documentation properly.)