Reconsider assigning all open issues to current release and moving them from release to release
From https://www.eclipse.org/lists/escet-dev/msg00303.html:
I was away last week, and upon return I found several hundred messages in the inbox of escet.
Aside from the discussions wrt development (which I don't do enough in escet
🙁 ) many messages were more administrative around the release and update of a new version. I am not sure what we're doing now is the simplest way, so maybe we should discuss that.First of all, moving of all open issues to the next milestone. I think it's clear by now that this action is not realistic in the sense that we're going to resolve all of them in the next 3 months. In other words, in about 3 months 80% of them will again get moved. So what I'd like to propose is that we don't attach issues to the next release. Instead, either don't attach them to a milestone or to a milestone "pending" or some other name. Obviously you can have several such milestones if you want to express some form of priority or road-map but not sure that's needed.