You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are late for performing the yearly release review, to insure that we're following the IP process and that everything is allright.
I have submitted the up-to-date IP Log for review: here (committers only have access, I think). I set the due date to March 18th, since I do not think this needs be tied to a release (we do this once a year normally).
According to the Release Review page above, there are 3 things to do:
1. PMC Approval (Can occur in parallel with, prior to, and after, the IP clearance);
2. IP Log Approval This is essential, and no release review can proceed without it!; and
3. Review document.
I think #1 is a formality once everything else is wrapped-up. #2 is submitted and we'll see about approval and whether we need to take some actions to secure it. #3 might be a bit more work - basically make sure our project documentation is up-to-date. This includes being up-to-date regarding both disclosed and undisclosed security issues. I think the list contains some items that are N/A for us on GitHub, like having a milestone build available on download.eclipse.org, so we'll have to use judgement.
The text was updated successfully, but these errors were encountered:
We are late for performing the yearly release review, to insure that we're following the IP process and that everything is allright.
I have submitted the up-to-date
IP Log
for review: here (committers only have access, I think). I set the due date to March 18th, since I do not think this needs be tied to a release (we do this once a year normally).According to the Release Review page above, there are 3 things to do:
I think #1 is a formality once everything else is wrapped-up. #2 is submitted and we'll see about approval and whether we need to take some actions to secure it. #3 might be a bit more work - basically make sure our project documentation is up-to-date. This includes being up-to-date regarding both disclosed and undisclosed security issues. I think the list contains some items that are N/A for us on GitHub, like having a milestone build available on download.eclipse.org, so we'll have to use judgement.
The text was updated successfully, but these errors were encountered: