On 12/20/2012 10:20 PM, David M Williams wrote:
Most of you know, that we normally keep 3 milestones in our common
repository, as a composite.
This works as long as no one removes a feature or a feature is
mistakenly "down versioned".
The easiest fix at this point, for common repo is just to make the
common repo be M4 only
I think it's a good move to put only one version in the repo since
before, some errors (missing IUs) in Milestone M could have been hidden
by what's provided in milestone M-1.
Having a single milestone makes the releases/kepler repo much closer
from what will be the final repo, and it seems more helpful to catch
possible issues early.
Cheers,
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets
<http://twitter.com/mickaelistria>
_______________________________________________
cross-project-issues-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
