Re: [cross-project-issues-dev] Planning to make .../releases/kepler be M

[David M Williams <david_williams@xxxxxxxxxx>]

> 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.

Yes, that's the way we used to do things,
and (some) people asked we leave all previous milestones there so people
could "roll back" if they wanted to. Our compromise was we'd
leave up to 3 unless there was known problems doing to, in which case we'd
announce what was happening and go with only latest (or latest -1). 

While having multiple milestones in
the composite is different than the one release in June, it is very similar
to what we end up with after 1, then 2, service releases.  Some have
argued we should not do that either (and always just have one release there)
... but ... I've never seen consensus on how to satisfy all the different
use cases. 

But agree there could be more automated
tests and reports to find issues ... all it takes is someone to do the
work! 

 



From:      
 Mickael Istria <mistria@xxxxxxxxxx>
To:      
 cross-project-issues-dev@xxxxxxxxxxx,

Date:      
 12/21/2012 02:34 AM
Subject:    
   Re: [cross-project-issues-dev]
Planning to make .../releases/kepler be M4 only
Sent by:    
   cross-project-issues-dev-bounces@xxxxxxxxxxx

---

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
My
blog - My
Tweets_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev