[cross-project-issues-dev] Requirements to participate in the Oxygen (2017) Release repository

[David Williams]

  
  


Every year, the Planning Council specifies that M4 is the
  deadline for the council to have the official, final version of
  the Simultaneous
Release Requirements. This year is no exception (though,
  sorry, I am sending this note a bit late in the day). 

The requirements are the same as previous years, except we did
  add one new item. Its purpose is to help us all focus on the
  direction Eclipse needs to go with "continuous updates". At this
  point, though, the requirement is for projects to "document" such
  support and technically it is possible for a project to document
  "we do not support it". See the following section for the new
  requirement (and, please, read the whole document if you are new
  to the Sim. Release and, even if you are not new, I recommend at
  least skim reading it yearly! :) 


https://wiki.eclipse.org/SimRel/Simultaneous_Release_Requirements#Document_Yearly_Update_Policy
As mentioned there I have also opened bug
509237 to have an ongoing discussion of what issues prevent
  "continuous updates".
= = = = = 

Off topic: This is not related to requirements, but does not
  deserve its own note ... 

I have started a "trouble shooting" section in the Simultaneous
Release FAQ called Common
errors and what to do about them. Please contribute to it,
  if anyone has seen other common problems that I have forgotten
  about. 

= = = = = 

Thanks as always! 



  

___
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

[cross-project-issues-dev] Eclipse Paho participation in Oxygen

[Ian Craggs]

I just thought I'd make a better subject for the mail!  And add that 
Paho will not be in the shared repository.



On 12/16/2016 03:55 PM, James Sutton1 wrote:

Hi,
Paho would like to participate in the Oxygen simultaneous release. 
 I've set our release date to the correct date on our next release 
(1.3.0) here: http://projects.eclipse.org/projects/iot.paho/releases/1.3.0

Thanks,
James
Kind regards,
*James Sutton*
Software Engineer - IoT Foundation - MQTT Open Source Projects
Ops Team - Wimbledon Project


Phone: 01962 815438 | Extension: x372454
E-mail: james.sut...@uk.ibm.com 
Personal Website: www.jsutton.co.uk 
Find me on:  
 

IBM

Hursley Park
Hursley, SO212JN
United Kingdom

IBM United Kingdom Limited Registered in England and Wales with number 
741598 Registered office: PO Box 41, North Harbour, Portsmouth, Hants. 
PO6 3AU

Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with 
number 741598.

Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU



___
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


--
Ian Craggs
icra...@uk.ibm.com IBM United Kingdom
Paho Project Lead; Committer on Mosquitto

___
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

[cross-project-issues-dev] Projects that have not (AFAICT) declared participation in Oxygen

[James Sutton1]

Hi,
 
Paho would like to participate in the Oxygen simultaneous release.  I've set our release date to the correct date on our next release (1.3.0) here: http://projects.eclipse.org/projects/iot.paho/releases/1.3.0
 
Thanks,
 
James
 
Kind regards, 

James SuttonSoftware Engineer - IoT Foundation - MQTT Open Source ProjectsOps Team - Wimbledon Project
Phone: 01962 815438 | Extension: x372454E-mail: james.sut...@uk.ibm.comPersonal Website: www.jsutton.co.ukFind me on:  Hursley ParkHursley, SO212JNUnited Kingdom 

IBM United Kingdom Limited Registered in England and Wales with number 741598 Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6 3AUUnless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU


___
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

[cross-project-issues-dev] Triquetrum to participate in Oxygen

[Christopher Brooks]

Triquetrum intends to participate in Oxygen with Triquetrum 0.2.0 and a +3
offset.

https://projects.eclipse.org/projects/science.triquetrum/releases/0.2.0

_Christopher

-- 
Christopher Brooks, PMP
Academic Program Manager
CHESS/Ptolemy/TerraSwarm
707.332.0670, c...@eecs.berkeley.edu, https://ptolemy.eecs.berkeley.edu/~cxh
___
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

Re: [cross-project-issues-dev] The SOA Project website repo has gone missing

[Matthias Sohn]

On Fri, Dec 16, 2016 at 4:23 PM, Bob Brodt  wrote:

> Does anyone know what happened to https://git.eclipse.org/c/
> www.eclipse.org/soa.git/ ? It seems to have disappeared mysteriously...
>

file a bug for webmaster in Bugzilla under "Eclipse Foundation > Community
> Git"
___
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

