|Re: [eclipse.org-planning-council] Request for re-spin on behalf of the MPC project|
+1 for finding a way to automate this so that we don’t have to decide between the burden on Markus and David and the burden on our users.
It would also be good to understand why we’re finding so many major quality problems so late. And as an adopter and as a user, I’m not happy we always decide to skimp on quality to make the schedule. This is why I never recommend people take the June release.
I also wonder with more frequent releases, we wouldn't hinge so much on this June release. That way we could cut content to save quality with the promise of the content landing with quality 3 months later.
From: <eclipse.org-planning-council-bounces@xxxxxxxxxxx> on behalf of Ian Bull <irbull@xxxxxxxxxxxxxxxxx>
Reply-To: Eclipse Planning Council <eclipse.org-planning-council@xxxxxxxxxxx>
Date: Thursday, June 18, 2015 at 6:06 PM
To: Mike Milinkovich <mike.milinkovich@xxxxxxxxxxx>, Eclipse Planning Council <eclipse.org-planning-council@xxxxxxxxxxx>
Subject: Re: [eclipse.org-planning-council] Request for re-spin on behalf of the MPC project
Back to the top