Re: [embed-cdt-dev] 2020-12 release schedule

[Jonah Graham <jonah@xxxxxxxxxxxxxxxx>]

Embed-cdt contains third-party code used as templates for end users. This third-party code needs to be vetted so that it can be distributed. If and when that third party code is updated, CQs for it need to be filed. The initial review is going to take longer (especially as this kind of use case is uncommon), but generally subsequent reviews for new versions are much quicker.

I think that means the filed CQs (that haven't been approved) can be withdrawn and new CQs for the newer code can be submitted. However, Wayne may say that the CQs can be updated, especially as the current ones have useful history of the discussion.

@Wayne Can you advise please? CQ 21826 is an example with the org.eclipse.embedcdt.templates.stm plug-in history showing where it was updated to newer versions.

Thank you!

Jonah

On Sun, 15 Nov 2020 at 05:53, Liviu Ionescu <ilg@xxxxxxxxxx> wrote:

> On 15 Nov 2020, at 04:25, Jonah Graham <jonah@xxxxxxxxxxxxxxxx> wrote:

> I think you should schedule the release for the 2020-12 SimRel release date, which is Dec 16. The review can be scheduled (IIRC) to conclude on Dec 2nd, giving us 18 days to finish everything, and enough time to remedy anything before the final contribution date.

I updated the release date to Dec 16, and the review date to Dec 2nd.

> - send an email to emo@xxxxxxxxxxx to make it public (already done perhaps?)

Done

> - send email to iot PMC for their approval

Done

> - submit IP log for review https://projects.eclipse.org/projects/iot.embed-cdt/releases/6.0.0/iplog/preview - I see that there are 6 CQs that still need resolving. What I believe Wayne meant is that by having the CQs tied to a release their review priority is increased to make sure release is on time.
...
> Have new CQs been filed for this new (updated) third party content? The current CQ (https://dev.eclipse.org/ipzilla/show_bug.cgi?id=21826) is from March.

You mean to re-submit all 6, as I did initially?

(I hope I still have the scripts to create the archives...)

> The rule is no major API changes after M3 (IIRC) which would be 24 Nov (actually 25 Nov for the +3 day). However an exception can be made with a short email to cross-project-issues-dev. The purpose of the no API change is so that API consumers have time to adapt. Of course as of now there are no API consumers in simrel for iot.embed-cdt. This means that the hard deadline is RC2+3 date, or Dec 9.

Ok, that's good.

I'll then submit to M3 whatever is available by Nov 24, and have some time to test. If necessary, we'll fix issues and resubmit at RC1/RC2.

> This is our first reviewed release for embed-cdt, there is actually quite a lot to review - see the checklist on https://wiki.eclipse.org/Development_Resources/HOWTO/Release_Reviews#Checklist
>
> Only one release review per year is required. However all CQs need to be approved before release.

Ok, if I have to re-submit all CQs, that's it, I'll try to find out how I did it last time and do it the same...

Thank you,

Liviu




_______________________________________________
embed-cdt-dev mailing list
embed-cdt-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/embed-cdt-dev