Bugzilla – Full Text Bug Listing
| Summary: | [release] technology.stem 4.0.0 | ||
|---|---|---|---|
| Product: | Community | Reporter: | Wayne Beaton <wayne.beaton> |
| Component: | Proposals and Reviews | Assignee: | Eclipse Management Organization <emo> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | ahmadswaid, cydnie.smith, jhkauf, sedlund, sharon.corbett, wayne.beaton |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| URL: | https://projects.eclipse.org/projects/technology.stem/releases/4.0.0 | ||
| Whiteboard: | |||
|
Description
Wayne Beaton
What is the status of this release. Will the project team engage? There's more information regarding releases and reviews in the handbook. https://www.eclipse.org/projects/handbook/#release I reached out to James regarding release. He advised there were delays, and as a result I have changed release date to January 15. The project is missing LICENSE and NOTICE files in the repository root. Can somebody from the project team please add them? The Documentation template generator should be able to help [1] (note that it looks like it's currently not functioning; Webmaster has been advised). You should also add a CONTRIBUTING file with information on how to contribute. It's not apparent to me how I go about building org.eclipse.stem.git. I found a build.sh file, but it doesn't seem to work (it appears to depend on some system variables; do I need to set these before calling the script?) Some documentation would be helpful. I need the project to update to EPL-2.0. This will require that all file headers be updated. Is this something that's possible to complete in time for this release? I noticed that some of your generated content does not have file headers. Strictly, speaking we need all content to have copyright headers (unless it is particularly onerous or technically undesirable to do so). Is this something that you can add when you update to EPL-2.0? [1] https://www.eclipse.org/projects/tools/documentation.php?id=technology.stem Thank you Wayne, Our project leads and committers are discussing the remaining todos. I may have to slip our release date to be sure we get it all done but will know for sure in a week or so. Thank you very much for the detailed feedback. Updated the release record. Also added a pdf of the release review slides to our wiki and the release record now points to that url (as does our 'what's new page'. Re the IP Log, we did summit the IP Log for review and for PMC Approval. The CQ 18602. ISSUE: On the form I was unable to select in the combo box that this review is a release review (it did not have the release listed). Cydnie, the nearest available data for the IP review is Jan 16 so we may have to slip our release data another week or two.... There are no new issues and no third party contributions since the last IP review. Ahmad has merged the STEM 4 branch back to head and the Eclipse CI is now building from head. I have pushed your release date to Feb 6 to accommodate the IP review, and provide time to engage in the release review. I will amend as needed. Ahmad merged the STEM 4 Branch back to master branch All Java files have been updated with copyright date and epl-2 license https://www.eclipse.org/legal/epl-2.0/ TODO: Still need to get Developers doc in line with setup of dev environment fix ant build of earth science data plugins after repository reorg The IP Log is approved. (In reply to James Kaufman from comment #5) > ISSUE: > On the form I was unable to select in the combo box that this review is a > release review (it did not have the release listed). My best guess is that the date on the release might have been out of range. Is it possible that it had been set to January 2018 before we changed it? Thank you Wayne. It is possible I made an error entering the date that caused it to be out of range. Thank you very much for fixing it. I have scheduled the review to conclude on Feb 6. I declare this review successful! Please continue with your release. Thank you Cydnie :-) |