Bugzilla – Full Text Bug Listing
| Summary: | [release] technology.basyx 1.0.0 (JAVA) | ||
|---|---|---|---|
| Product: | Community | Reporter: | Maria Teresa Delgado <mariateresa.delgado> |
| Component: | Proposals and Reviews | Assignee: | Eclipse Management Organization <emo> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | frank.schnicke, marco.jahn, markus.damm, proposals-inbox, sharon.corbett, thomas.kuhn, wayne.beaton |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| URL: | https://projects.eclipse.org/projects/technology.basyx/releases/1.0.0-java | ||
| Whiteboard: | |||
|
Description
Maria Teresa Delgado
This bug will cover both releases of the Eclipse BaSyx project: - 1.0.0 (.NET) - 1.0.0 (JAVA) I've noticed that the project repository needs the CONTRIBUTING file in the root. Please add this as part of the release. You can use the Legal Documentation Generator tool available in the project PMI page (https://www.eclipse.org/projects/tools/documentation.php?id=technology.basyx) Let me know if you have any further questions. Many thanks for pointing this out. I added the CONTRIBUTING file to the master and release_1.0_java branches. AFAIK there are still some issues being worked linked to the .NET dependencies, and the project still has not requested PMC approval for the release materials. I'm pushing the release review date to April 7th. Please modify your release date accordingly and remember to ask for PMC approval. We intended to release the dotnet and java elements in separate releases. Is it possible to review both releases separately to speed up the process? Many thanks for pointing out the missing PMC approval request, I sent out a mail requesting it. The IP Log is approved. PMC Approval: https://www.eclipse.org/lists/technology-pmc/msg12368.html We have everything that we need, including the required one week of community review. I see no value in delaying the release. I declare this review successful. Please continue with your release. I'll update the dates on the release and review records. My apologies for the churn, Maria Teresa and I have crossed some wires. For completeness, the purpose of a release review is to ensure that the project is correctly implementing the Eclipse Foundation Development Process and Eclipse IP Policy prior to making a release. The release review focuses on the state of the project, not the state of any particular component/element. IMHO, we've proven that the Eclipse Basyx team doing this successfully. In particular, I believe that the project team is correctly tracking intellectual property. The success of this release review applies to the entire project, so you can release the Java, dotnet, and the rest of the elements of the project as frequently as you need for the next year. Please ensure that any new intellectual property that you add or third party content that you leverage is fully vetted before it is included in any release. I recall that we'd had some discussion regarding third party dependencies for the .NET. Third party content related to your .NET elements will need to be vetted like any other third party content before you can reference it from any release that contains that third party content. For the purposes of implementing the IP Policy, no vetting of the .NET platform itself is required (we consider the platform itself as an "exempt prerequisite"); we consider any content that is not the project code or the platform to be "third-party". That is, we do need the project team to engage in the IP Due Diligence Process for all third-party content that sits between the project code and the .NET platform. If you need assistance, please connect with EMO. |