[cross-project-issues-dev] EMF and XSD Participation in SimRel YYYY-MM

[Ed Merks]

EMF and XSD will always (at least until further notice) participate in
every SimRel YYYY-MM and do so at offset -1.

The release record for EMF's and XSD's latest ongoing releases will
always be available here:

  https://projects.eclipse.org/projects/modeling.emf.emf
  https://projects.eclipse.org/projects/modeling.mdt.xsd

I would suggest that pawing through this mailing list's archive is
perhaps not an ideal way to gather this information. Is that how the
following list is maintained?

  https://projects.eclipse.org/releases/2018-09

Is that done manually?  Could this list perhaps be generated from the
release records we create?

[Matthias Sohn]

Post by Ed Merks
EMF and XSD will always (at least until further notice) participate in
every SimRel YYYY-MM and do so at offset -1.
The release record for EMF's and XSD's latest ongoing releases will
https://projects.eclipse.org/projects/modeling.emf.emf
https://projects.eclipse.org/projects/modeling.mdt.xsd
I would suggest that pawing through this mailing list's archive is
perhaps not an ideal way to gather this information. Is that how the
following list is maintained?
https://projects.eclipse.org/releases/2018-09
Is that done manually? Could this list perhaps be generated from the
release records we create?

Could we add a corresponding field in the PMI release record ?

[image: Screen Shot 2018-07-13 at 08.42.12.png]
​

[Ed Merks]

Matthias,

Yes, something in the PMI release record would be great.. Although
thinking how to implement it given the diverse nature of the overall set
of projects and the fact that there might be (in the future) multiple
SimRel-type activities for other project groups and that some release
might be contributed to multiple SimRels, e.g., if a project chooses to
simply recontribute an existing release for a given 3 month interval,
rather than creating a new one, it's likely not totally trivial.  But
Wayne and team have done a great job with the project portal to date...

Post by Ed Merks
EMF and XSD will always (at least until further notice)
participate in
every SimRel YYYY-MM and do so at offset -1.
The release record for EMF's and XSD's latest ongoing releases will
https://projects.eclipse.org/projects/modeling.emf.emf
https://projects.eclipse.org/projects/modeling.mdt.xsd
I would suggest that pawing through this mailing list's archive is
perhaps not an ideal way to gather this information. Is that how the
following list is maintained?
https://projects.eclipse.org/releases/2018-09
Is that done manually?  Could this list perhaps be generated from the
release records we create?
Could we add a corresponding field in the PMI release record ?
Screen Shot 2018-07-13 at 08.42.12.png
​
_______________________________________________
cross-project-issues-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

[Ed Willink]

Hi

As I pointed out earlier, there appears to be a hidden "participated-in"
that the EMO presumably fills in as a consequence of a successful
review. As committers we just need a simple "intends to participate in"
which will should just be a single next release for the intended
participation of the corresponding planned release. If explicit
recontribution is necessary, then a reviewed release could offer a very
similar checkbox+menu for its next planned recontribution.

    Regards

        Ed Willink

Post by Ed Merks
Matthias,
Yes, something in the PMI release record would be great.. Although
thinking how to implement it given the diverse nature of the overall
set of projects and the fact that there might be (in the future)
multiple SimRel-type activities for other project groups and that some
release might be contributed to multiple SimRels, e.g., if a project
chooses to simply recontribute an existing release for a given 3 month
interval, rather than creating a new one, it's likely not totally
trivial.  But Wayne and team have done a great job with the project
portal to date...

Post by Ed Merks
EMF and XSD will always (at least until further notice)
participate in
every SimRel YYYY-MM and do so at offset -1.
The release record for EMF's and XSD's latest ongoing releases will
https://projects.eclipse.org/projects/modeling.emf.emf
https://projects.eclipse.org/projects/modeling.mdt.xsd
I would suggest that pawing through this mailing list's archive is
perhaps not an ideal way to gather this information. Is that how the
following list is maintained?
https://projects.eclipse.org/releases/2018-09
Is that done manually?  Could this list perhaps be generated from the
release records we create?
Could we add a corresponding field in the PMI release record ?
Screen Shot 2018-07-13 at 08.42.12.png
​
_______________________________________________
cross-project-issues-dev mailing list
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
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

[Wayne Beaton]

I maintain the list of participating projects on behalf of the Eclipse
Planning Council. I update the record as announcements are made on this
mailing list.

https://projects.eclipse.org/releases/2018-09

FWIW, the implementation accounts for multiple mappings between project
releases and simultaneous release instances (i.e. a single project release
can be part of multiple simultaneous release instances).

When your project gets listed here, the project record and corresponding
release record automatically get the "This release is part of X"
notification. This notice appears regardless of release state or whether or
not a review record exists.

Note that (per my earlier note) maintaining this project participation list
is not the primary goal of the email notification requirement.

Wayne

Post by Ed Willink
Hi
As I pointed out earlier, there appears to be a hidden "participated-in"
that the EMO presumably fills in as a consequence of a successful review.
As committers we just need a simple "intends to participate in" which will
should just be a single next release for the intended participation of the
corresponding planned release. If explicit recontribution is necessary,
then a reviewed release could offer a very similar checkbox+menu for its
next planned recontribution.
Regards
Ed Willink
Matthias,
Yes, something in the PMI release record would be great.. Although
thinking how to implement it given the diverse nature of the overall set of
projects and the fact that there might be (in the future) multiple
SimRel-type activities for other project groups and that some release might
be contributed to multiple SimRels, e.g., if a project chooses to simply
recontribute an existing release for a given 3 month interval, rather than
creating a new one, it's likely not totally trivial. But Wayne and team
have done a great job with the project portal to date...

Post by Ed Merks
EMF and XSD will always (at least until further notice) participate in
every SimRel YYYY-MM and do so at offset -1.
The release record for EMF's and XSD's latest ongoing releases will
https://projects.eclipse.org/projects/modeling.emf.emf
https://projects.eclipse.org/projects/modeling.mdt.xsd
I would suggest that pawing through this mailing list's archive is
perhaps not an ideal way to gather this information. Is that how the
following list is maintained?
https://projects.eclipse.org/releases/2018-09
Is that done manually? Could this list perhaps be generated from the
release records we create?

Could we add a corresponding field in the PMI release record ?
[image: Screen Shot 2018-07-13 at 08.42.12.png]
​
_______________________________________________
To change your delivery options, retrieve your password, or unsubscribe from this list, visithttps://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
To change your delivery options, retrieve your password, or unsubscribe from this list, visithttps://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_866905489063409777_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
_______________________________________________
cross-project-issues-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev