Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Eclipse/PMC"
< Eclipse
(June 12 meeting notes) |
|||
| (73 intermediate revisions by 6 users not shown) | |||
| Line 11: | Line 11: | ||
= Meeting Minutes = | = Meeting Minutes = | ||
| − | ''' | + | '''June 12, 2018''' - McQ, Alex, Tom, Lars |
| − | * | + | * RC4a looks good; hidpi fix is in place |
| − | ** | + | ** no plans for further builds at this point |
| − | + | ||
| − | + | '''June 05, 2018''' - McQ, Alex, Tom, Dani, Lars | |
| − | ''' | + | * Dani: |
| − | * | + | ** Image limit for help should be increased? -> Not covered in the call |
| − | * | + | ** Will most likely not be able to join the next call |
| − | ** | + | * Alex: |
| − | ** | + | ** Support only last LTS version of Linux? |
| − | ** | + | *** Agreement to drop old LTS versions for 4.9 but not to change the target environment for 4.8 |
| − | *** | + | ** Dropping big Endian -> we all agreed to drop it, MQ found the email to cross, so we can remove it |
| − | *** | + | * Lars: |
| − | ** | + | ** Update to EPL 2.0? |
| − | * Dani | + | *** change of about.html is trivial |
| − | ** | + | *** requires version updates of MANIFEST.MF and pom.xml |
| − | * | + | *** Script for source update look good, Lars checked manually lots of files |
| − | * | + | *** Coordindate with Jay or Noopur for the JDT UI update |
| + | *** Dani suggested to announce such work via the mailing list so that everyone is aware of the work | ||
| + | |||
| + | ** Only one N&N per release? -> Agreed to have one document per release | ||
| + | ** Do we get a name for Photon+1 -> Dani: Our SDK is called 4.9, splash screen will only be month year, planning counsil still discussing | ||
| + | ** Include Tips and Tricks in the SDK -> Not covered in the call | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | '''May 29, 2018''' - Alex, Tom, Dani | |
| − | ''' | + | * Dani: |
| − | * Dani: | + | ** Uploaded IP log |
| − | * | + | ** Working on issue with IP log: looks like a CQ is missing for com.google.code.atinject.tck |
| − | * | + | ** Finalized Photon plan |
| + | ** Sent Release Review material for approval to PMC mailing list | ||
| + | ** RC3 looks good so far | ||
| − | |||
| − | ''' | + | '''May 22, 2018''' - Alex, Tom, McQ, Dani |
| − | * | + | * EPL 2.0 |
| − | * | + | ** Still working with foundation on whether we can gradually move to 2.0 |
| − | ** | + | * Will we be supporting updates from release to release in the new 3 month release cycle? |
| − | * | + | ** Yes, unless we explicitly indicate otherwise. |
| − | * Alex | + | ** To simplify this, we should have a "latest" update site |
| − | ** Dani | + | ** We need to make this simpler for users, but not get in the way of the EPP, OOMF, etc. |
| + | ** Alex to write this up in more detail | ||
| + | ** Dani reminded us that there had been a previous discussion in the planning council | ||
| + | * Project leads have updated Photon plans | ||
| + | ** Dani will be updating the overall plan; PMC to comment on bug 529640 | ||
| + | * Dani also working on release review and IP log | ||
| + | ** PMC members to approve once it's ready | ||
| + | * As previously discussed our first milestone will be called "M2" | ||
| − | |||
| − | |||
| − | ''' | + | '''May 15, 2018''' - Alex, Tom, McQ, Lars, Dani |
| − | * project | + | * GDPR |
| − | * | + | ** audit did not report any issues on our project pages |
| − | * | + | * Opening development for 4.9 |
| + | ** Will branch RC2 and update master with required Releng work | ||
| + | ** master will be open after RC3 | ||
| + | * EPL 2.0 | ||
| + | ** No plans to do anything for 4.8 | ||
| + | ** Lars will look into it | ||
| + | ** Ideally we gradually move to 2.0 | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | ''' | + | '''May 8, 2018''' - Dani, Alex, Tom, McQ |
| + | * GDPR | ||
| + | ** Eclipse Project collects no information from the users on the project websites | ||
| + | ** The Error Reporting tool, might be impacted | ||
| + | ** Also possibly bugzilla <-- Do we need to delete bugs older than some retention period? | ||
| + | ** Impossible to remove emails from all git repos (because of cloning) | ||
| + | ** We need to be sure to respond to requests from the foundation | ||
| + | * Jetty | ||
| + | ** 9.4.10 is in latest build, and help system is working | ||
| + | ** they made the dependencies that were problematic optional | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | '''May 1, 2018''' - cancelled due to public holiday in most Europe | |
| − | ''' | + | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | * | + | '''April 24, 2018''' - Dani, Lars, Alex, Tom |
| − | ** | + | * Target environments |
| − | ** | + | ** We will keep Java 8 and 10 and remove java 9 from the list |
| − | ** | + | ** remove JVMs as soon as they run out of support from target environments - AGREED |
| − | ** Dani to | + | * javax.annotation |
| + | ** Version shipped is quite old, should we update it to newer version | ||
| + | ** Update to latest standalone release to be tried | ||
| + | ** Alex to try to drive this through | ||
| + | * Notify cross project about removal of ee modules from the JVM | ||
| + | ** People don't follow Java 11 work so will probably be surprised when things start to fail so we better try to spread the information | ||
| + | ** Dani will send a link to the JEP containing detailed information | ||
| + | * Contribution guidelines | ||
| + | ** Do not open bugs for simple changes and cleanups | ||
| + | ** Actual bug fixes to be split from cleanups in separate patches so the bug commit is straight on the topic | ||
| + | ** Dani will update the wiki | ||
| + | * Cancel May 1st call - public holiday in Europe | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | '''April 17, 2018''' - Dani, Alex, McQ | |
| − | ''' | + | * On Java 11... |
| − | * | + | ** We are actually shipping the javax annotation support |
| − | ** | + | ** Java 11 is working in 4.8, but isn't in 4.7.x |
| − | * | + | *** Tom Watson is investigating why it is not working 4.7.x |
| − | ** | + | |
| − | + | ||
| − | + | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | '''April 10, 2018''' - Tom, Dani, Lars, Alex | |
| − | ''' | + | * Discussed {{bug|533390}}: Eclipse does not launch with Java 11 |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | * | + | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | '''April 3, 2018''' - Tom, Dani, Mcq, Lars | |
| − | ''' | + | * 4.7.3a update |
| − | * | + | ** Delivered RC2 on Saturday, so we could fix some badness in handling Java 10 "var" support (tl;dr: rename appeared to allow you to affect "var" as if it were a type (but would not have modified the code)) |
| − | ** | + | ** Currently think we're done |
| − | *** | + | * Naming milestones |
| − | ** | + | ** As previously discussed, we will contribute the most recent I-build to the release train for the 3-week "M1". |
| + | ** We will call our first milestone (at the 6-week point) M2 so that it aligns with the release train naming. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | '''March 27, 2018''' - Tom, Dani, Mcq, Lars, Alex | |
| − | ''' | + | * Java packages for configured Java in workspace |
| − | * | + | ** Equinox no longer provides hard-coded information about execution environments. In the past this information was used at runtime for describing the running execution environment within the OSGi Framework. Other usecases outside the Framework started uses the Java profile data from Equinox. Equinox no longer has any need for the hard-coded information so no longer provides it. |
| − | ** | + | ** JDT and PDE have come to depend on the internal resources of the framework to get hard-coded information about execution environments |
| − | ** | + | ** JDT and PDE need to have a common way to figure out the available packages for Java versions >= Java 9 |
| − | * | + | ** See [https://bugs.eclipse.org/bugs/show_bug.cgi?id=531642 531642] [https://bugs.eclipse.org/bugs/show_bug.cgi?id=532773 532773] |
| + | * SWT clean-up | ||
| + | ** Lars reviewed the removal of Windows XP. Built binaries locally on Windows. | ||
| + | ** Found a form data issue deleted some code that was still used | ||
| + | ** Tom - Unit tests didn’t catch the issue. Concerning? | ||
| − | + | --> Update from Lars after the call: Later testing did show that this is a bug already existing in Eclipse. 4.7 and master and not related to the patch | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ** Lars did review and test | |
| − | + | ** Dani - put all the code in the branch and produce a build and ask windows community to test it | |
| − | * | + | ** Mcq - thinks it is a good idea |
| − | ** | + | ** Dani - create an official build for testing, not out of master with normal builds |
| − | ** | + | ** Lars - what is the risk of putting in master |
| − | * Dani | + | ** Dani - can do the build right away pre-CQ review approval. Allows for more quick testing. |
| − | ** | + | ** Alex, no need for a branch, can be a developer build we publish. Alex will ask Leo to do this. |
| − | ** | + | * Jetty version |
| − | * | + | ** Jetty added non-optional dependencies on service-loader |
| − | * | + | ** Dani - got reverted, but old versions still caused Gerrit build issue |
| + | ** We don’t need the service-loader for our usage of jetty | ||
| + | ** jetty may be making a hard requirement on an implementation of server-loader (Aries spi-fly) | ||
| + | ** Can we move help off jetty? Will be a major undertaking. Should figure out what it would me to do so. Currently no interested contributer has stepped up to do the work to figure out what this would mean. | ||
| + | ** Equinox will still need jetty for the http service implementation. Perhaps things are more simple if this is an Equinox only dependency. Only pull in jetty if the http service implementation is needed and then pull in all of jetty and its dependencies. | ||
| + | ** No current plans or interested contributors for providing our own service-loader implementation. | ||
| + | ** Our build should start resolving the capabilities are requirements which would catch issues like this early in the build. | ||
| + | ** Alex - can we move latest tycho to get the capability/requirements meta-data. No objections? Alex will move forward. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | '''March 20, 2018''' - Dani, McQ, Tom, Lars, Alex | |
| − | ''' | + | * Dani: The IBM SWT team considers the Windows XP removal too risky and in addition has no capacity to look at that big change. Fine if someone else looks at the removal. The type changes will have to wait after Photon (too risky). Lars will ask Conrad and Alex will also look at the patches. |
| − | * Dani: | + | * Databinding generification should be done early 4.9, too late for Photon. |
| − | + | * Dani: Eclipse support for Java 10 will be merged to the official branches starting Wednesday. A Marketplace entry for 4.7.3 will be made available once 4.7.3 is released. The first official release with Java 10 support is 4.7.3a scheduled for April 11. | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | * | + | |
| − | + | ||
| − | * Dani: | + | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | '''March 13, 2018''' - Dani, McQ, Tom | |
| − | ''' | + | * Alex had troubles to join; Lars still in vacation |
| − | * Alex | + | * Dani: in the new release process we need to downgrade some milestones to "checkpoints" where we only deliver the bits |
| − | + | ** ACTION ITEM: Dani to start the discussion with the PMC via e-mail and then inform cross-project | |
| − | + | ||
| − | * | + | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | ** | + | |
| − | + | ||
| − | + | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | '''March 6, 2018''' - McQ, Tom, Alex | |
| − | ''' | + | * Short call without any interesting topics |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | '''February 27, 2018''' - Lars, Dani, McQ, Tom, Alex | |
| − | + | * JDT support for new Java releases | |
| − | + | ** McQ: With current change rate and OpenJDK process we can not promise Zero day compatibility but rather release as soon as possible | |
| + | ** Dani: effort to try convincing Oracle to tell the features a release earlier and get easier access to OpenJDK community | ||
| + | * Dropping XP support | ||
| + | ** Dani: no objection to drop it, the question is whether to do it for Photon or delay it for next release | ||
| + | ** Mail to be posted to cross project by Dani to gather feedback | ||
| + | ** Alex: 1 week for gathering input on cross-project - '''AGREED''' | ||
| + | ** If noone speaks up with reasonable reason to keep support - preapproved by Dani, Lars and Alex | ||
| + | ** To be formally voted after the mail to cross-project | ||
| + | * Release names | ||
| + | ** Version only, release names are irrelevant from Eclipse TLP side - '''AGREED''' | ||
| + | * Inactive committers pruning | ||
| + | ** Lars: no access to committer emails so sending just to the mailing list | ||
| + | ** Wait 2 months for reply before action | ||
| + | ** McQ: ask foundation to send direct mails on behalf of the project, if foundation is not fine - remove committers directly | ||
| + | ** Alex: only public replies to the mailing list are accepted so people wanting to remain committers at least follow the mailing list | ||
| + | * Tip of the day - | ||
| + | ** Lars: CQ approved, to be merged today/tomorrow | ||
| + | ** Alex: we should have it part of the build and part of the p2 repo for easy testing | ||
| + | ** Dani: unclear APIs to be removed and to be simplified so we don't end up maintaining useless parts | ||
| + | * GTK 2 vs. 4 | ||
| + | ** Alex: Gtk 4 release aiming at late 2018, it's big change in drawing so conflicts with Gtk 2 badly | ||
| + | ** Alex: Gtk 2 support to be removed in future one of the next 2 releases, whether Sep or Dec to be discussed later in the Photon release train | ||
| + | ** Alex: mail to cross project list around Photon M7 or RC when more information on both Gtk 4 release plans and SWT bugs will be known | ||
| + | ** McQ: what is our statement on supported Gtk version? | ||
| + | ** Alex: Statement should be: Once SWT switches to latest Gtk version as default, support for previous versions goes into deep maintenance mode but will kept until it starts hurting new development and support for the default version at which point to be removed. | ||
| + | ** To be discussed further. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | '''February 20, 2018''' - Lars, Dani, McQ, Tom | |
| − | ''' | + | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | * Dani: Update on 4.7 RC3 | |
| − | ''' | + | * Lars: Can we drop Windows XP support? |
| − | * Dani: | + | ** Lars: Big contribution comes in (https://bugs.eclipse.org/bugs/show_bug.cgi?id=531097), dropping XP support might be a good motiviation to contribute more also to other people. Removing lots of code including the version checks will also result in a cleaner code base for maintenance and might improve performance. |
| − | * | + | ** Dani: IBM investigate if they officially drop XP |
| − | * Dani: | + | ** Tom: Do we need support XP with the latest Eclipse version? |
| − | * Dani: | + | --> Pending on the answer of the IBM team, will be discussed in next weeks call |
| − | * Lars: ''' | + | * Tom: OSGI CQs updated and approved for OSGi Service Platform 7.0 version |
| − | * | + | |
| − | ** | + | |
| − | ** | + | '''February 6, 2018''' - Lars, Dani, McQ |
| − | ** | + | * Lars: Can we mark MInput and MInputPart for deletion ({{bug|509868}})? |
| − | ** | + | ** Dani: Before approving to mark them for deletion, someone has to investigate how much work needs to be done to do it. Both have over 50 references. |
| − | ** | + | *** McQ agrees |
| − | * | + | * Dani: [https://dev.eclipse.org/mhonarc/lists/ui-best-practices-working-group/msg00743.html Topic on ui-best-practices-working-group list]: Replace "..." with an ellipses Unicode character |
| − | ** | + | ** Looks good on Mac and is actually used by Mac OS, but less good on Windows. No info regarding Linux at this time |
| − | ** | + | ** McQ: |
| − | + | *** Mac OS UI guidelines specify to use the ellipses character | |
| − | ** | + | *** SWT could do the right thing depending on the platform |
| − | *** | + | * Lars: view menu, minimize and maximize buttons look bad to him. Would like to replace the view menu with ellipses |
| − | **** | + | ** Dani: Would have to change all three together. View menu is always there and not indicating an overflow |
| − | *** ''' | + | ** McQ: Windows 10 also uses a triangle, but upwards. Current view menu is used and familiar to users for at least more than 10 years. |
| − | *** | + | ** Lars to file a bug report and send the bug number to the PMC |
| − | *** | + | * McQ: Should discuss in one of the next meetings how JDT can handle the new release cadence for Java |
| + | ** Dani: We will see how it goes with Java 11 (18.3) | ||
| + | * Dani: How will we name the milestones in our new new release scheme? | ||
| + | ** Consensus to start with M1 after each release. | ||
| + | ** Up to planning council to decide the release naming convention. Lars: Would prefer year/month | ||
| + | |||
| + | |||
| + | '''January 30, 2018''' - Alex, Lars, Dani, Tom | ||
| + | * General Updates (Dani) | ||
| + | ** Shipped M5, still working some p2 issues | ||
| + | ** RC1 for Neon.3 next week, may need API changes after the freeze for junit 5 support updates | ||
| + | ** Discussion about the incubation for Java. Ongoing thread in jdt-dev list https://dev.eclipse.org/mhonarc/lists/jdt-dev/msg00964.html. The incubation features will be part of the release specification which implies they need to be implemented to be compliant. Spend time putting them into a release only to pull out later if they don’t finalize. Not clear there are tests added to the TCK. Alex asks if this effects us for Java 10, no not for Java 10. Java 10 only has local type reference, not huge delta of function from Java 9. No incubation in Java 10. But incubation may affect us for Java 11. | ||
| + | * Info about infrastructure (Alex) | ||
| + | ** Foundation push to move to Jenkins. Releng has moved, uncovered issues with rest API and token exchange … disabled for now for Jenkins. Issue is being worked but only can be fixed once all is moved to Jenkins. | ||
| + | ** Platform HIPP moving to Jenkins tomorrow. Will be some downtime, should be less than an hour or so. May cause several issue. Issues in non-standard jobs with multiple repos etc. For Gerrit verifications should be fine. Let Alex know if there are issues. Alex to send a note when the migration occurs. | ||
| + | ** p2 issue is real. Other issues are pressing (infrastucture/build). Todor has a bug that he should be looking at. Not something happening in the past, but now the capabilities are being resolved. Issues happened with a hand crafted p2.inf file. Hopefully will scope down the p2.inf files. Alex to drive to determine if a respin is needed. | ||
| + | ** Need to monitor the p2 issue, determine how many are broken. Cannot just break 100s of folks without serious consideration. Why not revert? Alex says it is not an option and we should do everything possible to fix. | ||
| + | ** Lars asks about nominating more committers, perhaps that were rejected in the past. Now the Eclipse PMC can overlook the nomination process. Work with existing contributors showing interest and look for opportunities to sponsor them for committership. | ||
| + | * Tip of the day (Clippy) | ||
| + | ** See [https://dev.eclipse.org/mhonarc/lists/platform-ui-dev/msg08006.html Tips Framework] | ||
| + | ** Tip of the Day or (Clippy) in coming contribution … looking for integration M6? | ||
| + | ** Lars thinks it is worth it. Dani disables such things by default, and also Lars. Alex find the function interesting. Others are also reviewing the patch. | ||
| + | ** Lars is moving forward with it. If it is very easy to disable and is stable on all platforms then it should be good. | ||
| + | ** Is there a concern about a solution that requires network … it doesn’t appear to be a concern. | ||
| + | |||
| + | |||
| + | '''January 16, 2018''' - Alex, Lars, Dani, Tom | ||
| + | * Native builds at eclipse.org status (Lars): | ||
| + | ** Dani: swt is done for some time already | ||
| + | ** Dani: launchers after M5 is released to prevent breakage | ||
| + | * GTK launcher changes (Alex): | ||
| + | ** Changes to not rely on X11 atoms but on dbus ready for review | ||
| + | ** Linux only as no other GTK platforms are currently built | ||
| + | * Equinox CQs (Tom): | ||
| + | ** P2 capabilities patch from Todor and felix.scr update | ||
| + | ** Slow process risking M5 | ||
| + | ** Alex: Ping Sharon asking for speedup if possible | ||
| + | * Updates from Dani: | ||
| + | ** Photon plan update - BREE to be part of the build info | ||
| + | ** End game - Oxygen.3 and M5 - send to the list | ||
| + | ** Running tests against Java 9 | ||
| + | * Java 10 eclipse release (Dani): | ||
| + | ** Oxygen.3a or marketplace feature only - Agreement for oxygen.3a | ||
| + | ** Dani: Local Variable type inference support in a branch | ||
| + | ** Future releases - to be aligned with JVM releases if they prove to release on time | ||
| + | * BREE updates recomendations | ||
| + | ** Dani: There are reasons to stay on older BREE | ||
| + | ** Alex: ease of getting jvm is the main concern here - if a contributor can't get jvm at that version easily we can't call it supported | ||
| + | |||
| + | |||
| + | '''Januar 09, 2018''' - McQ, Alex, Lars, Dani | ||
| + | * Updates from Dani: | ||
| + | ** Ian Skerrett is leaving the Eclipse foundation | ||
| + | ** Dani got nominated as committer representive | ||
| + | * Planning council update | ||
| + | ** Dani: low participation in the last calls | ||
| + | ** Dani will talk with Melanie about it | ||
| + | ** Input required for the planning council for the API and feature freezes for the platform | ||
| + | * API and feature freeze policy in platform | ||
| + | *** Alex: API and feature freeze in platform should be RC1, except breaking API which should be done in milestone build | ||
| + | *** everyone agrees to Alex suggestion-> agreed | ||
| + | * Alex: SWT linux currently uses X-Windows specific API, which does not work on Wayland. This will be moved to a DBUS API to open file and open URL | ||
| + | * Dani: Plan update, biggest change is for the component plan | ||
| + | ** Equinox plan has been added | ||
| + | ** Manual generated BREE list has been dropped from the plan. This list is still automatically generated for every I-Build | ||
| + | * Launcher and natives build move from IBM to the foundation still in progress | ||
| + | ** ({{bug|528230}}) Build FileSystem native component on Eclipse Foundation Infra | ||
| + | ** ({{bug|528230}}) Build launcher on Eclipse Foundation Infra | ||
= Archive = | = Archive = | ||
| + | * [[Eclipse/PMC/Minutes 2017 | Archive of Meeting Minutes from 2017]] | ||
* [[Eclipse/PMC/Minutes 2016 | Archive of Meeting Minutes from 2016]] | * [[Eclipse/PMC/Minutes 2016 | Archive of Meeting Minutes from 2016]] | ||
* [[Eclipse/PMC/Minutes 2015 | Archive of Meeting Minutes from 2015]] | * [[Eclipse/PMC/Minutes 2015 | Archive of Meeting Minutes from 2015]] | ||
Revision as of 11:15, 12 June 2018
Documents
Some documents written and/or used by the PMC:
Meeting Schedule
The Eclipse Project PMC has a weekly phone meeting every Tuesday at 11.00am EST.
Meeting Minutes
June 12, 2018 - McQ, Alex, Tom, Lars
- RC4a looks good; hidpi fix is in place
- no plans for further builds at this point
June 05, 2018 - McQ, Alex, Tom, Dani, Lars
- Dani:
- Image limit for help should be increased? -> Not covered in the call
- Will most likely not be able to join the next call
- Alex:
- Support only last LTS version of Linux?
- Agreement to drop old LTS versions for 4.9 but not to change the target environment for 4.8
- Dropping big Endian -> we all agreed to drop it, MQ found the email to cross, so we can remove it
- Support only last LTS version of Linux?
- Lars:
- Update to EPL 2.0?
- change of about.html is trivial
- requires version updates of MANIFEST.MF and pom.xml
- Script for source update look good, Lars checked manually lots of files
- Coordindate with Jay or Noopur for the JDT UI update
- Dani suggested to announce such work via the mailing list so that everyone is aware of the work
- Update to EPL 2.0?
- Only one N&N per release? -> Agreed to have one document per release
- Do we get a name for Photon+1 -> Dani: Our SDK is called 4.9, splash screen will only be month year, planning counsil still discussing
- Include Tips and Tricks in the SDK -> Not covered in the call
May 29, 2018 - Alex, Tom, Dani
- Dani:
- Uploaded IP log
- Working on issue with IP log: looks like a CQ is missing for com.google.code.atinject.tck
- Finalized Photon plan
- Sent Release Review material for approval to PMC mailing list
- RC3 looks good so far
May 22, 2018 - Alex, Tom, McQ, Dani
- EPL 2.0
- Still working with foundation on whether we can gradually move to 2.0
- Will we be supporting updates from release to release in the new 3 month release cycle?
- Yes, unless we explicitly indicate otherwise.
- To simplify this, we should have a "latest" update site
- We need to make this simpler for users, but not get in the way of the EPP, OOMF, etc.
- Alex to write this up in more detail
- Dani reminded us that there had been a previous discussion in the planning council
- Project leads have updated Photon plans
- Dani will be updating the overall plan; PMC to comment on bug 529640
- Dani also working on release review and IP log
- PMC members to approve once it's ready
- As previously discussed our first milestone will be called "M2"
May 15, 2018 - Alex, Tom, McQ, Lars, Dani
- GDPR
- audit did not report any issues on our project pages
- Opening development for 4.9
- Will branch RC2 and update master with required Releng work
- master will be open after RC3
- EPL 2.0
- No plans to do anything for 4.8
- Lars will look into it
- Ideally we gradually move to 2.0
May 8, 2018 - Dani, Alex, Tom, McQ
- GDPR
- Eclipse Project collects no information from the users on the project websites
- The Error Reporting tool, might be impacted
- Also possibly bugzilla <-- Do we need to delete bugs older than some retention period?
- Impossible to remove emails from all git repos (because of cloning)
- We need to be sure to respond to requests from the foundation
- Jetty
- 9.4.10 is in latest build, and help system is working
- they made the dependencies that were problematic optional
May 1, 2018 - cancelled due to public holiday in most Europe
April 24, 2018 - Dani, Lars, Alex, Tom
- Target environments
- We will keep Java 8 and 10 and remove java 9 from the list
- remove JVMs as soon as they run out of support from target environments - AGREED
- javax.annotation
- Version shipped is quite old, should we update it to newer version
- Update to latest standalone release to be tried
- Alex to try to drive this through
- Notify cross project about removal of ee modules from the JVM
- People don't follow Java 11 work so will probably be surprised when things start to fail so we better try to spread the information
- Dani will send a link to the JEP containing detailed information
- Contribution guidelines
- Do not open bugs for simple changes and cleanups
- Actual bug fixes to be split from cleanups in separate patches so the bug commit is straight on the topic
- Dani will update the wiki
- Cancel May 1st call - public holiday in Europe
April 17, 2018 - Dani, Alex, McQ
- On Java 11...
- We are actually shipping the javax annotation support
- Java 11 is working in 4.8, but isn't in 4.7.x
- Tom Watson is investigating why it is not working 4.7.x
April 10, 2018 - Tom, Dani, Lars, Alex
- Discussed bug 533390: Eclipse does not launch with Java 11
April 3, 2018 - Tom, Dani, Mcq, Lars
- 4.7.3a update
- Delivered RC2 on Saturday, so we could fix some badness in handling Java 10 "var" support (tl;dr: rename appeared to allow you to affect "var" as if it were a type (but would not have modified the code))
- Currently think we're done
- Naming milestones
- As previously discussed, we will contribute the most recent I-build to the release train for the 3-week "M1".
- We will call our first milestone (at the 6-week point) M2 so that it aligns with the release train naming.
March 27, 2018 - Tom, Dani, Mcq, Lars, Alex
- Java packages for configured Java in workspace
- Equinox no longer provides hard-coded information about execution environments. In the past this information was used at runtime for describing the running execution environment within the OSGi Framework. Other usecases outside the Framework started uses the Java profile data from Equinox. Equinox no longer has any need for the hard-coded information so no longer provides it.
- JDT and PDE have come to depend on the internal resources of the framework to get hard-coded information about execution environments
- JDT and PDE need to have a common way to figure out the available packages for Java versions >= Java 9
- See 531642 532773
- SWT clean-up
- Lars reviewed the removal of Windows XP. Built binaries locally on Windows.
- Found a form data issue deleted some code that was still used
- Tom - Unit tests didn’t catch the issue. Concerning?
--> Update from Lars after the call: Later testing did show that this is a bug already existing in Eclipse. 4.7 and master and not related to the patch
- Lars did review and test
- Dani - put all the code in the branch and produce a build and ask windows community to test it
- Mcq - thinks it is a good idea
- Dani - create an official build for testing, not out of master with normal builds
- Lars - what is the risk of putting in master
- Dani - can do the build right away pre-CQ review approval. Allows for more quick testing.
- Alex, no need for a branch, can be a developer build we publish. Alex will ask Leo to do this.
- Jetty version
- Jetty added non-optional dependencies on service-loader
- Dani - got reverted, but old versions still caused Gerrit build issue
- We don’t need the service-loader for our usage of jetty
- jetty may be making a hard requirement on an implementation of server-loader (Aries spi-fly)
- Can we move help off jetty? Will be a major undertaking. Should figure out what it would me to do so. Currently no interested contributer has stepped up to do the work to figure out what this would mean.
- Equinox will still need jetty for the http service implementation. Perhaps things are more simple if this is an Equinox only dependency. Only pull in jetty if the http service implementation is needed and then pull in all of jetty and its dependencies.
- No current plans or interested contributors for providing our own service-loader implementation.
- Our build should start resolving the capabilities are requirements which would catch issues like this early in the build.
- Alex - can we move latest tycho to get the capability/requirements meta-data. No objections? Alex will move forward.
March 20, 2018 - Dani, McQ, Tom, Lars, Alex
- Dani: The IBM SWT team considers the Windows XP removal too risky and in addition has no capacity to look at that big change. Fine if someone else looks at the removal. The type changes will have to wait after Photon (too risky). Lars will ask Conrad and Alex will also look at the patches.
- Databinding generification should be done early 4.9, too late for Photon.
- Dani: Eclipse support for Java 10 will be merged to the official branches starting Wednesday. A Marketplace entry for 4.7.3 will be made available once 4.7.3 is released. The first official release with Java 10 support is 4.7.3a scheduled for April 11.
March 13, 2018 - Dani, McQ, Tom
- Alex had troubles to join; Lars still in vacation
- Dani: in the new release process we need to downgrade some milestones to "checkpoints" where we only deliver the bits
- ACTION ITEM: Dani to start the discussion with the PMC via e-mail and then inform cross-project
March 6, 2018 - McQ, Tom, Alex
- Short call without any interesting topics
February 27, 2018 - Lars, Dani, McQ, Tom, Alex
- JDT support for new Java releases
- McQ: With current change rate and OpenJDK process we can not promise Zero day compatibility but rather release as soon as possible
- Dani: effort to try convincing Oracle to tell the features a release earlier and get easier access to OpenJDK community
- Dropping XP support
- Dani: no objection to drop it, the question is whether to do it for Photon or delay it for next release
- Mail to be posted to cross project by Dani to gather feedback
- Alex: 1 week for gathering input on cross-project - AGREED
- If noone speaks up with reasonable reason to keep support - preapproved by Dani, Lars and Alex
- To be formally voted after the mail to cross-project
- Release names
- Version only, release names are irrelevant from Eclipse TLP side - AGREED
- Inactive committers pruning
- Lars: no access to committer emails so sending just to the mailing list
- Wait 2 months for reply before action
- McQ: ask foundation to send direct mails on behalf of the project, if foundation is not fine - remove committers directly
- Alex: only public replies to the mailing list are accepted so people wanting to remain committers at least follow the mailing list
- Tip of the day -
- Lars: CQ approved, to be merged today/tomorrow
- Alex: we should have it part of the build and part of the p2 repo for easy testing
- Dani: unclear APIs to be removed and to be simplified so we don't end up maintaining useless parts
- GTK 2 vs. 4
- Alex: Gtk 4 release aiming at late 2018, it's big change in drawing so conflicts with Gtk 2 badly
- Alex: Gtk 2 support to be removed in future one of the next 2 releases, whether Sep or Dec to be discussed later in the Photon release train
- Alex: mail to cross project list around Photon M7 or RC when more information on both Gtk 4 release plans and SWT bugs will be known
- McQ: what is our statement on supported Gtk version?
- Alex: Statement should be: Once SWT switches to latest Gtk version as default, support for previous versions goes into deep maintenance mode but will kept until it starts hurting new development and support for the default version at which point to be removed.
- To be discussed further.
February 20, 2018 - Lars, Dani, McQ, Tom
- Dani: Update on 4.7 RC3
- Lars: Can we drop Windows XP support?
- Lars: Big contribution comes in (https://bugs.eclipse.org/bugs/show_bug.cgi?id=531097), dropping XP support might be a good motiviation to contribute more also to other people. Removing lots of code including the version checks will also result in a cleaner code base for maintenance and might improve performance.
- Dani: IBM investigate if they officially drop XP
- Tom: Do we need support XP with the latest Eclipse version?
--> Pending on the answer of the IBM team, will be discussed in next weeks call
- Tom: OSGI CQs updated and approved for OSGi Service Platform 7.0 version
February 6, 2018 - Lars, Dani, McQ
- Lars: Can we mark MInput and MInputPart for deletion (bug 509868)?
- Dani: Before approving to mark them for deletion, someone has to investigate how much work needs to be done to do it. Both have over 50 references.
- McQ agrees
- Dani: Before approving to mark them for deletion, someone has to investigate how much work needs to be done to do it. Both have over 50 references.
- Dani: Topic on ui-best-practices-working-group list: Replace "..." with an ellipses Unicode character
- Looks good on Mac and is actually used by Mac OS, but less good on Windows. No info regarding Linux at this time
- McQ:
- Mac OS UI guidelines specify to use the ellipses character
- SWT could do the right thing depending on the platform
- Lars: view menu, minimize and maximize buttons look bad to him. Would like to replace the view menu with ellipses
- Dani: Would have to change all three together. View menu is always there and not indicating an overflow
- McQ: Windows 10 also uses a triangle, but upwards. Current view menu is used and familiar to users for at least more than 10 years.
- Lars to file a bug report and send the bug number to the PMC
- McQ: Should discuss in one of the next meetings how JDT can handle the new release cadence for Java
- Dani: We will see how it goes with Java 11 (18.3)
- Dani: How will we name the milestones in our new new release scheme?
- Consensus to start with M1 after each release.
- Up to planning council to decide the release naming convention. Lars: Would prefer year/month
January 30, 2018 - Alex, Lars, Dani, Tom
- General Updates (Dani)
- Shipped M5, still working some p2 issues
- RC1 for Neon.3 next week, may need API changes after the freeze for junit 5 support updates
- Discussion about the incubation for Java. Ongoing thread in jdt-dev list https://dev.eclipse.org/mhonarc/lists/jdt-dev/msg00964.html. The incubation features will be part of the release specification which implies they need to be implemented to be compliant. Spend time putting them into a release only to pull out later if they don’t finalize. Not clear there are tests added to the TCK. Alex asks if this effects us for Java 10, no not for Java 10. Java 10 only has local type reference, not huge delta of function from Java 9. No incubation in Java 10. But incubation may affect us for Java 11.
- Info about infrastructure (Alex)
- Foundation push to move to Jenkins. Releng has moved, uncovered issues with rest API and token exchange … disabled for now for Jenkins. Issue is being worked but only can be fixed once all is moved to Jenkins.
- Platform HIPP moving to Jenkins tomorrow. Will be some downtime, should be less than an hour or so. May cause several issue. Issues in non-standard jobs with multiple repos etc. For Gerrit verifications should be fine. Let Alex know if there are issues. Alex to send a note when the migration occurs.
- p2 issue is real. Other issues are pressing (infrastucture/build). Todor has a bug that he should be looking at. Not something happening in the past, but now the capabilities are being resolved. Issues happened with a hand crafted p2.inf file. Hopefully will scope down the p2.inf files. Alex to drive to determine if a respin is needed.
- Need to monitor the p2 issue, determine how many are broken. Cannot just break 100s of folks without serious consideration. Why not revert? Alex says it is not an option and we should do everything possible to fix.
- Lars asks about nominating more committers, perhaps that were rejected in the past. Now the Eclipse PMC can overlook the nomination process. Work with existing contributors showing interest and look for opportunities to sponsor them for committership.
- Tip of the day (Clippy)
- See Tips Framework
- Tip of the Day or (Clippy) in coming contribution … looking for integration M6?
- Lars thinks it is worth it. Dani disables such things by default, and also Lars. Alex find the function interesting. Others are also reviewing the patch.
- Lars is moving forward with it. If it is very easy to disable and is stable on all platforms then it should be good.
- Is there a concern about a solution that requires network … it doesn’t appear to be a concern.
January 16, 2018 - Alex, Lars, Dani, Tom
- Native builds at eclipse.org status (Lars):
- Dani: swt is done for some time already
- Dani: launchers after M5 is released to prevent breakage
- GTK launcher changes (Alex):
- Changes to not rely on X11 atoms but on dbus ready for review
- Linux only as no other GTK platforms are currently built
- Equinox CQs (Tom):
- P2 capabilities patch from Todor and felix.scr update
- Slow process risking M5
- Alex: Ping Sharon asking for speedup if possible
- Updates from Dani:
- Photon plan update - BREE to be part of the build info
- End game - Oxygen.3 and M5 - send to the list
- Running tests against Java 9
- Java 10 eclipse release (Dani):
- Oxygen.3a or marketplace feature only - Agreement for oxygen.3a
- Dani: Local Variable type inference support in a branch
- Future releases - to be aligned with JVM releases if they prove to release on time
- BREE updates recomendations
- Dani: There are reasons to stay on older BREE
- Alex: ease of getting jvm is the main concern here - if a contributor can't get jvm at that version easily we can't call it supported
Januar 09, 2018 - McQ, Alex, Lars, Dani
- Updates from Dani:
- Ian Skerrett is leaving the Eclipse foundation
- Dani got nominated as committer representive
- Planning council update
- Dani: low participation in the last calls
- Dani will talk with Melanie about it
- Input required for the planning council for the API and feature freezes for the platform
- API and feature freeze policy in platform
- Alex: API and feature freeze in platform should be RC1, except breaking API which should be done in milestone build
- everyone agrees to Alex suggestion-> agreed
- Alex: SWT linux currently uses X-Windows specific API, which does not work on Wayland. This will be moved to a DBUS API to open file and open URL
- Dani: Plan update, biggest change is for the component plan
- Equinox plan has been added
- Manual generated BREE list has been dropped from the plan. This list is still automatically generated for every I-Build
- Launcher and natives build move from IBM to the foundation still in progress
- (bug 528230) Build FileSystem native component on Eclipse Foundation Infra
- (bug 528230) Build launcher on Eclipse Foundation Infra
Archive
- Archive of Meeting Minutes from 2017
- Archive of Meeting Minutes from 2016
- Archive of Meeting Minutes from 2015
- Archive of Meeting Minutes from 2014
- Archive of Meeting Minutes from 2013
- Archive of Meeting Minutes from 2012
- Archive of Meeting Minutes from 2011
- Archive of Meeting Minutes from 2010
- Archive of Meeting Minutes from 2009