I misread the question. My apologies.
A project that is releasing must only contain other release bits.
Regardless of the project phase (mature, incubation).
AFAICT, Eclipse Tycho has never done an actual release. Mickael
must have read it the same way that I did and interpreted
"incubation release" as "milestone build".
Tycho needs to do an actual release; the project is long overdue.
I'll connect with the project leads.
Wayne
On 16/11/16 11:05 AM, Simon Bernard
wrote:
Wayne,
You agreed but it seems Mickael and you are not saying the
exactly same thing.
Mickael seems to says that Releases (In our case incubation
release) can consume milestones release and you say "Releases
should themselves only consume release builds".
You agreed because you used "should" and not "must", right ?
Simon
Le 16/11/2016 à 16:39, Wayne Beaton a
écrit :
Agreed.
Milestone builds can consume milestone builds from other
projects.
Releases should themselves only consume release builds.
HTH,
Wayne
On 16/11/16 09:25 AM, Mickael
Istria wrote:
On 11/16/2016 03:24 PM, Simon
Bernard wrote:
Is it possible to release an incubation
release (e.g v0.9) which has a maven dependency on a
milestone release of another project (e.g. 2.0.0M5) ?
Yes, I think so.
Tycho does it often for instance: shipping an incubation
release consuming a milestone of equinox.
HTH
_______________________________________________
incubation mailing list
incubation@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/incubation
--
Wayne Beaton
@waynebeaton
The Eclipse Foundation
_______________________________________________
incubation mailing list
incubation@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/incubation
--
Wayne Beaton
@waynebeaton
The Eclipse Foundation
