Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "Eclipse/PMC"

(Meeting Minutes)
(June 12 meeting notes)
(505 intermediate revisions by 14 users not shown)
Line 1: Line 1:
 
= Documents =
 
= Documents =
 
 
Some documents written and/or used by the PMC:
 
Some documents written and/or used by the PMC:
  
Line 8: Line 7:
 
= Meeting Schedule =
 
= Meeting Schedule =
  
The [http://www.eclipse.org/eclipse/team-leaders.php Eclipse Project PMC] has a weekly phone meeting '''every wednesday at 10.30am EST'''.
+
The [http://www.eclipse.org/eclipse/team-leaders.php Eclipse Project PMC] has a weekly phone meeting '''every Tuesday at 11.00am EST'''.
  
 
= Meeting Minutes =
 
= Meeting Minutes =
'''September 21, 2011:''' - Dani, John, Martin
 
* Dani: '''git''' - Mac / Linux using scripts, tooling not yet ready for Windows ... productivity lacks
 
** painful when working across multiple repositories ... problematic workflow for reviewing incoming changes
 
** John: egit could fetch automatically in the background (without merge)
 
* John: '''used platforms poll'''
 
** Results visible once voted: [http://www.eclipse.org/eclipse/development/platform-poll.php platform-poll.php]
 
  
'''September 14, 2011:''' - John, McQ, Dani, Martin
+
'''June 12, 2018''' - McQ, Alex, Tom, Lars
* Martin: '''PMC membership''' - still looking for people to ask after Steve and Jeff left
+
* RC4a looks good; hidpi fix is in place
* John: '''Jetty 8''' - should be using Jetty from Eclipse (Jetty 7 ist stable, Jetty 8 is current) but API changes after Jetty 6
+
** no plans for further builds at this point
** eg standalone help - AI John to ping Chris G;
+
 
** No longer re-exporting Jetty API since 3.6 (deprecated api, introduced replacements)
+
'''June 05, 2018''' - McQ, Alex, Tom, Dani, Lars
** releng, would need Jetty at -1 if using current from train .. makes builds a bit more messy again
+
* Dani:
** check with Equinox
+
** 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?
 +
*** 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:
 +
** 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"
  
'''September 7, 2011:''' - John, McQ
 
* State of building Juno at eclipse.org: we are close but still some issues with the tests. Transition to Git halted our progress on this. Once the Git migration is complete, we should just make the switch over and live with the pain of some failing tests. Component teams will need to help with diagnosing problems with their tests.
 
  
<hr/>
+
'''May 15, 2018''' - Alex, Tom, McQ, Lars, Dani
'''August 31, 2011:''' - Dani, John
+
* 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
  
* We need to pull the new ICU4J out of maintenance release because the fix didn't pass review in time. We will defer to Indigo SR2
 
* Some discussion of the treatment of tags in Git vs CVS. Committers need to be aware they can't checkout the contents of a particular build into their workspace all at once.
 
  
<hr/>
+
'''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
  
'''August 24, 2011:''' - Dani, John
 
* EGit is far behind on level of polish, usability, robustness, conforming to UI guidelines, etc. We may need to make contributions to avoid it hurting productivity
 
* Proposed workflow changes in bugzilla 4.0: {{bug|337245}}. Proposing removing NEW, ASSIGNED and CLOSED states which would lose valuable information for us.
 
  
<hr/>
+
'''May 1, 2018''' - cancelled due to public holiday in most Europe
  
'''August 10, 2011:''' - Dani, Martin, McQ, John
 
* Dani / Martin - '''Debug Flexible Hierarchy "provisional.api" namespace'''
 
** Cannot be moved into an "API" namespace without breaking external non-SDK clients since types are leaked from internal packages
 
** Q1: Move framework to a place outside Debug?
 
** Q2: Declare "internal" packages as API? - API Tools won't be usable
 
** McQ: Is it really impossible to add new API in parallel while keeping the old one in place for now?
 
*** Issues: (1) Performance, (2) bugs due to delegating, (3) is it worth doing that work? CDT already marked x-friends - Debug could offer the same for other clients.
 
** McQ: Do we anticipate a huge Community out there just waiting for stuff to become full API? Then it's probably worth it...
 
*** But at this point any potential consumers already consume, so it's likely not worth the pain of renaming
 
*** Dani's suggestion: Go into a separate bundle and re-export, such that clients don't need debug
 
** John: Unless packages were intended to be API from the beginning, it's likely not API quality (that's likely also why Boris didn't want it in Jface)
 
** Martin: Would really want to see namespace refactored... quality standards..
 
** John: Had the experience in p2, it was much more than just package renaming
 
*** Very painful for user community, but in the end produced a much better results (but p2 was very young at that time)
 
** McQ: Can we provide backward compatible versions in parallel to the new namespace? We CANNOT break consumers.
 
*** Renaming only makes sense if mirroring/proxying is possible.
 
*** Lots of consumers in the old form, how many new consumers would we gain in the new form?
 
** Martin: Create a fork / clone on the UI side for new consumers, as real API?
 
*** McQ: Only makes sense if there's a community just waiting to pick this up.
 
*** Dani: Debug itself could not move to the new framework without breaking clients ... so we'd not have any clients inside the SDK
 
** McQ: It's non-trivial work, and before starting it we'd need to verify there's consumers for it
 
** Learnings from the past: Not keep stuff in provisional for so long any more
 
** Resolution: '''Pawel to find consumers for a refactored new bundle, then decide if / how to do the work'''
 
* Dani: '''Java 7 - Segfault due to loop optimizations''' ([http://www.infoq.com/news/2011/08/java7-hotspot details])
 
** Occurs a lot inside Apache Lucene, how to communicate that?
 
** McQ: send to eclipse-dev and cross-project
 
** Oracle aware of the issue - working on an early refresh, workaround exists (disable loop optimizations via -XX:-UseLoopPredicate)
 
** Another JIT bug was fixed by Oracle before GA because we reported it
 
** AI Dani '''Talk to Oracle when an update can be expected, soon send a message to eclipse-dev / cross-project'''
 
* Vacation notices:
 
** Martin: away from August 14 to September 1
 
** McQ: away from August 22 to September 5
 
  
<hr/>
+
'''April 24, 2018''' - Dani, Lars, Alex, Tom
'''August 3, 2011:''' - Dani, Martin, McQ
+
* Target environments
* Dani - successfully moved Java 7 support to 3.7.1, 3.8, 4.1.1 and 4.2 streams
+
** 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
  
  
<hr/>
+
'''April 17, 2018''' - Dani, Alex, McQ
'''July 27, 2011:''' - Dani, John, McQ
+
* On Java 11...
* Discussed how many versions back PDE should support development on. Historically we used N-2 but currently it is N-7. The layers of compatibility are starting to become hard to manage. We agreed dropping support for versions prior to 3.6 is ok if there is a benefit in doing so (cleans up PDE, makes the situation less confusing for end user, etc). However PDE must handle existing plugins with old version numbers in the plugin.xml (possibly with a warning and a quick fix to update/remove the number).
+
** We are actually shipping the javax annotation support
* We have some rough days ahead: first release train milestone on 4.x, ongoing build pain from Git migration, merge of Java 7 into mainline, and lots of people on holidays. Hold onto your hats!
+
** 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
  
  
<hr/>
+
'''April 10, 2018''' - Tom, Dani, Lars, Alex
'''July 20, 2011:''' - Dani, Martin, John, Jeff
+
* Discussed {{bug|533390}}: Eclipse does not launch with Java 11
* Dani - '''p2 Installer {{bug|317785}}''' affects Java 7 users - when they want to update it looks like they are dead
+
** Regression test only fails once every 100 times .. might be more often in the wild
+
** Might need some note on the download page (clickthrough) - people dont read the readme
+
* John - '''git migration''' - parts from git / parts from CVS isn't that bad for now
+
  
  
<hr/>
+
'''April 3, 2018''' - Tom, Dani, Mcq, Lars
'''July 13, 2011:''' - McQ, Dani, Martin
+
* 4.7.3a update
* Want more Community involvement in the Eclipse PMC - "outside representation" in addition to companies with a commercial interest
+
** 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))
* nice Java 7 webcast last week - Mike Milinkovich mentions our Eclipse Java 7 Support (BETA)
+
** 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.
  
<hr/>
 
'''July 6, 2011:''' - John, Dani, Martin
 
* Dani - on track with Java 7 work; Oracle interested in having good Eclipse support
 
* git migration - Platform UI likely going to move this week
 
** Paul has a tool for gathering build notes from git (currently a commandline script)
 
  
<hr id="20110615"/>
+
'''March 27, 2018''' - Tom, Dani, Mcq, Lars, Alex
'''June 15, 2011:''' - McQ, John, Dani, Martin, Jeff
+
* Java packages for configured Java in workspace
* John - '''git migration''': should egit be part of the SDK ?
+
** 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.
** Build-time circular dependencies. Keep SDK small, but make it a very simple and obvious step to obtain egit.
+
** JDT and PDE have come to depend on the internal resources of the framework to get hard-coded information about execution environments
** It's already easy to update - milestone to mileston SDK update is a single step for SDK + egit.
+
** JDT and PDE need to have a common way to figure out the available packages for Java versions >= Java 9
* John - '''git migration''' and the mapfiles
+
** See [https://bugs.eclipse.org/bugs/show_bug.cgi?id=531642 531642] [https://bugs.eclipse.org/bugs/show_bug.cgi?id=532773 532773]
** In orion, just tag HEAD of the build branch
+
* SWT clean-up
** Dani: need to make sure that build notes can still be created
+
** 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?
  
<hr/>
+
--> 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
'''June 1, 2011:''' - McQ, John, Dani
+
* Some discussion of proposed Eclipse Foundation security policy
+
* We still want to see the disclosure time-frame being 3 months after the release containing the fix. Not all of our consumer community has the build technology or expertise to apply source patches to their products. Making sure the fix is in a maintenance release is the only practical way for some people to consume fixes
+
* It would be nice for critical security fixes to appear in the simultaneous release repository even after the SR2 time period. p2 would need some small amount of work to be able to flag critical/security patches and automatically notify the user about them being available. Nobody has signed up to do this work.
+
* Some discussion of Git migration. There is no need to move everything at once since our build can handle homogeneous inputs from both CVS and Git. One possibility is migrating Equinox as a first step. The most complicated piece is migrating the repository containing the builder itself. We will need to decide on where map files and documentation go: likely some kind of "common" repository for Eclipse TLP.
+
  
<hr/>
+
** Lars did review and test
'''May 25, 2011:''' - McQ, John, Dani, Martin
+
** Dani - put all the code in the branch and produce a build and ask windows community to test it
* Missing CQ's for old legacy stuff in old update sites / repos
+
** Mcq - thinks it is a good idea
** No problem for ZIP's (we can move to archive)
+
** Dani - create an official build for testing, not out of master with normal builds
** OK with removing some legacy old stuff... How many years back to keep old stuff?
+
** Lars - what is the risk of putting in master
* Java 7 and 3.7.1
+
** Dani - can do the build right away pre-CQ review approval.  Allows for more quick testing.
** Mike M OK with including in 3.7.1 (when it's stable enough)
+
** 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.
  
<hr/>
 
'''May 4, 2011:''' - Jeff, Dani, Martin, McQ, John
 
  
* RC1 test pass went well overall
+
'''March 20, 2018''' - Dani, McQ, Tom, Lars, Alex
* Investigating an SWT blocker preventing checkbox tables from working
+
* 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.
* There is a problem with the Ant mail task with Ant 1.8. Ant mail requires an optional extra jar to be added. In Ant 1.7 this didn't cause build to fail, but in Ant 1.8 it does. Our conclusion was to document in the migration guide but take no other action.
+
* Databinding generification should be done early 4.9, too late for Photon.
* Git migration:
+
* 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.
** Kim and DJ are investigating migration of the build to Git. Making progress but don't have a full build working yet
+
** We should consider summer 2011 for migration. For those teams with forked code between 3.x/4.x, they are finding it difficult to keep fixes in sync and potentially git can help with that.
+
  
<hr/>
 
'''April 27, 2011:''' - Jeff, Dani, Martin, McQ, John
 
* Dani '''still 100 bugs tagged 3.7''' - need to remind in the archcall to properly tag target milestones
 
* John '''EDL for Examples'''
 
** Value of examples is they're there to be used - there's no business value in holding on to IP via Copyright so EDL seems right
 
** Re-licensing existing examples is difficult (eg SWT examples); but new examples should go under EDL
 
** Including examples in distributed features must take care of fixing abouts
 
* John '''3.7 plan final update''': all plan items committed or deferred; update to RH6
 
  
<hr/>
+
'''March 13, 2018''' - Dani, McQ, Tom
'''April 20, 2011:''' - Jeff, Dani, Martin, McQ, John
+
* Alex had troubles to join; Lars still in vacation
* Jeff,Martin '''Builds at Eclipse''' - Work ongoing. IBM Mac has been donated. Mac testing has problems with some weird vnc bug
+
* Dani: in the new release process we need to downgrade some milestones to "checkpoints" where we only deliver the bits
** Martin - could kick a 3.6.2+ build and artifacts OK, but confused by lots of warning messages. Kim responded immediately, but can this be made "more official" ?
+
** ACTION ITEM: Dani to start the discussion with the PMC via e-mail and then inform cross-project
** Public Builds - get the engineering underpinnings in place, then polish afterwards
+
** Won't get a lot better in 3.7 but could make it a plan item for 3.8
+
** John agrees that improving the warning messages to be more informative is a good thing - Kim's very helpful
+
* Dani '''Polish Bug to be prioritized''': {{bug|342648}} In SWT on Linux, RTL mode, Tree.getItem(Point) gives invalid result.
+
** Regression ?
+
** McQ: Every GTK version needs work - maybe it's specific to a new GTK; might be more than a P2
+
  
<hr/>
 
'''April 13, 2011:''' - McQ, John, Martin, Dani, Jeff
 
* John: reminder to review proposed project charter update
 
* Freeze plan for Indigo is ready
 
* Reviewed new polish items
 
* Investigating some 4.1 compatibility problems, possibly related to EMF changes
 
<hr/>
 
  
'''March 30, 2011:''' - McQ, John, Martin, Dani
+
'''March 6, 2018''' - McQ, Tom, Alex
* Discussed and clarified the API approval guidelines. Will be announced in the arch call.
+
* Short call without any interesting topics
* Dani - Java 7 deferred from 3.7. GA planned together with 3.7.1.
+
** John: is feature work which might need review
+
* John - we need to prepare the Git migration
+
** John to ask DJ to do investigations
+
<hr/>
+
  
'''March 23, 2011:''' - McQ, Dani
 
* Prioritized the [[Polish3.7]] list. This is a recurring task for the next few weeks.
 
* Discussed and agreed on API change approval process, see [http://dev.eclipse.org/mhonarc/lists/eclipse-pmc/msg01368.html PMC mailing list note].
 
<hr/>
 
  
'''March 9, 2011:''' - John, McQ
+
'''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.
  
* Ongoing discussion of direction for 2012 release train. Will continue discussion in email to ensure all PMC members are involved.
 
  
<hr/>
+
'''February 20, 2018''' - Lars, Dani, McQ, Tom
'''March 2, 2011:'''
+
* McQ - Migrating to 4.x. Don't be disruptive when there is no need to. Want to avoid migration pain.
+
** New feature work will be in 4.x, but as long as there are committers working on 3.x it will stay alive
+
** Make sure that quality keeps up: Releng / Build, make long-term committers continue reviewing contributions
+
** Problem with 4.x is just the bugs (impeding productivity), it's not anything architectural
+
** '''Convene again next week and come up with a consistent message''', AI McQ get hold of Jeff for a statement
+
* John - '''3.6.2+ builds''' set up on Hudson now
+
** Kim's {{bug|338557}} Job's mostly ready, Martin is the first tester. Should inform the Community once things go smoothly
+
** Updating version numbers like going to a virtual never-existing "3.6.3" release in order to give a clear and consistent message
+
** Dani has an (internal) document - Martin: interested for TM and CDT projects - '''AI Dani''' send Doc to Martin for for meeting notes
+
** Always updating the micro by one only ... so if bundle was not updated in Helios SR1 or SR2, it should go .1 in 3.6.2+
+
  
'''February 23, 2011:'''
+
* Dani: Update on 4.7 RC3
* Martin - '''3.6.2+ M-Builds post 3.6.2''' - needed for adopters to get 3.6.2+ bundles signed; on demand only? If scheduled, how often?
+
* 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
  
<hr/>
 
'''February 16, 2011:'''
 
  
<hr/>
+
'''February 6, 2018''' - Lars, Dani, McQ
'''February 9, 2011:''' - McQ, John, Dani, Martin
+
* Lars: Can we mark MInput and MInputPart for deletion ({{bug|509868}})?
* Dani - '''Builder bug''': Theoretically, the builder bug can cause bad binaries shipped from Eclipse.org
+
** 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.
** But switching the builder now could have other consequences. Most people likely use the 3.6.0 or 3.6.1 builder
+
*** McQ agrees
** Platform uses the 3.6.1 builder. Bug appeared in 3.6.0
+
* 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
** McQ thinks we should recommend using the new builder - John: can never know whether a problematic code construct is there or not
+
** Looks good on Mac and is actually used by Mac OS, but less good on Windows. No info regarding Linux at this time
** Provide a patched version of the 3.6.1 basebuilder as an option for people to use - '''AI John''' ask Kim to re-produce a new basebuilder, then respin RC4
+
** McQ:
* McQ - '''Builds at Eclipse.org'''
+
*** Mac OS UI guidelines specify to use the ellipses character
** IBM Ottawa consolidating 7 offices into 2, plan to not have a build lab
+
*** SWT could do the right thing depending on the platform
** Kim still frustrated with Foundation facilities; McQ talked to people both inside IBM and the Foundation
+
* 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
  
  
<hr/>
+
'''January 30, 2018''' - Alex, Lars, Dani, Tom
'''February 2, 2011:''' - Canceled (no topics)
+
* General Updates (Dani)
<hr/>
+
** 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 26, 2011:''' - Dani, John, Martin,
 
* Dani: {{bug|330534}} '''ObjectTeams Contribution''' - JDT might allow using their namespace as an exception, couple p2 bugs pending
 
** If the p2 solution cannot be done, OT/J will need to remain off the train
 
* Martin: Concerned about '''Eclipse 3.x quality''', many regressions and not being addressed
 
** {{bug|320329}} ThreadJob#waitForRun can spin when blockingJob is not RUNNING
 
*** '''Platform Runtime: Regression''' introduced in 3.6, can have severe Performance impact, reported 10-Jul, commenters unsure about approach to fix
 
*** A buggy contribution was accepted, and then the contributor left
 
*** John spent a lot of time.. there was a fix that didn't work
 
*** Dani: Could the contribution be pulled out? - No because it's new API (yield())
 
*** Contributor was quite good originally but then just switched teams and was no longer available
 
*** The new testcase from Markus Schorn might help narrowing down the case quickly
 
** {{bug|335153}} Regression: p2 downloads are much slower due to picking remote artifacts even when a local file: URL is available
 
*** '''p2: Regression''' introduced in 3.6, reported 24-Jan, testcase + patch attached, response pending
 
** {{bug|332840}} Wrong error about API change (Regression; works with 3.7M3)
 
*** '''API Tooling: Regression''' introduced in 3.7M4, reported 17-Dec, Olivier:  "I'll take a look" but no response since
 
** {{bug|332838}} Bogus potential null pointer access warning (regression; works with 3.6)
 
*** '''JDT: Regression''' introduced in 3.7M4, reported 17-Dec, Ayushman: "I'll investigate" but no response since
 
** {{bug|332507}} [regression] incomplete build path reported on o.e.rse.subsystem.shells.local
 
*** '''PDE UI: Regression''' introduced in 3.7M4, reported 14-Dec, initial traffic but no followup since 16-Dec
 
** {{bug|335466}} Regression: category.xml processing fails when "name" contains special chars
 
*** Just detected recently
 
** {{bug|313899}} [Progress] Every user-job causes a busy cursor to be shown for a minimum of 250ms
 
*** '''Platform UI''': Patch provided on 21-May, no response whatsoever from Platform UI
 
** John: There had been a fair bit of turnover, new committers getting up to speed ... having less experienced people is a fact
 
*** Identifying key bugs in the big bug database takes a lot of experience
 
** Dani: M5 is the Major feature freeze, so new feature / API work has highest priority ... so quality drop is somewhat expected in M5
 
** Even for regressions... if the regression is less critical than new bugs, it goes behind
 
** '''RESOLUTION:''' Make the important bugs visible to the component leads or PMC. It's natural that we sometimes need to ping on a bug. M5 is a problematic time.
 
* John: {{bug|335374}} '''Redhat 6 as a Reference Platform'''
 
** SWT team doing some final testing, then will put only RH6 on the Ref Platform list
 
* John: '''OpenJDK as a Reference Platform''' - Oracle is interested and might contribute testing
 
  
<hr/>
+
'''January 16, 2018''' - Alex, Lars, Dani, Tom
''' January 19, 2011:''' - McQ, John, Jeff, Dani, Martin
+
* Native builds at eclipse.org status (Lars):
* Jeff will be unavailable for meeting next 6-7 weeks
+
** Dani: swt is done for some time already
* John: How do we interpret "under the direction of the PMC" in [http://www.eclipse.org/legal/EclipseLegalProcessPoster.pdf Eclipse legal process]?
+
** Dani: launchers after M5 is released to prevent breakage
** McQ: Not about approval, but about PMC being aware
+
* GTK launcher changes (Alex):
** Jeff: Goal is to indicate "Working with an Eclipse mindset", ie in close collaboration with a committer ... contributor must be aware of IP due diligence guidelines from the beginning of evolution of the code. We want to avoid introducing IP leaks by accepting legacy code that was written before assuming an Eclipse mindset.
+
** Changes to not rely on X11 atoms but on dbus ready for review
** McQ: This is about understanding the direction of Eclipse as a whole. Request a PMC +1 on the bug as work is being started. PMC should work with committer to ensure that contributor has been instructed about IP rules.
+
** 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
  
<hr/>
 
''' January 12, 2011:''' -
 
  
<hr/>
+
'''Januar 09, 2018''' - McQ, Alex, Lars, Dani
''' January 5, 2011:''' - McQ, John, Dani, Jeff, Martin
+
* Updates from Dani:
* Dani: Component Lead progress? - Portal still doesn't have the correct list of components
+
** Ian Skerrett is leaving the Eclipse foundation
<hr/>
+
** 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 2015 | Archive of Meeting Minutes from 2015]]
 +
* [[Eclipse/PMC/Minutes 2014 | Archive of Meeting Minutes from 2014]]
 +
* [[Eclipse/PMC/Minutes 2013 | Archive of Meeting Minutes from 2013]]
 +
* [[Eclipse/PMC/Minutes 2012 | Archive of Meeting Minutes from 2012]]
 +
* [[Eclipse/PMC/Minutes 2011 | Archive of Meeting Minutes from 2011]]
 
* [[Eclipse/PMC/Minutes 2010 | Archive of Meeting Minutes from 2010]]
 
* [[Eclipse/PMC/Minutes 2010 | Archive of Meeting Minutes from 2010]]
 
* [[Eclipse/PMC/Minutes 2009 | Archive of Meeting Minutes from 2009]]
 
* [[Eclipse/PMC/Minutes 2009 | Archive of Meeting Minutes from 2009]]

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
  • 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
    • 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: 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

Back to the top