Re: [science-pmc] Participation in the Oxygen Simultaneous Release

[Jonah Graham <jonah@xxxxxxxxxxxxxxxx>]

Postpone until January.
~~~
Jonah Graham
Kichwa Coders Ltd.
www.kichwacoders.com


On 9 December 2016 at 14:37, Greg Watson <g.watson@xxxxxxxxxxxx> wrote:
> Availability for next Tuesday (other days have less participation):
>
> Greg Watson
> Christopher Brooks
> Jonah Graham
> Philip Wenig
> Peter Chang
>
> Should we hold the meeting or postpone until Jan?
>
> Greg
>
> On Dec 8, 2016, at 2:33 AM, Jonah Graham <jonah@xxxxxxxxxxxxxxxx> wrote:
>
> Hi Greg,
>
> I don't think January has a reason to participate, unless one of the
> dependent projects signs up to simrel. Perhaps a topic for the next pmc? BTW
> Are we having one next week? If it is the same participation as last time I
> think we should skip it.
>
> Jonah
>
> On 7 Dec 2016 2:16 p.m., "Greg Watson" <g.watson@xxxxxxxxxxxx> wrote:
>>
>> Science Project Leads:
>>
>> For those projects interested in participating in the next simultaneous
>> release, please note that you have to opt-in by Dec 16. To opt-in, you need
>> to create a minimal release record for your project, then announce your
>> intention to participate by emailing the cross-project-issues-dev list. See
>> this wiki page [1] for more details on the requirements for participating.
>>
>> Let me know if you have any questions or would like more information.
>>
>> [1] https://wiki.eclipse.org/SimRel/Simultaneous_Release_Requirements
>>
>> Thanks,
>> Greg
>>
>>
>>
>>
>> Begin forwarded message:
>>
>> From: Wayne Beaton <wayne@xxxxxxxxxxx>
>> Subject: [cross-project-issues-dev] State intent early (M4)
>> Date: December 6, 2016 at 11:19:08 AM EST
>> To: Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
>> Reply-To: Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
>>
>> Many projects have not yet announced their intention to participate (or
>> not) in the Oxygen Simultaneous release.
>>
>> The deadline is approaching. For our Oxygen release, that's Friday,
>> December 16/2016.
>>
>> Part of the reason why we require that project teams explicitly opt-in by
>> M4 is to ensure that project teams are paying attention to the communication
>> channel. It's also a quick reminder for everybody in the community to take a
>> quick look at your plans to make sure that they identify potential
>> challenges they may face working with you.
>>
>> Please take a quick look at the release participation page [1]. Please
>> also take a quick look at the "details" page [2].
>>
>> The details page shows the "summary" from the description that you've
>> provided in your release record; this is the first place that we'll look for
>> ideas regarding what we'll include in our press (and discussions with
>> analysts) about the release. Please try to provide a short executive summary
>> style paragraph at the beginning of your description (e.g. something that I
>> can say when I'm taking to people about your project; it's hard to say a
>> list of bullets): give people a reason to want to find out more about your
>> project.
>>
>> If your project does not appear on the participation page, please first
>> ensure that you've created a release record for Oxygen (with a reasonable
>> description), and then send a note to this channel with a pointer to that
>> release record and an indication of your project's offset in the build.
>> There's more information in the wiki [3] (while you're there, please take a
>> couple of minutes to scan the rest of the participation requirements
>> document).
>>
>> I did scan through the mailing list archives, and I'm pretty sure that
>> I've recorded all of the announcements made there. If I've missed you,
>> please accept my humble apologies and then restate.
>>
>> Thanks,
>>
>> Wayne
>>
>>
>> [1] https://projects.eclipse.org/releases/oxygen
>>
>> [2] https://projects.eclipse.org/releases/oxygen/details
>>
>> [3]
>> https://wiki.eclipse.org/SimRel/Simultaneous_Release_Requirements#State_intent_early_.28M4.29
>>
>> --
>> Wayne Beaton
>> @waynebeaton
>> The Eclipse Foundation
>> _______________________________________________
>> cross-project-issues-dev mailing list
>> cross-project-issues-dev@xxxxxxxxxxx
>> To change your delivery options, retrieve your password, or unsubscribe
>> from this list, visit
>> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>>
>>
>>
>> _______________________________________________
>> science-pmc mailing list
>> science-pmc@xxxxxxxxxxx
>> To change your delivery options, retrieve your password, or unsubscribe
>> from this list, visit
>> https://dev.eclipse.org/mailman/listinfo/science-pmc
>>
> _______________________________________________
> science-pmc mailing list
> science-pmc@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from
> this list, visit
> https://dev.eclipse.org/mailman/listinfo/science-pmc
>
>
>
> _______________________________________________
> science-pmc mailing list
> science-pmc@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from
> this list, visit
> https://dev.eclipse.org/mailman/listinfo/science-pmc
>