The public shaming was to start next week. :-) I've added Eclipse Collections to the list.
Wayne On Wed, May 8, 2019 at 4:08 PM Nanivadekar, Nikhil < [email protected]> wrote: > Hi Wayne, Eclipse Collections will be participating. There will not be a > new release which we will contribute. I will touch the aggrcon file and > commit. > > Pardon my ignorance if this was discussed before. > > > > Thanks, > > Nikhil. > > > > > > *The Goldman Sachs Group, Inc. All rights reserved*. > > See http://www.gs.com/disclaimer/global_email for important risk > disclosures, conflicts of interest and other terms and conditions relating > to this e-mail and your reliance on information contained in it. This > message may contain confidential or privileged information. If you are not > the intended recipient, please advise us immediately and delete this > message. See http://www.gs.com/disclaimer/email for further information > on confidentiality and the risks of non-secure electronic communication. > If you cannot access these links, please notify us by reply message and we > will send the contents to you. > > > > *From:* [email protected] < > [email protected]> *On Behalf Of *Wayne Beaton > *Sent:* Wednesday, May 08, 2019 2:05 PM > *To:* Cross project issues <[email protected]> > *Subject:* [cross-project-issues-dev] Simultaneous Release 2019-06 opt-in > > > > Greetings Simultaneous Release 2019-06 participants. > > > > Per our process, I have started to assemble the participants list for > 2019-06 > <https://urldefense.proofpoint.com/v2/url?u=https-3A__projects.eclipse.org_releases_2019-2D06&d=DwMFaQ&c=7563p3e2zaQw0AB1wrFVgyagb2IE5rTZOYPxLxfZlX4&r=h7JOQQIGild4afzuJspD2UtIxQINBIgyaphkOA7Zg1k&m=zp0clNPMtJWbNMfwsx3vb2UTfzBdbw99TPIqic49_fc&s=7FxN17CzM8EfDD2tjbd5mD_noxXhfLSC0nSQVu-MVUM&e=> > . > > > > By way of reminder, the process requires > <https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.eclipse.org_SimRel_Simultaneous-5FRelease-5FRequirements-23State-5Fintent-5Fearly&d=DwMFaQ&c=7563p3e2zaQw0AB1wrFVgyagb2IE5rTZOYPxLxfZlX4&r=h7JOQQIGild4afzuJspD2UtIxQINBIgyaphkOA7Zg1k&m=zp0clNPMtJWbNMfwsx3vb2UTfzBdbw99TPIqic49_fc&s=Mc8wz9WRTL7imcNoevYSel9M7xqjYo8k53GUGf5DcgI&e=> > that project teams signal their participation by making a change to their > aggrcon file in the simrel repository. For project teams that intend to > drop out of the simultaneous release, the process requires that you inform > the group and then remove your aggrcon file. > > > > For projects that did participate in the previous simultaneous release, > the project team's representative must touch the project's aggrcon file by > the milestone 2 (M2) date of the release to indicate that the project > wishes to continue participating and that they project team is paying > attention. > > > > AFAICT, 49 project teams have changed their aggrcon file since the start > of this release cycle. I have captured my best guess at the version that > each project is participating with. Please have a look and let me know what > I've gotten wrong. > > > > Note that if you are adding a new version of your content (major, minor, > or service), you need to create a release record. Make sure that your > release record has "2019-06-19" as the release date (I did notice that > least one existing release record showed 2019-06-20 as the release date; > please have a look and fix your record if this is you). > > > > Please create the release record (or ensure that it has been created) > before you tell me that I've listed the wrong version. > > > > Version names must include some form of a semantic version. You can prefix > or suffix version names as you'd like. The convention appears to be to not > prefix or suffix, or to include the simultaneous release name as a suffix. > > > > Note that the PMI doesn't handle numbers appearing before the semantic > version very well, but I have a fix in the queue that should sort this out > in time for the release. > > > > I intend to do a pass over the simrel repository again on Friday, May 10 > (M2) to bring the participation list up to date and will start the public > shaming of those who have not followed the rules sometime thereafter. > > > > Per the December 2018 update to the EDP, project teams are not required to > engage in a release review if they've engaged in one in the year leading up > to their release date. No review is required. No PMC approval is required. > No IP log review is required. *Remember that whether or not you engage in > a review, project teams are required to follow the Eclipse IP Due Diligence > Process. Your releases must only include IP that has been either "license > certified" or "approved" by the IP Team. *I will initiate a scan of the > repository tonight to ensure that unvetted IP has not been inadvertently > added. > > > > Thanks for your attention. > > > > Wayne > > > > -- > > *Wayne Beaton* > > *Director of Open Source Projects | **Eclipse Foundation, Inc.* > > ------------------------------ > > Your Personal Data: We may collect and process information about you that > may be subject to data protection laws. For more information about how we > use and disclose your personal data, how we protect your information, our > legal basis to use your information, your rights and who you can contact, > please refer to: www.gs.com/privacy-notices > _______________________________________________ > cross-project-issues-dev mailing list > [email protected] > To change your delivery options, retrieve your password, or unsubscribe > from this list, visit > https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev -- Wayne Beaton Director of Open Source Projects | Eclipse Foundation, Inc.
_______________________________________________ cross-project-issues-dev mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
