eclipse-jdt / eclipse-jdt/eclipse.jdt.core
BETA_JAVAX branch development is intransparent
- Dominant language
- Java
- Stars
- 237
- Forks
- 195
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 47
Description
One thing that always wondered me: why all the "next Java support" development that happened on BETA_JAVAX branches is so intransparent?
With transparency I mean: there are obviously some tests & builds running, but nowhere is mentioned where they are.
There is no SDK build that includes that JDT patch, so one can't even easily smoke test whatever was implemented on the branch, or verify how some Java feature looks like in next Eclipse.
At least minimal things I wish we should have would be wiki page (can be on github) with
1) link to the latest SDK binaries produced containing latest JDT branch state
2) link to latest SDK test results with new JDT branch
3) schedule of the builds (if they are automatically scheduled) or link how to manually trigger a build
4) Link to the main issue for the next Java support in JDT
@akurtakov : if we want continue to go forward with "better" JDT project culture, faster JDT release cycles etc, this is one of the points we should address.
E.g. after merging https://github.com/eclipse-jdt/eclipse.jdt.core/pull/593 I would like to see how the overall SDK build/test results look like, and if that introduces new issues already.
Contributor guide
Assessment
This issue has not been assessed yet.