Bugzilla – Full Text Bug Listing
| Summary: | [release] technology.scout 11.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: | claudio.guglielmo, mariateresa.delgado, proposals-inbox, sharon.corbett |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| URL: | https://projects.eclipse.org/projects/technology.scout/releases/11.0.0 | ||
| Whiteboard: | |||
|
Description
Wayne Beaton
What is the state of the master branch? The master branch looks completely bogus (it breaks looking for a J2SE-1.5 runtime). I had to dig into the build configurations on Jenkins to sort out how to build. A low bar for courting community engagement is to make the project easily buildable. Is there something that you can at least add in the README or CONTRIBUTING file to give folks a fighting chance of building the project code? I see from Jenkins that you're building individual projects. What's the role of the "aggregator" repository? (it also appears to pull master) We don't actively maintain the scout aggregator anymore because it is only needed for some very old builds. The master branch is not used at all since we work on dedicated release branches (e.g. releases/11.0). I discussed this topic with some team members and we decided to either delete the master branch or adjust the old jobs to make them clone the individual projects so that we will eventually be able to remove the aggregator. Regarding README and CCONTRIBUTING files: You will find them in the individual projects. https://git.eclipse.org/c/scout/org.eclipse.scout.rt.git/tree/?h=releases/11.0 https://git.eclipse.org/c/scout/org.eclipse.scout.sdk.git/?h=releases%2F11.0 It looks like it was the aggregator that tripped me up and got me stuck in the master branch. I see now that it's labeled "Old Scout Aggregator (only used for..."; I must have missed this yesterday. It appears that the org.eclipse.scout.rt repository is configured with HEAD pointing at your 10.0 branch, which means that just cloning that repository and building results in a clean build and happy potential contributors. You had not missed it, that description is brand new ;-) https://git.eclipse.org/r/c/scout/org.eclipse.scout-aggregator/+/176818 We also deleted the master branch: https://bugs.eclipse.org/bugs/show_bug.cgi?id=571451 The IP Log is approved. I have the review scheduled to conclude on March 17/2021. I need PMC approval before I can declare success. https://www.eclipse.org/projects/handbook/#release-review I requested an approval last week and sent a reminder to the technology-pmc mailing list on Wednesday. I guess we just have to be patient? (In reply to Claudio Guglielmo from comment #6) > I requested an approval last week and sent a reminder to the technology-pmc > mailing list on Wednesday. I guess we just have to be patient? And persistent. A polite reminder might be in order. I just checked with a colleague and he has not received any email from me on the technology-pmc mailing list. So my mails have probably never arrived, likely because I used the wrong email account to send them. My company changed the email addresses a while ago but I had never switched to the new email for my eclipse account because the old one still works. I changed my account and sent the email again (twice, unfortunately, because my colleague still has not received any email from me, even though he is subscribed to technology-pmc) and now got a +1 from Gunnar. I declare this review successful! Please continue with your release. |