Re: [cross-project-issues-dev] Eclipse IDE 2022-03 participation

[Wayne Beaton]

Done.

Wayne

On Fri, Mar 11, 2022 at 9:22 AM Mickael Istria  wrote:

> Hi,
>
> Wild Web Developer 0.13.3 is part of SimRel (for a relatively long time
> already, so no extra things like respins to worry about). Can the 2022-03
> metadata please be changed accordingly?
>
> Thanks in advance
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
>


-- 

Wayne Beaton

Director of Open Source Projects | Eclipse Foundation
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Eclipse IDE 2022-03 participation

[Mickael Istria]

Hi,

Wild Web Developer 0.13.3 is part of SimRel (for a relatively long time
already, so no extra things like respins to worry about). Can the 2022-03
metadata please be changed accordingly?

Thanks in advance
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Eclipse IDE 2022-03 participation

[Wayne Beaton]

Updated! Thanks.

Does anybody else have any updates?

Wayne

On Tue, Mar 8, 2022 at 11:00 AM Pierre-Charles David <
pierre-charles.da...@obeo.fr> wrote:

> Le 02/03/2022 à 19:59, Wayne Beaton a écrit :
>
> Greetings folks.
>
> I've created the release page for 2022-03
> . Please have a look to
> make sure that I have the information for your project captured correctly.
>
>
> EMF Services will still contribute the same 1.12.2 as before instead of
> version 1.13.0, which I could not find the time to release (I've moved its
> date further in the PMI).
>
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
>


-- 

Wayne Beaton

Director of Open Source Projects | Eclipse Foundation
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Eclipse IDE 2022-03 participation

[Pierre-Charles David]

Le 02/03/2022 à 19:59, Wayne Beaton a écrit :

Greetings folks.

I've created the release page for 2022-03 
. Please have a look to 
make sure that I have the information for your project captured correctly.



EMF Services will still contribute the same 1.12.2 as before instead of 
version 1.13.0, which I could not find the time to release (I've moved 
its date further in the PMI).


___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Eclipse IDE 2022-03 participation

[Wayne Beaton]

Reviews are not required for service/maintenance releases. Further, it
appears that the project team engaged in a progress review last July, so no
reviews are required until this July.

I ran the Dash License Tool on the m2e-core repository and everything seems
to be in order from an intellectual property due diligence point of view.

I've updated the project's record on the participation page.

It looks like you're good to go.

Wayne

On Fri, Mar 4, 2022 at 3:18 PM Hannes Wellmann 
wrote:

> For M2E version 1.20.1 was just released [1], which is a maintenance
> release for m2e 1.20.0 that only adds signatures for embedded *.jnilib
> files to fulfill the requirements of macOS-notarization.
>
> The release entry for the project page is [2]. I have already created a
> Gerrit-change to update M2E's SimRel contribution.
> Please consider it for the project page.
>
> Do we have to start a IP Due Diligence Process for this release?
>
> Thanks,
>
> Hannes
>
>
> [1] - https://www.eclipse.org/lists/m2e-dev/msg02479.html
> [2] - https://projects.eclipse.org/projects/technology.m2e/releases/1.20.1
>
> *Gesendet:* Mittwoch, 02. März 2022 um 19:59 Uhr
> *Von:* "Wayne Beaton" 
> *An:* "Cross project issues" 
> *Betreff:* [cross-project-issues-dev] Eclipse IDE 2022-03 participation
> Greetings folks.
>
> I've created the release page for 2022-03
> <https://projects.eclipse.org/releases/2022-03>. Please have a look to
> make sure that I have the information for your project captured correctly.
>
> As usual, I had to make some guesses at the versions included. I did check
> the list against changes in the simrel repository and -- in some cases -- I
> created release records on behalf of the project teams based on what I saw
> (mostly when I saw a new minor version). Again, please make sure that I've
> correctly captured the release information for your project. Please make
> sure that you provide a short description in the corresponding release
> record.
>
> If your project is contributing a new minor or major version and has not
> engaged in either a progress or release review in the past 12 months,
> please connect with EMO as soon as possible to schedule a release review.
>
> Note that, even if your project does not require a review at this time,
> you are required to implement the IP Due Diligence Process for your
> release. That is -- even if you are contributing a service release, or have
> completed a release or progress review in the past 12 months -- you are
> still required to complete the IP Due Diligence Process for any content
> that is included in your release (this includes both project or third-party
> content).
>
> I've been experimenting with running the Eclipse Dash IP Log Tool
> <https://github.com/eclipse/dash-licenses> on (more-or-less) randomly
> selected project repositories and it seems to function well. If you have an
> opportunity to try it, I would love to hear about your experience.
>
> Wayne
>
> --
>
> Wayne Beaton
>
> Director of Open Source Projects | Eclipse Foundation
> ___ cross-project-issues-dev
> mailing list cross-project-issues-dev@eclipse.org To unsubscribe from
> this list, visit
> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
>
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
>


