Hi
A couple of years ago, David tried chucking everyone out at M1 if they
hadn't announced. This was fairly disastrous since some projects have a
holiday till after M1.
Last year we reverted to an M4 deadline with 3 milestones of warnings
and it worked much better, but now we don't have so long.
There are two important things to know.
1) Is there a major version change requiring changed API accommodation?
- this should be announced noisily on cross-project with a link to
perhaps a Wiki page / Bugzilla. With three month releases perhaps
non-trivial API changes should be made available one release cycle early.
2) Is a project dying? - the dying project is often not alive enough to
announce its death. Late remedial action was required at Photon RC2/RC3.
With much reduced timescales, do dead projects automatically get
contributed for perhaps two cycles to give other projects a chance to
adapt / resurrect?
The I'm alive email announcements seem like a waste of time. A PMI entry
does the same and a timely PMI report might identify those projects that
may be dying.
Regards
Ed Willink
On 10/07/2018 15:12, Kenn Hussey wrote:
The FAQ [1] mentions an annual round-up coordinated by the EMO where
projects can declare their intention to (continue to) be on the train,
but it's unclear (to me, anyway) whether this already happened as part
of the Photon.0 release.
Regardless of how projects declare their intention to participate in a
given release, it would seem useful for projects to become aware of
what _type_ of release the other projects intend to contribute
(especially for projects with close dependencies) early on in the
cycle. In the absence of a redundant email declaration, I'm not sure
where one is expected to easily find this out (short of looking
through other project's contributions to the aggregator)...
[1] https://wiki.eclipse.org/SimRel/Simultaneous_Release_Cycle_FAQ
On Tue, Jul 10, 2018 at 8:47 AM Ed Willink <e...@willink.me.uk
<mailto:e...@willink.me.uk>> wrote:
Hi
The PMI seems to have nearly all the support for this, and
ultimately a PMI release record is required.
It appears that there is an EMO-maintained participation that
records which SimRels are project is part of.
Don't we just need a pulldown to indicate select an offset and
which, if any, SimRel a future release is targetted at?
Regards
Ed Willink
On 10/07/2018 13:04, Ed Merks wrote:
A general question...
I thought that all projects in Photon are automatically in
2018.09 and that we'd only need to announce if we plan to drop
from the train. Isn't that the case?
It seems a slightly redundant to send out a flood of these notes
every 3 months.
On 10.07.2018 12:13, Karsten Thoms wrote:
Hi all,
Xpand will participate in the 2018.09 release with offset +2. We
are planning to contribute version 2.2.0 again.
https://projects.eclipse.org/projects/modeling.m2t.xpand/releases/2.2.0
Kind regards,
~Karsten
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
<mailto:cross-project-issues-dev@eclipse.org>
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
<mailto:cross-project-issues-dev@eclipse.org>
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
Virus-free. www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
<#m_-3912059958609441463_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
<mailto:cross-project-issues-dev@eclipse.org>
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
