It's as simple as "as plans are a valuable means for the community to get involved with your project, the plan should be started at the beginning of the release cycle. By establishing the plan early, you give prospective contributors help in determining how they can most usefully contribute, and adopters can prepare their own development schedule and themes. ", as stated in [1].
If you are excelling at communicating to possible contributors know what areas they can contribute on for the current cycle, and letting adopters know what exactly will be in the future release / was in a past release, I'm pretty sure your PMC would tolerate a project plan that just point to information maintained elsewhere :)
There is a doc explaining the rationale of this plan process?
I just hate doing paperwork stuff just because I have to and not understand why I have to :)
_______________________________________________
cf-dev mailing list
cf-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cf-dev