Re: [cross-project-issues-dev] Projects that have not (AFAICT) declared participation in Oxygen

[Sven Efftinge]

Hi David,

yes, I am a representative of Xpand. And Karsten (Thoms) already formally
announced the participation in another mail.
Also Xpand has an aggrecon file, so I think we are fine.

Thank you!
Sven

2016-12-16 15:28 GMT+01:00 David Williams :

> On 12/15/2016 08:56 AM, Sven Efftinge wrote:
>
>>
>> Xpand is in maintenance mode, but I understood that it needs to be
>> included if other projects have a dependency on it.
>> In that case, I assume it is a viable option to just include last year's
>> release again.
>> Is that correct?
>>
>> That is correct. With some possible complications.
>
> Are you, Sven, saying to include Xpand as a representative of Xpand? If
> so, then I think fine for you to include it, in your own ?.aggrcon file. My
> guess is it would be best to also have a release record, even if it was not
> a new release, just repeat the previously released version, and say
> "maintenance mode, same version" as its release documentation. (But Wayne
> is the authority on release records).
>
> I can envision a few other cases and one of those will get complicated:
>
> 1. In the past, projects wanted to "include" a previous release of a
> project (or a few bundles) that was maintenance mode, and had no ?.aggrcon
> file of their own (i.e. no one left to represent the project) so in those
> cases the participating project "included" it, either directly via features
> or by mirroring to their own repository. This is a direct analogy to "the
> Orbit case".
>
> 2. The new case that might need some new procedure or policy:
> If there is a large project, say like DTP (just as an example), which is
> required by many, but has no one real representative, then technically it
> should NOT be in its own ?.aggrcon file, and SOMEONE should say they will
> include a copy of the previous release in their repository (or, in their
> own ?.aggrcon file?) for themselves and others to use. That way, there is
> always someone at least partially responsible for it if something goes
> wrong. If nothing goes wrong, everything is fine. If something does go
> wrong, SOMEONE has to do SOMETHING! (even if it is to decide "not to
> include it").
>
> I mention this last "special case" since it sounds like there are a number
> of projects "in maintenance mode" and I suspect they will all "work" for a
> while, but eventually, as I am sure you already know, they will no longer
> work. Hence, a long term "ownership" is required, even for maintenance mode.
>
> Thanks,
>
>
>
>
> ___
> 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
>



-- 
Sven Efftinge

TypeFox GmbH
Am Germaniahafen 1
24143 Kiel

Sitz: Kiel, Registergericht: Amtsgericht Kiel, HRB 17385
Managing Directors: Sven Efftinge, Moritz Eysholdt, Dr. Jan Köhnlein
___
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

Re: [cross-project-issues-dev] Projects that have not (AFAICT) declaredparticipation in Oxygen

[Igor Vinnykov]

Hello,

 

Subversive intends to participate in Oxygen Simultaneous Release with
version 4.1, and a +2 offset.

 

Best regards,

Igor Vinnykov

 

  _  

From: cross-project-issues-dev-boun...@eclipse.org
[mailto:cross-project-issues-dev-boun...@eclipse.org] On Behalf Of Wayne
Beaton
Sent: Wednesday, December 14, 2016 10:07 PM
To: Cross project issues
Subject: [cross-project-issues-dev] Projects that have not (AFAICT)
declaredparticipation in Oxygen

 

According to my records, the following projects have not yet declared their
intent to participate in our Oxygen Simultaneous Release. The deadline to
state your intention to participate is this Friday, December 16/2016.

If your project is listed below, please take immediate steps to declare your
intent to participate. The process is described in the Planning Council's
documentation [1] and in the Eclipse Committer Handbook [2]. If you really
are planning to drop out of the simultaneous release, please also let us
know.

*   Xpand
*   Thym
*   Maven Integration for Web Tools Platform
*   Lua Development Tools (LDT)
*   Subversive - SVN Team Provider
*   Eclipse Paho
*   Andmore - Eclipse Android Tooling
*   Accessibility Tools Framework
*   Java Workflow Tooling
*   Eclipse Gyrex Project
*   ATL - A Model Transformation Technology
*   Data Tools Platform
*   Graphical Modeling Framework (GMF) Tooling
*   Graphical Modeling Framework (GMF) Notation
*   Graphical Modeling Framework (GMF) Runtime
*   EMF Transaction
*   EMF Validation
*   EMF Query

If a project that you depend on is on this list, please make that concern
known as well. I know that we have some staffing challenges on a handful of
these, so it will be valuable to know who cares about something that is
missing.

Note that I did add EMF Validation and Query to the list based on the
description in the release records. AFAICT, the project teams have not
formally declared.

I've updated the dates on the wiki page [3]

*   December 16/2016 - Opt-in deadline
*   February 17/2017 - CQ Submission deadline (specify that the CQ is
required for Oxygen)
*   May 24/2017 - IP Log submission deadline
*   May 31/2017 - Review materials due
*   June 7/2017 - First round of release reviews (aim for this date if
you can)
*   June 21/2017 - Second (final?) round of release reviews
*   June 28/2017 - Eclipse Oxygen GA

Please pay special attention to the CQ deadline to give the IP Team a
fighting chance of getting all the required CQs processed. If you know that
you're going to be coming in late with some third-party dependencies, please
contact emo-ip-t...@eclipse.org to let them know.

Thanks,

Wayne

[1]
https://wiki.eclipse.org/SimRel/Simultaneous_Release_Requirements#State_inte
nt_early_.28M4.29
[2]
https://www.eclipse.org/projects/handbook/#pmi-joining-a-simultaneous-releas
e
[3] https://wiki.eclipse.org/Category:Oxygen
-- 
Wayne Beaton
@waynebeaton
The Eclipse Foundation
   

___
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

[cross-project-issues-dev] The SOA Project website repo has gone missing

[Bob Brodt]

Does anyone know what happened to
https://git.eclipse.org/c/www.eclipse.org/soa.git/ ? It seems to have
disappeared mysteriously...

-- 

Robert ("Bob") Brodt
Senior Software Engineer
JBoss by Red Hat
___
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

[cross-project-issues-dev] ATL participation in Oxygen

[Dennis Wagelaar]

ATL intends to participate in Oxygen, with ATL 3.8, and a +2 offset.


Kind regards,

Dennis Wagelaar
___
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

[cross-project-issues-dev] Oxygen M4 is available

[David Williams]

Oxygen M4 has been made available at the built-in URL of

http://download.eclipse.org/releases/oxygen/

(It is a composite, now consisting of M4, M3, and M2.)


The EPP Packages are (or will be soon) available at the "developers" tab 
for packages, at


https://www.eclipse.org/downloads/index-developer.php

(I believe EPP is still waiting for a few package maintainers to 
approve, before ALL packages will be visible there).


Thanks everyone for participating!

One more for 2016: Neon.2 next Wednesday!


___
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

[cross-project-issues-dev] JWT participation in Oxygen

[Marc Dutoo]

Hi  all,

The Eclipse JWT (Java Workflow Tooling) project intends to participate 
in the Oxygen simultaneous release, with an offset of +3 (as usual).


The release record can be found in the PMI tool here:

https://projects.eclipse.org/projects/soa.jwt/releases/1.7.0

More details about JWT Oxygen contribution TODO list can be found at 
https://wiki.eclipse.org/JWT_Ramp-Down-Policy .


Regards,
Marc Dutoo
Eclipse JWT project co-lead
Smile
http://www.smile.fr
___
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

Re: [cross-project-issues-dev] Projects that have not (AFAICT) declared participation in Oxygen

[David Williams]

On 12/15/2016 08:56 AM, Sven Efftinge wrote:


Xpand is in maintenance mode, but I understood that it needs to be 
included if other projects have a dependency on it.
In that case, I assume it is a viable option to just include last 
year's release again.

Is that correct?


That is correct. With some possible complications.

Are you, Sven, saying to include Xpand as a representative of Xpand? If 
so, then I think fine for you to include it, in your own ?.aggrcon file. 
My guess is it would be best to also have a release record, even if it 
was not a new release, just repeat the previously released version, and 
say "maintenance mode, same version" as its release documentation. (But 
Wayne is the authority on release records).


I can envision a few other cases and one of those will get complicated:

1. In the past, projects wanted to "include" a previous release of a 
project (or a few bundles) that was maintenance mode, and had no 
?.aggrcon file of their own (i.e. no one left to represent the project) 
so in those cases the participating project "included" it, either 
directly via features or by mirroring to their own repository. This is a 
direct analogy to "the Orbit case".


2. The new case that might need some new procedure or policy:
If there is a large project, say like DTP (just as an example), which is 
required by many, but has no one real representative, then technically 
it should NOT be in its own ?.aggrcon file, and SOMEONE should say they 
will include a copy of the previous release in their repository (or, in 
their own ?.aggrcon file?) for themselves and others to use. That way, 
there is always someone at least partially responsible for it if 
something goes wrong. If nothing goes wrong, everything is fine. If 
something does go wrong, SOMEONE has to do SOMETHING! (even if it is to 
decide "not to include it").


I mention this last "special case" since it sounds like there are a 
number of projects "in maintenance mode" and I suspect they will all 
"work" for a while, but eventually, as I am sure you already know, they 
will no longer work. Hence, a long term "ownership" is required, even 
for maintenance mode.


Thanks,



___
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

Re: [cross-project-issues-dev] Projects that have not (AFAICT) declared participation in Oxygen

[Frédéric Jouault]

Hello,

ATL intends to participate in Oxygen Simultaneous Release with ATL
3.8, and a +2 offset.


Thanks,

Frédéric


> From: Wayne Beaton 
> Date: Wed, Dec 14, 2016 at 9:07 PM
> Subject: [cross-project-issues-dev] Projects that have not (AFAICT) declared 
> participation in Oxygen
> To: Cross project issues 
>
>
> According to my records, the following projects have not yet declared their 
> intent to participate in our Oxygen Simultaneous Release. The deadline to 
> state your intention to participate is this Friday, December 16/2016.
>
> If your project is listed below, please take immediate steps to declare your 
> intent to participate. The process is described in the Planning Council's 
> documentation [1] and in the Eclipse Committer Handbook [2]. If you really 
> are planning to drop out of the simultaneous release, please also let us know.
>
> Xpand
> Thym
> Maven Integration for Web Tools Platform
> Lua Development Tools (LDT)
> Subversive - SVN Team Provider
> Eclipse Paho
> Andmore - Eclipse Android Tooling
> Accessibility Tools Framework
> Java Workflow Tooling
> Eclipse Gyrex Project
> ATL - A Model Transformation Technology
> Data Tools Platform
> Graphical Modeling Framework (GMF) Tooling
> Graphical Modeling Framework (GMF) Notation
> Graphical Modeling Framework (GMF) Runtime
> EMF Transaction
> EMF Validation
> EMF Query
>
> If a project that you depend on is on this list, please make that concern 
> known as well. I know that we have some staffing challenges on a handful of 
> these, so it will be valuable to know who cares about something that is 
> missing.
>
> Note that I did add EMF Validation and Query to the list based on the 
> description in the release records. AFAICT, the project teams have not 
> formally declared.
>
> I've updated the dates on the wiki page [3]
>
> December 16/2016 - Opt-in deadline
> February 17/2017 - CQ Submission deadline (specify that the CQ is required 
> for Oxygen)
> May 24/2017 - IP Log submission deadline
> May 31/2017 - Review materials due
> June 7/2017 - First round of release reviews (aim for this date if you can)
> June 21/2017 - Second (final?) round of release reviews
> June 28/2017 - Eclipse Oxygen GA
>
> Please pay special attention to the CQ deadline to give the IP Team a 
> fighting chance of getting all the required CQs processed. If you know that 
> you're going to be coming in late with some third-party dependencies, please 
> contact emo-ip-t...@eclipse.org to let them know.
>
> Thanks,
>
> Wayne
>
> [1] 
> https://wiki.eclipse.org/SimRel/Simultaneous_Release_Requirements#State_intent_early_.28M4.29
> [2] 
> https://www.eclipse.org/projects/handbook/#pmi-joining-a-simultaneous-release
> [3] https://wiki.eclipse.org/Category:Oxygen
> --
> Wayne Beaton
> @waynebeaton
> The Eclipse Foundation
>
> ___
> 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
___
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

[cross-project-issues-dev] ACTF participation to Oxygen

[Kentarou Fukuda]

Hi all,

ACTF will contribute 1.5.0 to Oxygen (Offset +3).

https://projects.eclipse.org/projects/technology.actf/releases/1.5.0

Excuse me for this last mintute paticipation announcement.

Best regards,
Kentarou
---
Kentarou Fukuda, Ph.D.
IBM Research - Tokyo
Tel: +81-3-3808-5252
E-mail: kenta...@jp.ibm.com

___
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