Bug 568969 - [release] iot.embed-cdt 6.0.0
Summary: [release] iot.embed-cdt 6.0.0
Status: RESOLVED FIXED
Alias: None
Product: Community
Classification: Eclipse Foundation
Component: Proposals and Reviews (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Eclipse Management Organization CLA
QA Contact:
URL: https://projects.eclipse.org/projects...
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2020-11-19 15:40 EST by Wayne Beaton CLA
Modified: 2020-12-09 19:41 EST (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Wayne Beaton CLA 2020-11-19 15:40:00 EST
We'll use this bug to track the release

We require IP Team approval of the IP Log.

We require PMC approval of the release and review materials.

There's help regarding releases in the handbook.

https://www.eclipse.org/projects/handbook/#release
Comment 1 Wayne Beaton CLA 2020-11-19 15:44:41 EST
NOTE: this will be combined release/graduation review.
Comment 2 Wayne Beaton CLA 2020-11-19 15:46:43 EST
(In reply to Wayne Beaton from comment #1)
> NOTE: this will be combined release/graduation review.

Liviu, I see that you've already marked this as a graduation review. But you've also marked it as "restructuring". What are you planning to restructure? (Restructuring reviews are for changing the nature of a project, e.g., changing scope or moving significant bits of code from one project to another)
Comment 3 Liviu Ionescu CLA 2020-11-19 16:07:45 EST
Alexander is working now on splitting the plug-ins into core/ui/branding separate plug-ins.

I considered this to match the "restructuring" tag, but if splitting plug-ins within the same project does not match this, we can remove this tag.
Comment 4 Wayne Beaton CLA 2020-11-19 22:52:03 EST
> I considered this to match the "restructuring" tag, but if splitting
> plug-ins within the same project does not match this, we can remove this tag.

Removed.

For future reference, our primary concern when it comes to a restructuring review is to give the membership an opportunity to weigh in when we're moving intellectual property between projects. Restructuring within a project is an internal matter (just make sure that you're communicating implications of changes with your adopters).
Comment 5 Wayne Beaton CLA 2020-12-01 14:55:58 EST
I've scheduled the review to conclude on December 9/2020.
Comment 6 Wayne Beaton CLA 2020-12-07 12:31:12 EST
The IP Log is approved.
Comment 7 Wayne Beaton CLA 2020-12-09 09:55:04 EST
We're still waiting on PMC approval. Once we have this, the review should be considered successful. That is, don't wait to hear it from me; when you see the +1 from the PMC, you're good-to-go.
Comment 8 Liviu Ionescu CLA 2020-12-09 10:13:19 EST
> when you see the +1 from the PMC, you're good-to-go.

To meet the general Eclipse releases schedule requirements, the "Embedded CDT plug-ins v6.0.0" were already contributed to SimRel, and EPP was updated to create the "Eclipse IDE for Embedded C/C++ Developers" binaries.
Comment 9 Wayne Beaton CLA 2020-12-09 10:24:27 EST
(In reply to Liviu Ionescu from comment #8)
> > when you see the +1 from the PMC, you're good-to-go.
> 
> To meet the general Eclipse releases schedule requirements, the "Embedded
> CDT plug-ins v6.0.0" were already contributed to SimRel, and EPP was updated
> to create the "Eclipse IDE for Embedded C/C++ Developers" binaries.

This is standard practice.

Strictly speaking, you've contributed a "release candidate" to the simultaneous release (the binaries that get built out of the simultaneous release repository are also release candidates). That release candidate will automagically become the "GA" release bits on December 16 when the simultaneous release goes live.

Theoretically, the PMC could say no and we'll have to unwind the project bits out of the simultaneous release builds, but this is extremely unlikely (unprecedented). If we thought that there was any real risk that the PMC might say no, we'd have started mitigation weeks or months ago.
Comment 10 Jonah Graham CLA 2020-12-09 10:39:58 EST
Jens has sent +1 for the release now.
Comment 11 Liviu Ionescu CLA 2020-12-09 12:02:37 EST
> Strictly speaking, you've contributed a "release candidate"

Right. Thank you for the clarification.

This also matches my workflow. All release candidates are published in folders like '/embed-cdt/release-candidates/6.0.0-202012080907', and the final release will be published in '/embed-cdt/releases/6.0.0' at release day.
Comment 12 Liviu Ionescu CLA 2020-12-09 12:20:54 EST
> Theoretically, the PMC could say no and we'll have to unwind the
> project bits out of the simultaneous release builds, but this is
> extremely unlikely (unprecedented).

First let me say that from my point of view the reviews should be a great opportunity to get additional feedback and I generally value any suggestion/critique that may help improve the quality and usability of the project.

So, if the review would reveal a major problem, I'd be the first to ask to unwind it from SimRel.

However, if the review would fail due to unrealistic bureaucratic procedures (like for example "one year of incubation phase is not enough") and the project would be kicked out or negatively affected in any way, that would most probably trigger retiring the project from the Eclipse Foundation.
Comment 13 Wayne Beaton CLA 2020-12-09 18:46:48 EST
PMC Approval: https://www.eclipse.org/lists/iot-pmc/msg07961.html

I declare this review successful. I have marked the project as "mature". Please continue with your release.
Comment 14 Liviu Ionescu CLA 2020-12-09 19:41:18 EST
Thank you, Wayne. Highly appreciated.