As I understand it, the end goal is to find projects that are no longer
actively participating, but not actively participating is only bad when there
is a breakage that requires that project to react. These breakages are
relatively rare. So, to guard against a rare occurrence of a breakage that
requires an inactive project to react, we subject everyone to the
disable/enable struggle. The cost/benefit scale isn’t balancing in my mind.
I hope that the Planning Council will reconsider this policy and we can start a
release with the content of the previous release instead of a clean slate.
Thanks,
- Konstantin
From: Kaloyan Raev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