-- 

Wayne Beaton

Director of Open Source Projects | Eclipse Foundation
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Eclipse IDE 2022-03 participation

[Hannes Wellmann]

For M2E version 1.20.1 was just released [1], which is a maintenance release for m2e 1.20.0 that only adds signatures for embedded *.jnilib files to fulfill the requirements of macOS-notarization.

 

The release entry for the project page is [2]. I have already created a Gerrit-change to update M2E's SimRel contribution.

Please consider it for the project page.

 

Do we have to start a IP Due Diligence Process for this release?

 

Thanks,

 

Hannes

 

 

[1] - https://www.eclipse.org/lists/m2e-dev/msg02479.html

[2] - https://projects.eclipse.org/projects/technology.m2e/releases/1.20.1
 

Gesendet: Mittwoch, 02. März 2022 um 19:59 Uhr
Von: "Wayne Beaton" 
An: "Cross project issues" 
Betreff: [cross-project-issues-dev] Eclipse IDE 2022-03 participation


Greetings folks.
 

I've created the release page for 2022-03. Please have a look to make sure that I have the information for your project captured correctly.

 

As usual, I had to make some guesses at the versions included. I did check the list against changes in the simrel repository and -- in some cases -- I created release records on behalf of the project teams based on what I saw (mostly when I saw a new minor version). Again, please make sure that I've correctly captured the release information for your project. Please make sure that you provide a short description in the corresponding release record.

 

If your project is contributing a new minor or major version and has not engaged in either a progress or release review in the past 12 months, please connect with EMO as soon as possible to schedule a release review.

 

Note that, even if your project does not require a review at this time, you are required to implement the IP Due Diligence Process for your release. That is -- even if you are contributing a service release, or have completed a release or progress review in the past 12 months -- you are still required to complete the IP Due Diligence Process for any content that is included in your release (this includes both project or third-party content). 

 

I've been experimenting with running the Eclipse Dash IP Log Tool on (more-or-less) randomly selected project repositories and it seems to function well. If you have an opportunity to try it, I would love to hear about your experience.

 

Wayne
 
--









Wayne Beaton

Director of Open Source Projects | Eclipse Foundation










___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev




 

 
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] Eclipse IDE 2022-03 participation

[Wayne Beaton]

Greetings folks.

I've created the release page for 2022-03
. Please have a look to make
sure that I have the information for your project captured correctly.

As usual, I had to make some guesses at the versions included. I did check
the list against changes in the simrel repository and -- in some cases -- I
created release records on behalf of the project teams based on what I saw
(mostly when I saw a new minor version). Again, please make sure that I've
correctly captured the release information for your project. Please make
sure that you provide a short description in the corresponding release
record.

If your project is contributing a new minor or major version and has not
engaged in either a progress or release review in the past 12 months,
please connect with EMO as soon as possible to schedule a release review.

Note that, even if your project does not require a review at this time, you
are required to implement the IP Due Diligence Process for your release.
That is -- even if you are contributing a service release, or have
completed a release or progress review in the past 12 months -- you are
still required to complete the IP Due Diligence Process for any content
that is included in your release (this includes both project or third-party
content).

I've been experimenting with running the Eclipse Dash IP Log Tool
 on (more-or-less) randomly
selected project repositories and it seems to function well. If you have an
opportunity to try it, I would love to hear about your experience.

Wayne

-- 

Wayne Beaton

Director of Open Source Projects | Eclipse Foundation
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev