> ok, fair enough...but if the LTS has been investing so much time and effort > into > building a process for being able to release updates to simultaneous releases, > will they assume that burden from the Planning Council eventually?
No, not that I am aware of. As far as I am concerned, LTS is solving quite a different problem. > Will that effort be rolled back into the simultaneous release process that > the > Planning Council currently takes care of? At this point in time, the LTS working group is still very much in start-up mode. They're still figuring out how to do the builds and manage the processes. My advice is that any variant of the thought that somehow LTS will allow change to the simultaneous release process is wrong for at least the next year or two. I won't say never, but I certainly don't see it within any reasonable planning horizon. > maybe a slight off topic, if so my apologies No problem at all. For the record, I _like_ the idea of trying to accelerate our releases to encourage more innovation and participation. But there are lots of moving parts, requirements, and expectations which need to be satisfied. And very limited resources to do them. As but one example, our entire community lean heavily on the time and personal commitment of David Williams and Markus Knauer. Asking them to do more does not seem reasonable. Perhaps this conversation will spur others to step forward to help. _______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
