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)
(Meeting Minutes)
(192 intermediate revisions by 5 users not shown)
Line 10: Line 10:
  
 
= Meeting Minutes =
 
= Meeting Minutes =
'''November 07, 2018''' - Dani, McQ, Alex, Tom, Lars
 
* For the 3 months releases, we have have a development freeze after RC1 until RC3. After RC3 master will be opened again for development
 
  
'''October 31, 2017''' - Dani, McQ, Martin, Alex,
+
'''January 14, 2020''' - McQ, Alex, Dani, Tom
* Tom: '''Bugzilla Landing Page''' - EMO said both PMCs need to be contacted
+
* Dani: Switch to SUSE Enterprise 15, team is in favor to drop 12
** Bug IDs, Equinox product and components remain in place, only the landing page will be updated
+
* Dani: Plan updated to remove Windows 7
* Dani: '''M3 Respin'''
+
* Alex: Felix Dependencies for SCR done
** Issue had been found by a team member, but got lost between different teams
+
** confirm fix for {{bug|544571}}
** Resolved and respun very fast, the fix is out now
+
** releng disruptions during update, but recovered. More disruptions expected as we update dependencies for March release.
* Dani: '''Release Cycles and Java Alignment'''
+
** broken builds, need to get a list of issues.  Seems to be more infrastructure issues. Need to report back to the foundation. Example, the signing issue that broken the respin.
** Planning Council F2F meeting was at EclipseCon Europe; planning call will be on Thursday
+
* Some discussion about gitlab option at foundation. {{bug|537913}}
** Initially, felt like aligning with Java 18.3 was a good idea, but for now the plan is keeping the Oxygen SR rhythm and releasing Oxygen.3a aligned with Java
+
** What happens to gerrit work flow for review?
** In case the Oracle release should slip, it will be most likely be named 18.4 (whatever month the release ends up in)
+
** Would dropping bugzilla happen or can we migrate all issues?
* All: '''Platform Release Rhythm'''
+
** Without migration it is a no-go for us
** At ECE, many people were surprised about changing release rhythm but the plan was generally appreciated
+
** Currently no plans to move Eclipse project to gitlab at this time.
** Should stick to the communicated Photon plan though and change only afterwards
+
** Alex suggests promoting a Milestone build from master (properly marked up as such) aligned with the Java 18 release
+
*** This would promote master as something that can be used
+
*** After Photon, we will release 4 times from master - there won't be any maintenance builds any more
+
*** For the release train, there will also be release candidates.
+
  
<strike>October 24, 2017 - cancelled due to ECE</strike>
 
  
<hr/>
+
'''January 7, 2020''' - McQ, Alex, Dani, Tom, Lars
'''October 17, 2017''' - Dani, McQ, Martin, Lars, Alex
+
* Dani: Created initial 4.15 plan - please have a look
* '''Conf.system:''' Fallback to McQ's number is not a good solution (can't give out the moderator code)
+
* Dani: Created release record for 4.15
** Foundation (Denis) is aware of the problem, looking for a solution sooner than later
+
* Dani: Sent a note to teams to create their 4.15 plan items/bugs
** Skype group call, or zoom.us would work for Dani and McQ
+
* Dani: Do we want to drop support for Windows 7 (remove from Target Environments only)
* Dani: '''{{bug|526065}} Java 9 to Oxygen.1a beta update issue'''
+
** Unanimous decision: Yes
** Users who had the Java 9 beta installed and "update" to Oxygen.1a are broken
+
* Dani: Discuss (again, see below) resolution for stale bugs
** McQ: Updating from "beta" to "final" is not necessarily supposed to be working (Lars disagrees)
+
** We want to ask the webmaster that stale bugs are directly closed. ACTION ITEM for Lars
** Not yet sure what's causing the issue .. p2 bug, or different groupID for Java9beta
+
** We will only auto/mass close existing stale bugs with notification turned off
** Fix the issue if it looks like a real bug or easy to fix ... otherwise just post a message, preferredly on the Marketplace client (''Dani: that part is done already'')
+
* Change rules about x-internal exports ({{bug|553709}})
* Lars: '''Release Cycle Discussion'''
+
** Decision:
** McQ still in favor of making every milestone a release
+
** - Newly added internal packages should not use x-internal exports unless there are very good reasons
*** Alex thinks we're not there yet in terms of releng, there's still too many manual steps. Would prefer slower cadence (eg 3 months) until more automation is there (updating pom.xml, version mgmt, ...)
+
** - For existing packages the x-internal export can be removed with PMC approval
*** With 4 releases per year (like today) but no more maintenance branches/backports, there's potentially less work than today
+
*** Try starting with a release every 2nd milestone; fix automation; then strive for releasing every milestone.
+
*** Dani thinks the model shouldn't change in the middle of Photon; look for feedback then move to the new model next year
+
** McQ: If we switch to the new model now (Oxygen.2), what do we lose?
+
*** Martin: Any bigger feature that would need to move into a branch? - Dani: Advanced Source Lookup
+
*** Dani: Also our rules about "no new features" and "PMC Approval" would need to change
+
*** '''Continue discussion in 2 weeks''' (skip next week due to EclipseCon)
+
  
<hr/>
 
'''October 10, 2017''' - Dani, McQ, Lars, Alex, Martin
 
* Dani: '''Oxygen.1a respin'''
 
** Primary reason for respin was, that people who have existing XText installed would be broken when updating the Platform
 
** Opportunity to piggy-back JDT critical fixes was welcome
 
* Dani: '''Equinox Move''' - Review passed without objections, working on implementation now
 
** Expecting less trouble than with the Platform and JDT merges recently
 
** Foundation want to keep Equinox as a brand, therefore will be a subproject (beside Platform, JDT, PDE)
 
** So to increase the committer base, the fast track option will now apply; also, more alignment in terms of PMC.
 
** Confirmed again that we will ask Tom to join our PMC. Approval can be found in [https://dev.eclipse.org/mhonarc/lists/eclipse-pmc/msg03166.html this thread].
 
* Dani: '''Planning Council - Rolling Releases Update'''
 
** Should remove some of the work maintaining 2 streams - simply release from master regularly
 
** In the past, API breakage (migration guide) was allowed only once per year - how to deal with this moving forward
 
** Handle with semantic versioning; how to give adopters sufficient time to adjust
 
** There's usually 2 camps for every topic being discussed ... though practically, Platform sets the pace
 
** Release Naming - New Name every quarter? Versioning scheme? (like 2017.4 or 17.04)
 
** How to simplify processes (also in terms of IP), can the Foundation scale up? Perhaps not more work, but more deadlines
 
*** In terms of the Release Review, only the N&N and the Migration Guide are relevant; need to satisfy small and big consumers
 
* Martin: '''Reddeer Contribution'''
 
** When we last discussed this, it was an important criterion that any contributor can run the tests easily
 
** Alex: Looks good, essentially boils down to running "mvn clean verify" in the PDE repo (or right-click > Run as Reddeer from the IDE) - '''AI Alex''' will have a video sent to the PMC list
 
* Alex: '''API Removal in Context of Rolling Releases'''
 
** Which Rules to apply for allowing removal of API; Allow removal in any release?
 
*** McQ: The real question is, how long it takes consumers to adopt to removal
 
*** Dani: Is more conservative regarding deletion - the value removing something is often smaller than the ripple it causes
 
*** McQ: If there is code in our codebase that significantly slows us down, it should be remove even if API
 
** Martin: With more releases, there's less push to upgrade ; but will consumers know they are broken? - Semantic versioning should address that, but who really uses upper version ranges ... they have caused more pain than benefit in the past
 
** Dani: In the past, with our 3-year deprecation plan, Major versions have not been updated even on announced removals...
 
** McQ: If we are earnest about faster velocity, we '''have to''' fully adopt semantic versioning practices. If we as producers have done what we could, our job is done - consumers who don't use upper version ranges are on their own
 
  
<hr/>
+
'''December 10, 2019''' - Alex, Dani, Tom, Lars
'''October 3, 2017''' - Dani, McQ, Alex, Martin
+
* Dani: RC2a respin to be promoted today
* '''Conf system woes''' - Dani couldn't dial in, Denis restarted the bridge leaving Martin and Alex in a Zombie bridge
+
* Dani: 4.15 M1 approaching fast (January 10)
** '''ACTION McQ''' will send out conf.details using IBM's bridge
+
* Dani: master is open
* {{bug|520720}} Mickael's question on Performance improvement
+
* Dani: Version bumps done for now
** Dani: There is already an asynchronous RequestLayout API for clients, and APIs already suggest clients use the async one
+
** Rebase if needed Gerrit makes it being able to push without version bumps and breaks next build
*** Therefore, changing the synchronous API to work asynchronously doesn't look right.
+
** Tool needs improvement to collect all version bumps needed to make initial bumps faster
** Alex: We seem to be mixing two aspects here -- agree regarding RequestLayout concerns, but why should the ProgressMonitor one be a problem?
+
* Dani: How to make milestones used more
*** Dani: Agree that the ProgressMonitor approach makes sense, but a very careful review is needed - existing code already subclasses ProgressMonitor, need to make sure that expected methods are still called
+
** Have latest and deny things that have been since M1 and no one reported till RC1
*** '''ACTION Dani''' will do a careful review of the ProgressMonitor part and deny the generic RequestLayout part
+
** Consider having latest unstable aka milestone channel which can be used by users/integrators
* Dani: '''Equinox Restructuring''' request for the move is in, will work with Tom and Foundation forward
+
* Tom: Java 8 support dropped - no decision to be made now
* Dani: '''Oxygen.1a''' - RC2 is in for JUnit5 and Java9
+
** Respin of Oxygen.1 for {{bug|520176}} Mac 10.13 High Sierra problem? - Not currently planned, there will be 1a instead
+
** A feature patch is another option, providing patched SWT; and, there's the workarounds
+
* Dani: '''Rolling Release''' - 2 topics: rolling release, and alignment with Java Update Releases
+
** Some projects on the train have alignment goals with other projects outside Java; will discuss again in the Planning Council
+
* Alex: '''{{bug|522733}} webkit crash''' - A workaround is available, in contact with webkit devs for a complete fix to keep Photon usable
+
** Workaround would introduce a small memory leak, but only on the first instance of webkit created
+
  
<hr/>
 
  
'''September 26, 2017''' - Dani, McQ, Alex, Martin
+
'''December 3, 2019''' - Alex, Dani, McQ, Lars
* {{bug|520176}} '''MacOSX 10.13 (High Sierra) Menus Disabled'''
+
* Dani: RC2 this week. Supposed to be the end of 4.14 for us.
** Only non-English Locales are affected
+
* Dani: Rules for exporting packages as outlined in [https://wiki.eclipse.org/Export-Package Export-Package] :
** For 4.7.1a and Photon, a fix is in
+
** Background: {{bug|544977}}.
** Foundation [https://www.eclipse.org/org/press-release/20170925criticalbug.php Press Release (Newsletter)] is out with information how to work around
+
** We need to discuss whether we want to relax those rules.
** Tweets are around as well -- keep spreading the message
+
** Tom to file a bug report.
* '''Equinox Move Review''' - progressing
+
* Alex: {{bug|522733}} '''GTK Crash on Close preventing IDE Restart''' - can it go into 4.7.1a ?
+
** Seen with Fedora 27 (Webkitgtk 2.18)
+
** Foundation wanted to keep Java9 stuff separate, so pushing it there might not even help
+
** The issue is serious (hard crash preventing restart of the IDE), though fortunately not many people have that particular webkitgtk version yet
+
** Investigate details and possible workarounds, then consider our options -- maybe a Foundation Newsletter similar to the OSX 10.13 issue
+
  
<hr/>
 
'''September 19, 2017''' - McQ, Alex, Martin, Lars
 
* '''Async APIs request from the eclipse-pmc list''' (not discussed today)
 
* Lars: '''Java 6-month release cycles'''
 
** Alex likes the 6 month idea - less backporting
 
** McQ would ideally like full releases every 3 months (except not releasing anything unfinished)
 
** Dani: If Java really delivers every 6 months (will they?), Eclipse could consider rolling releases every milestone. There is a doc from the Planning Council (Mélanie Bats) in that regard.
 
** Dani: Support for the public JDKs will be limited to the current release only (6mo)
 
** Risk: Oracle Java may be working on big features "in the background", if there is very little time adopting new features (current license doesn't allow releasing stuff built on Beta's) it's hard for Eclipse to keep up
 
** Lars: Some teams already moving to Kotlin...
 
** Dani: More discusssions planned at ECE, AC etc
 
** '''AGREEMENT''' to wait for now for (a) the Planning Council announcement and (b) how Java will actually implement and live up to their plans. Work towards faster release cycles (that's a good message to the consumers anyways).
 
** Will need to work on details. If there's more releases, and each one needs a review, it's more work on release records and reviews. Already on a good path here, paperwork reduced to a matter of an hour.
 
* Dani: Java 9 (Oxygen.1a) round the door. Plan is a full release.
 
* McQ: {{bug|520176}} '''MacOS 10.13 menubar issue''' people at Apple are also looking at it. Biggest problem is that it's not 100% reproducible. Might end up with some System Properties to be set to resolve the problem.
 
  
<hr/>
+
'''November 26, 2019''' - Alex, Dani, McQ
'''September 12, 2017''' - McQ, Alex, Dani
+
* GTK minimum version being upgraded: 3.14 -> March; 3.22 -> June
* Dani asked Alex to look into {{bug|517063}} with high prio. We need this for M2.
+
* Target environments upgraded for 4.14, PMC members please verify
* Dani: sub-project merge
+
* Standalone SWT download was broken in M3; Fixed in RC1
** McQ and Lars approved my message regarding sub-project. Will send out the note today.
+
* Mac downloads are now being notarized
** Still an issue with IP log not being merged
+
* Red Hat team will help with release engineering work
** Release engineers can no longer restart the HIPPs
+
* Started to discuss [https://dev.eclipse.org/mhonarc/lists/eclipse-pmc/msg03116.html Advise for performance enhancement making API methods behave async]
+
** We need more time to verify the fix and look at the patch. Will discuss and decide next week.
+
  
'''September 5, 2017''' - McQ, Alex, Martin
 
* Alex: {{bug|521639}} '''Mac Signing Issues for Oxygen.1'''
 
** 3 requests out of 5 failing, don't know yet why - webmasters assume hardware issues, trying to move to a different machine
 
** RC4:
 
*** Security fix in p2 ({{bug|518031}})
 
*** Changes in Releng scripts to run tests on different Mac machine
 
  
<hr/>
+
'''November 19, 2019''' - Tom, Alex, Lars, Dani
'''August 29, 2017''' - McQ, Dani, Martin
+
* Bumping GTK minimum version for SWT
* All: '''Conference System Woes''' - 3 tries for McQ (race conditions?), 2 tries for Martin (silence first), 10 tries for Dani
+
** No bump has been done in the last 2 years
* Dani: '''Subproject Merge''' done after some hiccups, no complaints since Fri
+
** GTK 4 is starting to shape up.  In preparation we need to move up.  3.14 minimal version from 3.10 for March 2020 release.  Will allow styling to go through our CSS engine.  Will address many bugs because we override the behavior.  Allows us to remove dead code.
** Subprojects are now "archived" with a comment that they got merged into the parent project
+
** For June release move to 3.22 release directly.  Wayland is useless under 3.20
** '''AI Dani''' planning to send another notification to mailing lists:
+
** Will confirm with the SWT team that this is ok, will have an answer next week.  PMC agrees to proceed as long as the development team is OK with it.
*** former PLs to become Repo Maintainers responsible for signoff and planning
+
* Dani: Fighting with build
*** Bugzilla remaining the same
+
** Orbit checksums were not redone in latest (working on fix)
*** Some former subproject leads already stepped up as combined project co-leads (Lars, Lakshmi, Sarika)
+
** Issues with Mac signing - been really unreliable {{bug|553205}}
** McQ: Move forward towards the new structure, but there's also need to push for responsibility among the subcomponents (finding go-to persons...)
+
* Dani: No IPLog needed this release, will need to be at least every year and we will do it in March.
* Dani: '''StyledText improvement request on the ML''' (Pluggable selection model)
+
* SWT patch for Windows, allows to theme the scrollbar. Patch is stale now?
** point to the e4 incubator for experiments, encourage innovation though might be quite hard and pervasive
+
** Can the team look at the patch and rework? We can review but likely not rework. {{bug|444560}}
* RC3 looking good (except for build issues on the Foundation side, no I-Build since Aug.22 - Mac DMG is at risk for RC3)
+
* Dani away next week, please watch the list for approvals towards RC4 next week
+
  
<hr/>
 
'''August 22, 2017''' - Alex, Dani, Martin
 
* All: '''Conference System Woes''' - Dani had 7 minutes trouble dialing in; Alex was kicked out
 
* Dani: '''Plan''' - '''AI Martin''' review
 
** Target Platform reduced - removed too much? - and Subproject plans. Rest is copy-and-paste.
 
* Dani: '''Subproject Merge''' - Everything approved, waiting for implementation by EMO.
 
* Dani: '''RC2 this week''' - Still many Platform/UI bugs, Dani will make a pass moving out since Lars is on vacation
 
* Martin: '''feature/bundle version issues'''
 
** Dani: Checking versions is quite time consuming, there's no tooling solution for the workspace right now (but there are reports).
 
** For branding bundles and features, rules are different than for others - Dani currently doing those, since few people have access
 
** Currently we're looking good, but automation would be better than manual nagging
 
  
<hr/>
+
'''November 12, 2019''' - Tom, Alex, Lars, Dani
'''August 15, 2017''' - Alex, Dani
+
* M3 next week
* Dani: '''subproject merge''' initiated - waiting for webmasters
+
** Many open bugs targeted for 4.14 M3 and 4.14
* Dani: Provided Photon (4.8) release record and plan - please provide comments
+
** Request for contributors to act on them and retarget
* Alex and Dani discussed feature/bundle version issues - next builds should be better
+
* Gerrit reviews
 +
** Dedicated time to spend on review patches from non-commiters and non-employees of IBM and Red Hat
 +
** Time still to be considered
 +
* Dani to check whether IP Log and review are needed for 4.14
 +
* Official build runs with Java 11 now
 +
** This is the runtime JVM used by the build system, nothing in the deliverables should require Java 11
 +
** Tools are catching up, reports had to be modified to work with it
 +
** If there is any issue noticed in deliverables, reports, download pages ... - please open a bug report and add Alex on cc
 +
* Pack200 (tom)
 +
** Test whether everything is fine if pack200 is gone is pending
 +
** Companies shipping only packed files will face issues
 +
** Ship alternative pack200 implementation? - better look at alternative compression if so critical
 +
** Build tools (e.g. reports generator) are using Pack200 classes directly, that would be a problem in the future
 +
** Drop packed files requirement for SimRel
 +
*** If/when contribution requires Java 14 it's the only feasible thing to do, to be clarified in requirements
  
<hr/>
 
  
'''August 8, 2017''' - Alex, Martin, Dani
+
'''October 29, 2019''' - Tom, McQ, Alex, Lars, Dani
* Eclipse [[Asterisk]] system is not working reliably (again). It took Dani 6 minutes until he could dial in (using the Swiss number - US number failed repeatedly). McQ can't dial in until 10 min later.
+
* Dani  
* Dani: starting the '''planning record for Photon''' to announce participation in M1
+
** still working on the PPC64LE issue
** Toplevel items: JUnit5, Java9. Subplans on the Wiki.
+
** EclipseCon was great, met lots of people, JDT team plans to do more reviews in the future
* Dani: '''subproject merge''' - wanted to wait for M1, but should be done this week
+
*** Dani: missed Lars, Mickael, Andrey and others
* Alex: '''ppc64be''' - Sravan is waiting on final decision whether it will be removed in Photon
+
** Wayne and Markus might not continue to work on the release train, so this may end up an automatic process or a new working group may be founding another person
** Dani: PMC decision was settled, so removed from Eclipse plan - IBM ''might'' still continue building it for internal use
+
* General discussion about unmaintained projects and how to deal with that
  
<hr/>
+
'''October 15, 2019''' - Tom, Alex, Dani
'''August 1, 2017''' - no call
+
* Shipped 4.13 M1 on time
 +
* Quickly discussed Wayne's plans to reduce his time for the Release Train
 +
* Next week EclipseCon (no Dani)
  
'''July 25, 2017''' - Alex, Lars, Dani
 
* project merge got go, Dani to implement it with webmaster and then send out the announcement this or next week. E-mail will also mention that existing project leads can become co-leads on Eclipse Platform
 
* Discussion if CVS should be removed from the SDK build, Alex +1, Lars +1, Dani +1
 
* Discussion if the remaining 2.0 compatibility layer can be removed, Dani: OK to remove but other plug-ins might still have dependencies to it, must the also updated, as well as the documentation
 
  
'''July 18, 2017''' - McQ, Alex, Lars, Dani
+
'''October 08, 2019''' - Tom, McQ, Alex, Dani, Lars
* project merge review awaiting go from Wayne - Dani pinged again in the bug report
+
* PPC64LE machine
* Dani will kick off planning for Photon a bit earlier since he will be in Bangalore the next 12 days. Platform UI already started.
+
** Downtimes experienced with current one and general warning that there might be more
* M1 on August 11
+
** McQ: how many downloads do we have?
<hr/>
+
*** Dani: probably more in products rather than IDE downloads
'''July 11, 2017''' - no meeting
+
** PPC64LE workstation on the market (https://www.raptorcs.com/content/TL2DS1/intro.html) and Fedora looks into adding PPC64LE desktop spin
 +
* Jetty update test failures
 +
** Tom to ask Raymond to help us with it
 +
* 4.14 plan created
 +
** To be published once we gather the work items
 +
* Release record created
 +
* M1 this week
 +
* Gerrit submit
 +
** AGREED: Switch to "Rebase if Necessary"
 +
** Alex to take care of contacting admins to see change implemented
  
'''July 4, 2017''' - no meeting
 
  
<hr/>
+
'''October 01, 2019''' - Tom, McQ, Alex, Dani, Lars
'''June 27, 2017''' - McQ, Dani, Martin, Alex
+
* Dani to look into plan and release record for 4.14
* '''Equinox Merge to the Eclipse TLP'''
+
* Stale bug reports should be closed as WONTFIX if there is not a response to the stale bug flag
** Keep Equinox as a separate Project, to allow independent Equinox releases without Platform (and keep Bugzilla simple)
+
* Changes on Gerrit to allow fast-forward merges
** The only argument for stronger integration would be getting more committers, but there is no strong need and we have the FastTrack process in place for that
+
** deferred to next week
* '''Eclipse Merge of Component (Sub)Projects into Platform'''
+
** Just 4 Projects: Platform, Equinox, JDT, PDE (plus the incubators for e4 and JDT)
+
** Former (Sub)Project Leads to become "Component Leads", "Technology Owners" or "Repository Owners"
+
*** Repository Ownership is appealing as the structure is very clear (+1 Dani,Alex,McQ)
+
** Platform Lead initially Dani, more Co-Leads could step up if they want
+
*** Main work is helping component leads if they can't come to a consensus - usually less work than PMC duties
+
* Dani: '''JSR 376 Ballot'''
+
** Public review reconsideration ballot got approved by all except Red Hat who abstained
+
** Much progress in the past weeks, consensus except RH abstained
+
** Looks like the OOBE of Java9 would tolerate reflection, currently looks like on track for a September Release
+
* '''Vacations''' many people will be off next week, especially in the U.S.
+
** PMC call will be skipped next week
+
  
<hr/>
 
'''June 20, 2017''' - MQ, Dani, Lars, Alex
 
* Attracting new contributors discussions - code cleanup and deletion of old paths needed
 
** Alex: Big issue to get people working on codebase and considering many now irrelevant paths in the codebase
 
** Dani: Cleanups should be done by the one starting them through the whole SDK
 
** Lars: Not feasible as some projects are slower pace moving and the change might require more effort than one can or is willing to spend in his free time
 
** Alex: Great opportunity to have new people joining by doing simple tasks and grow them into full committers
 
** McQ: We have to come up with list of items we would like to get cleaned and properly follow our deprecation policy even if the migration guide for Photon get really big with things we schedule for removal in the future.
 
* Dani: Sub-projects merge
 
** Name of the new project - McQ: Everyone refers to it as Platform so natural choice it is
 
** JDT, PDE, Platform (subprojects) to become single project
 
** Person responsible for some code area in the merged project - to be further dicussed
 
* Dani: Dropping Xulrunner support - PMC to approve it in the bug
 
  
<hr/>
+
'''September 24, 2019''' - Tom, McQ, Alex, Dani
'''Juni 13, 2017''' - MQ, Dani, Lars
+
* discussed enabling fail on warnings on JDT projects
* Dani: Release review for 4.7 was successful
+
** Dani to clarify with Roland
* Dani: Rebuild for 4.7RCa required due to new EMF version and a fix for a critical bug which resulted in duplicated menu entries
+
  
* Merge of the sub-projects
 
** Planned for M1, desired to be coordinated with the move of Equinox to Platform
 
** We prefer to keep the project pages and wikis so that all the information is kept
 
** Preferable we want to have one committer list for Eclipse platform
 
** Dani to check with foundation how the merge can be done
 
  
'''May 30, 2017''' - Martin, Dani, Lars
+
'''September 17, 2019''' - Tom, McQ, Alex, Dani
* Dani: Please approve or disapprove the release review
+
* Crash issue on win32 - respin done
* Dani: '''Starting the Debugger doesn't work always'''
+
* Java 13 GA
** Occurs for Lars, but isn't reproducible - one of the top 3 things to fix if steps to reproduce are found
+
** marketplace entry works with M3 and onwards
** Lars: Equinox replaced the DS implementation in 4.7, the issue is probably related
+
** merge into master starting
** Failure is totally random: On a very slow Virtual Machine, it failed almost always (9 failures out of 10); on other machine it works most of the time; even after working fine 3 times, it may fail the 4th time; seems to occur more frequently on older machines than newer ones.
+
* 4.13 GA
** Martin: try with a reverse debugger like [http://chrononsystems.com/products/chronon-time-travelling-debugger/download Chronon] ?
+
** looks goods so far, packages are there
*** Should help by just collecting a log; and when the failure occurs, "play back" the log to understand under what condition the race condition occurs; the a reproducible case is available, and the log can also be sent around between different developers for investigation, potentiall also to Apache Felix upstream
+
** macos notarization still in process for EPPs
* Dani: '''Equinox Launcher Issues'''
+
** During M7, a change was made to ignore certain command-line arguments
+
** This caused 2 regressions - {{bug|517013}} and {{bug|516349}} MacOSX restart regression
+
** Java 9 will probably change the parameters again, see {{bug|516911}} :(
+
** It's getting too late to make any more changes to the Launcher. Re-compiling on different hardware has already caused {{bug|517013}}, it's possible that more issues (not yet known) might be caused by the rebuild. With Java 9 probably changing again, we don't win much by rebuilding to try and align with something that's not yet released.
+
*** Option A: Put options into the eclipse.ini -- today it works for both Java 8 and Java 9
+
*** Option B: Add the "probably proposed" new option to the launcher, will need to rebuild the launcher again
+
*** Option C: Revert the launcher to what it was before (and well tested) back to M6 - for running with Java 9, the options have to be added manually
+
** Users will have to read on a webpage what needs to be done for Java 9 launching; for Eclipse SDK, a single option is needed - some add-on components
+
*** Additional complexity: Different JVMs need different options (IBM, Oracle...)
+
*** Martin: {{bug|517452}} Introduce a fallback mechanism to the launcher, which reads the Java ID and loads 'eclipse-javaID.ini' with a fallback to 'eclipse.ini', but does not seem reasonable for Oxygen since too late
+
*** Better to have a clean story: At IBM, the entire build environment changed ... reverting gets us back to a bullet-proof launcher that was tested for 7 milestones ... will work safely with Java 8, for Java 9 people will have to read the N&N or StackOverflow to find out about the right arguments - same as in Neon
+
* '''AGREEMENT to revert the Launcher to the M6 version'''
+
  
<hr/>
 
'''May 23, 2017''' - Alex, Martin, Dani, McQ
 
* Dani: '''Apache Batik XXE Vulnerability'''
 
** Alex: Moving to Batik 1.9 would be good, but there is so much UI breakage that it's not viable for Oxygen
 
* Martin: '''Bugs discovered during RC test cycle'''
 
** Surprised that some low-priority issues do get attention ({{bug|517108}}) while others get no response at all ({{bug|517013}}
 
** Dani: Only interested in severe issues and regressions - send message to platform-releng-dev with severe regressions found
 
** Dani: Please +1 the Gerrit for {{bug|517108}}
 
  
<hr/>
+
'''September 10, 2019''' - Tom, McQ, Alex, Lars, Dani
'''May 16, 2017''' - Alex, Martin, Dani, Lars
+
* Gerrits are failing
* Plan Update - updated on Wiki, main plan updated, please provide feedback until tomorrow latest:
+
** one failed because of missing version increase, some appear to be tooling issues
** Has Updates to delivered / not delivered, and Target Operating Environment
+
** change went in to API tooling, which may fix it
* {{bug|509922}} Performance Tests: Header is wrong, but it really compares against 4.6.1: results are created but report is wrong
+
** do not merge failing gerrits
** Code should have been improved through many action enablement changes and startup improvments
+
* Many thanks to those who worked through the weekend to fix the Mac signing issue!
** Sravan will work on making a proper comparison against 4.6
+
* '''Test failures:''' Some in Platform/UI fail frequently, the most frequent ones should be considered for fixing
+
** Browser tests: pick "an available" server, the M7 run was on a newly provisioned server which didn't have all the stuff for Webkit. This should be fixed now.
+
** CVS tests fail from time to time since the CVS server isn't stable at the foundation
+
** UI tests may fail if Mozilla or similar show a pop-up dialog requesting an update
+
* {{bug|516114}} Tabbed Properties View Styling Change
+
** Due to the code change, the Tabbed Properties View is now loaded even if it's not used; that may degrade performance
+
** The issue is due to how styling is architected; an OSGi flag activates the plugin if any class is "used", the CCS engine just checks for a class without even instantiating, that already triggers the bundle activation
+
** That should be discussed for change in 4.7.1 or 4.8 ... maybe use reflection to avoid this, or avoid the need for eager activation of tabbed properties ... Lars did that in the past, but it's a lot of effort
+
** Activation by itself would be relatively cheap, but then the code goes through all Singleton instantiations - hard to estimate
+
*** The impact is likely small compared to PDE for example, which takes 1.5 seconds out of 6 seconds startup time
+
** '''AGREEMENT:''' In order to be fair to other people who worked on improving startup performance, the change should be reverted. We have a change that benefits few people, but impacts everyone here.
+
*** Lars: OK to revert, but in the next cycle we should look at improving activations in general. Opening the Resource perspective should not activate PDE + JDT (today, this is likely triggered due to some decorators).
+
*** McQ would love to see an "optimistic UI" which can render at least the shell even if not all menus/etc are yet filled in
+
* Dani is out Thu-Sat, please jump in and help the team if something is needed
+
* Alex: '''Project Structure'''
+
** Platform/Resources doesn't have a lead at the moment. Would like to merge more and more into Platform/UI. It doesn't make sense keeping separate structures just for the sake of creating barriers to contributions.
+
** Eventually we'll just have the Platform/UI morph into "The Platform Project" with more co-leads
+
** In the end it's not about positions and authorities .. it's all about people who are good
+
** Dani: Agrees; in experience, every 2nd contribution is causing some issues, but we do have good people even if they are not official leads
+
** McQ: What we really need is high-level overview and authority to recognize changes that might negatively impact others..
+
** Could eventually end up with JDT/PDE/SWT/Platform. Lars and McQ are not so sure any more if SWT really needs to be separate, had several overlapping contributions - 9 active SWT committers also work on Platform code. Consider moving forward with this after the Oxygen release...
+
** '''AGREEMENT''' to move forward on this, with a ''Platform Leadership'' group. We need to advance to leadership of Eclipse along with advancing the code. Leadership change should also lead to growing community.
+
  
<hr/>
 
'''May 9, 2017''' - Alex, Martin, Dani, McQ
 
* Dani: '''JSR376 Jigsaw''': 10 said yes and 13 said no; a new spec to be provided within 30 days
 
** From a technical perspective, should be possible to resolve within 30 days
 
** JDT team implementing a compiler; IBM implementing a JVM, that's completely separate concerns!
 
** For implementing a compiler, the last spec is quite old, that is not good enough
 
** JDT team votes via Mike Milinkovich (Eclipse Foundation), Mike considered JDT team and RH team and probably others
 
* Dani: '''M7/RC0''' - test passes upcoming; compressed scheduled due to the moved date for Devoxx
 
** When using the RC, watch out for 2 things:
 
**# Action contribution enablement fix -- look out for menu and toolbar items not properly enabled
 
**# Section forms layout
 
* Dani: '''httpcore 4.4.1 -&gt; 4.4.6 ECF Update and API Compatibility'''
 
** Annotations got removed - no binary breakage, but breaks source compatibility
 
** People will prefer newer httpcore; API breakage due to annotations is unlikely
 
** Also, source breakage gives developers a chance to just recompile, so accepting the new version is better
 
** Alex: Are we forcing our dependencies to not break API? - We don't have that power anyways?
 
** Alex: httpclient has security issues every few months ... better consume the latest now, and we'll likely have to update again. So if breaking compatibility, better do it now
 
** '''AGREEMENT''' to do the update and thus accept the source breakage.
 
* Flooding in Ottawa: Restricted to a fairly small area
 
* Dani: '''Release Review''', does anybody look at the full document or can it be simplified?
 
** All of the information in the RV is public (eg bug statistics, # contributors, ...)
 
** McQ: It's useful for consumers to see that new things are happening, that is the N&N; beyond that, the use is limited. Effort around half a day.
 
** Many bloggers talk about new things anyways
 
** Migration Guide and N&N will get into the RV Material; beyond that, Dani offers adding stuff that people request
 
** '''AGREEMENT''' to keep it simple, and send add-on requests to Dani if they come up.
 
  
<hr/>
+
'''September 3, 2019''' - Tom, McQ, Alex, Lars
'''May 2, 2017''' - Dani, Lars, Martin, Alex, McQ
+
* Discussed status of RC3
* Lars: '''Regex Evaluator Plugin'''
+
** This Friday for Platform - two known issues being looked at
** Basically a view where one can input a regex and text, and see if it matches
+
** {{bug|550672}} - Alex - Still no final solution to the problem.  May result in backing out fix to {{bug|548002}}
** Would like to add to e4 incubator, goal to eventually add into Platform/Text or similar
+
** {{bug|550606}} - Tom - at first seemed like a major regression that could require a revert of fix to {{bug|548877}}.  Alex - has been determined to be a very limited scenario that we feel is not blocking the release and does not warrant reverting to fix.
** McQ: Where it the boundary between e4 and Platform? How do people kick off little projects .. e4 incubator?
+
* Discussion of download stats. Much improved over the past year and looks to be double what the Photon release was a year ago for the 2019-06 release.
** '''AGREEMENT''' to move code to Eclipse.org (into the incubator) and proceed from there. Might not end up in Platform, but will be good having the code at Eclipse.org.
+
** Some thoughts on what has caused the increased interest. Lars - much work around quality and performance. Alex - a result of a broader community involvement and other development plugins for eclipse gaining popularity which drive Eclipse downloads.
* Dani: Endgame plan sent - Oxygen looking good, not too many bugs open
+
* Dani: '''JSR Jigsaw Ballot'''
+
** Asking for finalizing the Specs on JSR376 before voting Yes, since otherwise life is hard
+
  
<hr/>
 
'''Apr 25, 2017''' - Dani, Alex, Martin
 
* Dani: '''Neon.3a'''
 
** Respin done -- problem: Updating from Neon.3 to Neon.3a , the problematic bundles are not removed
 
*** '''AI Alex''' tell Jeff to ask Pascal or Tom about how to disable the bundles on update
 
*** Martin: If this problem can't be resolved could live with it ... better not take too much risk trying to resolve this very special problem
 
  
<hr/>
+
'''August 27, 2019''' - Tom, Dani, Alex, Lars
'''Apr 18, 2017''' - Dani, Lars, Martin, Alex, McQ
+
* Dani: '''RH and Java9 Jigsaw'''
+
** Very good write-up linked from the [https://dev.eclipse.org/mhonarc/lists/eclipse.org-architecture-council/msg03385.html AC Mailinglist] - see also [https://dev.eclipse.org/mhonarc/lists/eclipse.org-architecture-council/msg03389.html follow-up]
+
** Eclipse JDT team concerns that the Spec is not complete brought forward to Wayne
+
* Dani: '''Neon.3 Respin'''
+
** Last action was with Ed Merks to validate that the Fix from Tom Watson actually works - no update so far
+
* Lars: '''[https://marketplace.eclipse.org/content/glance#group-details Glance] Migration''' to e4 and/or Platform
+
** e4 incubator was always intended to have very low entry barrier - can give the Glance team access quickly
+
* Lars
+
** JUnit 5 licensing - EPL + Apache
+
  
<hr/>
+
* Dani - Status update
'''Apr 11, 2017''' - McQ, Lars, Alex, Dani
+
** RC1 this Friday for Platform - on track
* Dani: Update from last Planning Council call:
+
** Still working on Notarize Mac app ({{bug|549814}})
** There will be a special drop for Java 9 in July, but it has not yet been decided whether it will be a release where users automatically get the update, or a special p2 repository or Marketplace entry where the update can be done on demand.
+
* Dani on vacation next week, starting this Friday
** Issues with Neon.3. A respin might be necessary. For details see https://dev.eclipse.org/mhonarc/lists/eclipse.org-planning-council/msg02741.html.
+
** ==> please watch out for approval requests for API and feature changes after RC1
* Dani: Asked Lars to review the Dark theme bug. Lars, said, he's not a user of it, but has one in his team. Dani: Ask him to review the change.
+
  
<hr/>
+
* Lars - new filter icon ({{bug|465914}})
'''Apr 04, 2017''' - Dani, Martin, Alex
+
** all agree to be willing to change the icon
* Martin: {{bug|514257}} and [https://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg14316.html cross-project Neon.3 wiring issue]
+
** Dani: not just a funnel, but maybe a combination of sieve and funnel, or a good sieve icon
** Problem: External libs don't deal with versions the same way we do
+
** Lars: will make some suggestion in the bug report
** Dani thinks that the problem is that Release Train projects don't agree on one version to use
+
** Martin saw a similar problem related to some bundles doing import-package and others doing require-bundle:
+
*** Commons Logging is not a Singleton
+
** Dani has a call with Tom later today; hoping a respin can be done after fixing in Equinox
+
* Dani: Heads up on upcoming Planning Council discussion re: Java 9 and Junit 5
+
* Dani: '''PPC''' - No response on McQ's message regarding PPC, Dani will update the Plan after another week
+
  
<hr/>
+
* Lars - compare panel orientation: should we change the default to what's in Gerrit? ({{bug|501752}})
'''Mar 28, 2017''' - McQ, Alex, Lars, Dani
+
** Agreement to try in 4.14 M1
* Replacement for Sergey
+
** let's wait and see how things go
+
** next candidate would be Tom Watson once Equinox is moved back to the Eclipse top-level project
+
* Dani: PPC strategy: drop 32-bit, provide 64-bit with Oxygen (4.7) and drop 64-bit BE with Photon (4.8)
+
** all agree
+
** McQ will send a note to cross-project-issues-dev
+
* Lars will nominate Mikaël Barbero for Platform UI
+
* Lars plans to bring a IDE search plug-in to e4 (http://ystrot.github.io/glance/)
+
  
<hr/>
 
'''Mar 21, 2017''' - Dani, Martin, Alex
 
* Dani: '''Dirk Fauth''' [https://dev.eclipse.org/mhonarc/lists/eclipse-pmc/msg02891.html Requests on eclipse-pmc]
 
** Alex agrees with Dani
 
** Where does the "0.x version before graduation" requirement come from? - Development Process, but maybe didn't apply to plugin versions
 
** Dani thinks that forcing a 0.x version causes forced breakage once something goes API thus doesn't make much sense
 
* Dani: '''Szymon Ptasiewicz'''
 
  
<hr/>
+
'''August 20, 2019''' - Tom, Dani, Alex, Lars
'''Mar 14, 2017''' - Dani, Martin, Alex
+
* Dani: '''Java 9 readiness''' - see [https://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev cross-project-issues-dev]
+
** Step 1: For testing, just download a Java 9 beta JVM, add the module -- all testing is possible from commandline
+
*** Platform team has an install, but Mike was concerned about legal issues - a bug is open to allow all simrel access
+
** Step 2: Running the JDeps tools as per the [[Java 9 Readiness]] wiki can show violations
+
*** Can even run with Java 8, Dani ran it on simrel, it's looking mostly good, only Orbit shows violations
+
*** Platform team has some scripts; for Hudson there's even a Mojo, but it aborts when it finds a violation.
+
** Step 3: Reflection - Will only figure out when knowing the code or testing
+
** All these 3 tests can be done without the Java 9 patch in PDE. Only for debugging, one needs to self-host.
+
*** This can be done either with Ed's Oomph support, or via the Marketplace
+
** Platform team is still negotiating options for better support with Oracle
+
* Dani: '''JUnit 5''' considers cutting down features for aligning with Oxygen
+
** Decision to align, contributing support to Oxygen Update 1 in September
+
* Dani: '''2 Platform Issues in M6'''
+
** platform.ui reexports everything including jface - lower bundles not updated - JDT may fail if installed (fixed for M7)
+
** major version uprev: interface not marked as @noimplement; reverting the version, people who loaded Friday's M6 would never get any updates any more; decision to stick to the version uprev, since the respective bundle is not used a lot
+
*** In general, accidental major version uprev should be reverted because the error would stay around for long and might break existing binary bundles who can't be fixed any more
+
*** In this case, it was OK to keep since the bundle isn't used much
+
* Alex: '''Generic Editor and Testing'''
+
** Looking very good already - only 1/3 of the code needed for getting the same feature set as with existing methods for creating editors
+
** Looking for features to add missing documentation (workflows, use-cases like converting existing editors): End goal is to provide everything that the JDT Editor is providing
+
** Dani: Likes replacement of pages on multipage editors, and some new editors; would not consider replacing the JDT editor
+
** In the Platform.ISV docs bundle, there should be a section for "how to write your own editor"
+
  
<hr/>
+
* Dani - Status update
'''Mar 7, 2017''' - Dani, Martin, Alex, Sergey, Lars
+
* Dani: '''4.6.3 Updates''' - Looking good, Equinox bugs moved out by Tom
+
* Dani: '''4.7M7 Update''' - Infrastructure issues but testing looks OK (except Mac which is not built yet)
+
* Dani: '''Java 9 / Planning Council Update''' - Postponing Oxygen was discussed but denied; late July update being considered
+
** See the [https://dev.eclipse.org/mhonarc/lists/eclipse.org-planning-council/ eclipse.org-planning-council archives]
+
* Lars: '''Platform.Resources Leadership''' after Sergey Leaving
+
** Dani pinged Szymon, will continue discussion when we hear back; merging with platform.ui is one option
+
** Sergey: The "Team" and "Resources/Filesystem" parts could be considered separately. Consider merging Team into UI.
+
** Alex: One top Platform Project would make sense now...
+
** Dani: reconsider when McQ is back. In the past, SWT was seen as separate.
+
** Dani: Releng needs to be separate and protected because Releng committers can also change Hudson jobs, shut down servers etc where no history is kept
+
  
<hr/>
+
** Tests are looking good for M3
'''Feb 28, 2017''' - Sergey, Alex, Martin, McQ
+
** Dani team gave focus to new Search, found several UX issues, like shortcuts
* Alex: '''Short update on Neon.3'''
+
** NPE Bug in the JDT quick outline, got fixed and rebuild was triggered
** 2 jdt.core bugs asking for PMC approval - regressions compared to Neon.2, approved
+
** Resource packs were donated by Redhat, IBM and vogella GmbH to platform, discussion how long it will take for the foundation to update
** PPC rebuild is in, so looking good
+
** Dani to discuss the build infrastructure with the foundation
* Sergey will leave Eclipse work after end of March
+
* Martin: '''RCPTT / Reddeer / Testing'''
+
** Reddeer: No tests that check Platform only - everything is on higher level today (WTP, server connectors etc)
+
** Runs on Neon.2 right now inside RH - the infrastructure isn't built for consuming daily builds
+
** Would take some effort reducing to Platform only - no time for this in the RH team at the moment
+
** '''AI Martin''' will look at integrating RCPTT as time permits; would like {{bug|505826}} resolved ideally
+
*** See https://github.com/moberhuber/eclipse.platform.rcptt-tests
+
*** And https://github.com/eclipse-testing/eclipse-platform
+
  
<hr/>
+
* Parallel activation for the IDE - Tom
'''Feb 21, 2017''' - Dani, Alex, Martin, Lars, Sergey
+
* Lars: {{Bug|512273}} Allow any committer to retrigger Gerrit validation, and {{Bug|512319}} allow rebase
+
** '''Agreement''' to allow retrigger for anyone, but rebase should be done by committers working on a contribution
+
** Dani: Not clear where to retrigger (Sergey: it's discoverable once permission is there)
+
** '''AI Lars''' follow up on the bug
+
* Martin: '''UI Testing'''
+
** [http://eclipse.org/rcptt RCPTT] is completely Open Source; commercial server could be used for load balancing tests but this is not necessary
+
** Alex: Interested in Reddeer for upstreaming tests that already exist at RH; good reports about stability and scalability at RH
+
** When we decide which way we go, we need a plan who's doing the work (create the tests). Maintenance would depend on their structure.
+
** Some Reddeer tests already upstreamed with WTP and Linuxtools
+
** Lars: Where would the tests live? - In a common project accessible to all, or with the component they test ?
+
*** Lars, Dani: Since these are functional end-to-end, should live in their own repository, accessible by all committers.
+
** '''AI Martin''' follow-up with Jubula. Try RCPTT on Windows and Linux. Give feedback till next week.
+
** '''AI Alex''' share list of Reddeer tests existing at RH
+
** '''AI Lars''' play with the Reddeer API
+
* Dani: '''Update on PPC''' drop 32-bit, build 64-bit both le and be on RH VMs {{bug|512224}}
+
** Alex: ppc64 currently built on Fedora 25; could build on REL7 if foundation requests a machine from RH Brno Farm '''AI Alex and Dani''' ask Denis
+
* Dani: '''Neon.3 RC3''' please keep an eye on builds
+
* Dani: Away this Friday afternoon and whole next week
+
  
<hr/>
+
** Tom stated that it will be very time consuming to enable this
'''Feb 15, 2017'''
+
** Might cause lots of issues during startup, i.e. deadlocks or missing DI due to activation order
 +
** Result: definitely nothing we should just do, without seeing a clear benefit during startup and it would require lots of efforts to get this well tested
  
<hr/>
+
* Process removal of views - Dani /Lars
'''Feb 8, 2017''' - Dani, Alex, Martin, Lars
+
** NavigatorView is deprecated but plugin.xml extension is not deprecated as we have no means of doing that
* Dani: '''{{bug|509412}}''' - Adopt newer JSch for Platform 4.6.3
+
** Suggestion from Lars: Announcement of removal now and mark for deletion
** Alex is fully consumed with Webkit work for Oxygen
+
** Suggestion from Dani: Replace the implementation
** Need to move target platform to the latest Orbit in order to pick up the new JSch; that might cause other changes, since Orbit retention policy keeps only one version
+
** Alex: Adding it to the label of the view
** Dani: Cherry-pick the new JSch recipe to the Orbit Maintenance Branch ?
+
** Martin: Looks like in the past, new Orbit R-Builds were made for Maintenance ... but with the move of Orbit to git, it is unclear how branch builds for Neon.x would be made
+
* Dani: '''Update on RT PMC (Equinox) coming to Platform'''
+
** Tom Watson is in favor, reached out to Wayne for process
+
** Potentially move entire IP log, but IP team is currently busy with CQs for Oxygen
+
* Dani: '''Finally Unblocked on Java Language Server'''
+
** Dirk from Microsoft signed the committer agreement
+
* Dani: '''Scenarios for UI Testing'''
+
** Initial Scenario from the PMC Notes can already be used; once that works, could extend to more
+
* Dani: '''Sign Up for Security Rep'''
+
** See [https://dev.eclipse.org/mhonarc/lists/tools-pmc/msg03927.html Wayne's message to PMCs] requesting PMC attendance
+
** John Arthorne used to be the Security Rep;
+
** Tasks: Follow the security mailing list; currently low volume but might get higher with IoT getting up speed
+
** '''RESOLUTION: Alex agrees to sign up''' since already following security issues
+
* Dani+Alex: '''libswt-gtk3 natives for PPC'''
+
** Alex: Trying to limit the list of supported GTK versions to maximum 2; now at the latest GTK2 version
+
** Currently, only Intel builds do both GTK2 and GTK3; PowerPC only does GTK2; the current hardware is unable to install REL7
+
** Would prefer building at the Foundation over using custom company hardware; cost of hardware is around 50K
+
** Primary Platforms should be built at the Foundation, secondary builds can be contributed ... should Linux-PPC be considered primary ?
+
** Alex could easily provide a Fedora Platform, but it would be much newer than anything else that's around; ARM32 and ARM64 builds are already provided by Fedora
+
** If somebody (IBM) needs an older version like CentOS, it would need to be provided by such adopters
+
** '''AI Dani+McQ''' find out on priority of Linux-PPC (32bit, 64bit)
+
* Alex: '''Update on Reddeer Testing Framework'''
+
** A new version is being written, that no longer uses SWTBot underneath; there's a plan making this an Eclipse project
+
** Engineers claim that after the rewrite it's a lot more stable recognizing widgets than on top of SWTBot
+
** Martin has been looking at [http://eclipsesource.com/blogs/tutorials/rcp-testing-tool-rcptt-basic-tutorial/ RCPTT] which looks promising initially (easy to record tests) but unclear how stable such tests would be.
+
** (call had to be closed at this point)
+
  
<hr/>
+
Result: Send out send to cross that we want to delete the view, outdate the label with "Deprecate" and mark it for deletion.
<strike>Feb 1, 2017 - cancelled</strike>
+
<hr/>
+
  
'''Jan 24, 2017''' - Dani, Lars, Martin, Alex
+
Tom: Do we need a way to deprecate an individual extension? Discussion about and general agreement that this would not help clients.
* Dani: '''New Jetty Version''' - Alex will look at it after FOSDEM (Feb 7)
+
* Dani: '''javax.xml''' - Plan to announce removal from the feature on cross-project for M6
+
** Cannot remove from the compile prerequisites, because plugins still on Java 5 need it
+
* Alex: '''[http://jboss-reddeer.github.io/reddeer/ Reddeer Testing Framework]'''
+
** JBoss Tools uses Reddeer for overall user story validation
+
** Lars: Why wasn't the framework added to SWTBot? -
+
*** Reddeer is not a framework, it's meant as a test harness library - smaller scope than SWTBot or Jubula
+
*** API Stability across multiple Eclipse versions is out of scope, thus created outside Eclipse for now
+
** Martin: Any improvements in object recognition compared to plain SWTBot?
+
*** Reddeer tries to make use of the best mechanisms from SWTBot for object recognition (Finder, or callbots). That saves users from making newbie mistakes in SWTBot, but apart from that it's no better
+
*** No solution for external (non-Eclipse) dialogs ... that's not doable in SWT
+
** Lars: EclipseSource people have been talking about [http://eclipsesource.com/blogs/tutorials/rcp-testing-tool-rcptt-basic-tutorial/ RCPTT], it might be able to deal with native tooltips etc
+
** Dani and Lars think Jubula is too heaviweight; might work for Integration Builds, but not for individual developer's builds. Local setup must be really easy. Also, setup looks non-trivial, needs resources to work on ... and, doesn't seem to add much benefit over SWTBot (assuming that Jubula agent doesn't hook into native libs like win32, Cocoa or GTK).
+
*** Alex: Especially integration in Maven may be hard.
+
** Alex: Main limitation is that we don't have resources to actually create tests. Suggest reaching out for help asking people who would actually create tests ... then use whatever framework that people would like to use.
+
** Dani and Lars won't be able to come up with a workflow scenario before end of next week --&gt; Alex will come up with an idea since he has meetings on Monday.
+
*** Dani: Launch Eclipse, choose a workspace, open the package explorer, create a Java project (helloworld). Expand later, maybe into quick assist.
+
*** '''AI Alex''' to demo Reddeer in 2 weeks
+
*** '''AI Martin''' to try installing Jubula until next week
+
*** '''AI Martin''' ping Sergey re: asking for help on Platform/Resources.
+
  
<hr>
+
'''August 13, 2019''' - Tom, Dani, Alex, Lars
'''Jan 17, 2017''' - Dani, Sergey, Alex, Lars, Martin, McQ
+
* Dani: Mass changes only up to M1?
* Sergey: '''Merging platform.resources with platform.ui'''
+
** Lars - If everyone agrees then post M1 changes can happen
** Seems that more contributions to platform.resources are made by platform.ui committers, than others. Only 2 platform.resources committers seem active (and those two are actually platform.ui committers as well)
+
** Tom - What makes it a mass change?
*** Opening up to Platform UI would encourage more people to actually contribute to resources. Strive for shared access on components that are interrelated
+
** Alex - doesn't see the need for timeline on guideline, just make it across the build
** Dani: Merging into platform.ui would mean making Dani and Lars the leaders for signoff - that causes too much burden
+
** -1 review always blocks the merge until some agreement is made on the change
** Sergey: Platform/Team has actually more synergy with Platform/UI than resources
+
** Committers are not required to have review and it is up to the committer to ask for a review
** Alex: For gcc for example, there is a notion of "maintainers" per git repo for signoffs - that's independent of leadership or commit rights
+
** JDT has additional concerns because a branch is needed to do next Java release development.  Should just be a restriction for JDT to decide when mass changes can be made.
*** McQ: Not sure how adding another role would simplify things ?
+
** Resolution:
** Sergey: The problem for signoffs is not is much the volume of commits, but the volume of failing tests
+
*** Mass changes are requested not to be more than 50 files in general if they can be split up but ...
** Alex: The manpower of Platform Resources is so low by now that even {{bug|509412}} was not being filed ... existing committers do not really seem to "own" the project any more, this is an indication for merging
+
*** Don't force it to be split for cases it is difficult to do so
** Martin: Can't see how merging into a bigger entity would resolve the "ownership" problem. Perhaps make interested contributors Platform/Resources committers instead, and see how to resolve the ownership issue on the smaller scope ?
+
*** A committer can block a mass change (like any other change) with -1 if there are good arguments
** McQ: Propose applying the recent simplification of gaining commit rights (for "known" committers)
+
*** Don't restrict mass changes to specific milestones
* Lars: '''Removing javax.xml'''
+
*** Cleanups are allowed at any time during development cycle
** Was introduced only for very old JRE's , it is part of the JRE now
+
*** Should reviewers be added?? 
** Martin: Might cause a uses constraint issue since not exporting the package with version any more, see http://njbartlett.name/2011/09/02/uses-constraints.html
+
**** No adding reviewers is not required by committers
** Lars: With javax.annotation, that was solved with smart reexporting
+
**** Project leads should monitor Gerrit queues - PMC agreed
** McQ: OK with removal when we can confirm we're not breaking things
+
* General discussion about JDT team changes with Java release cycle ...
** Dani: Whoever requested removal should double-check whether the API is the same.
+
** expect large changes for Java 14 (e.g. Valhalla)
**'''AI Lars''' send a note to Tom Watson as the submitter.
+
* Alex - What happens when our dependencies require java 11?
* Dani: '''Project Updates'''
+
** Particularly for help, Lucene and Jetty
** Deadlines upcoming for CQs and APIs - see Endgame Plan, please provide feedback
+
* Lars - Fix in toolbar ({{bug|549898}}) that exposed another bug that is old
* McQ: '''UI Testing and Jubula'''
+
** If not fixed do we need to revert original issue?
 +
* Dani talks about resource packs and possibility of companies donating resources to the Eclipse Project: https://www.eclipse.org/lists/eclipse.org-project-leadership/msg00181.html
  
<hr/>
+
 
'''Jan 10, 2017''' - Dani, Lars, Martin, Alex, Sergey, McQ - Special Guest: Alex Schladebeck
+
'''August 6, 2019''' - McQ, Tom, Dani
* Dani: '''Platform Bits on Maven Central''' - Now available thanks to Stephan Herrmann
+
* Dani: contributed I-build to M2 last Friday
* Dani: '''Board Committer Rep Elections''' opening
+
* Discussed [https://www.eclipse.org/lists/platform-dev/msg01793.html macOS 10.15 notarization process]
* Dani: After David Williams' move, Wayne is looking for a Planning Council Chair; Fred Gurr has taken over Simrel Releng
+
 
* Dani: objenesis (Mockito / Easymock dependency) and Java9 - will wait for how upstream is planning to address issues
+
 
* Lars: '''Equinox move to Platform''' - no updates - '''AI Dani''' talk to Tom again
+
'''July 30, 2019''' - McQ, Alex, Dani
* McQ / AlexS: '''Jubula'''
+
* Nothing to discuss.
** In the past, with lots of full-time Platform committers, sniff tests just happened automatically giving great confidence. Now, with more part-time work happening, there is more need for end-to-end workflow test automation to give quality confidence
+
 
** Martin: On top of low-level JUnit tests, want at least very few highlevel end-to-end test to avoid "Eclipse looking silly". Need UI tests that are really stable (avoid random failures)
+
 
** Dani: On EGit SWTBot tests, too many libraries to install, how to run on Gerrit HIPP slaves
+
'''July 23, 2019''' - McQ, Tom, Dani
** AlexS: Original Jubula goal was to allow non-programmers write tests. Beginning 2015, the client API (for controlling the SUT) was separated from the front-end, was separated from the ITE. This allows writing UI tests programmatically, and avoids the need for a database.
+
* Nothing to discuss.
*** For identifying components/actions to write tests, officially an object mapping needs to be done in the front-end (ITE, integrated test environment). But there may be a shortcut available for getting object IDs
+
 
*** Compared to SWTBot, Jubula is 90% blackbox (code highlevel actions rather than things like calling setText())
+
 
*** UI Tests typically take longer than unittests by definition (due to setup, teardown, ...), so might not be applicable for Gerrit triggers
+
'''July 16, 2019''' - Alex, Tom
*** Dani: Would like to run a first test on CentOS first, as part of the integration tests
+
* Bouncycastle MessageDigets plugin inclusion (bug 541781)
*** Lars: Robustness of the tests? - SWT on Mac is problematic, but Linux and Windows should be OK.
+
** Alex: Which feature should contain it so it's published?
*** Martin: Dependencies? - Around 5MB Libs, plus the agent needs to be installed (around 100MB). Once that is there, tests are stand-alone on a laptop. There might also be an "embedded agent" but not sure ('''AI AlexS to check''')
+
** Tom: Let's discuss on the bundle but usability of current equinox features is questionable.
*** Getting a first test up and running ? - Maybe around 1 week, depends on what to do ?
+
** Alex: Let's sanitize them in this case.
**** Lars: Would like something for quick access. Martin would something for "fresh download" (fresh config area + workspace) maybe combined with quick access.
+
** Tom: +1, we need to figure what the deprecation policy (if any) there is for features.
*** '''AI AlexS''' send slides
+
* Merge of rt.equinox.bundles and framework git repos
*** '''AI Dani + Lars''' propose scenarios. Check possible owners of the initiative on Platform/UI side
+
** Tom: still interested in it but very low priority
*** '''AI AlexS''' check possible PlatformUI Contributors from Jubula team to get started
+
** Alex: interested in it for the sake of rename of repos from rt.equinox to eclipse.equinox
 +
 
 +
 
 +
'''July 9, 2019''' - Dani, Tom
 +
* Dani: M1 this week. Looks good so far.
 +
* We will not suspend the calls during summer.
 +
 
 +
 
 +
'''July 2, 2019''' - Alex, Tom
 +
* General chat about bugzilla vs gerrit only workflow.  No binding decisions due to lack of quorum.
 +
 
 +
 
 +
'''Jun 25, 2019''' - Alex, Lars
 +
* General chat about state of affairs due to lack of quorum
 +
 
 +
 
 +
'''Jun 18, 2019''' - McQ, Lars, Tom
 +
 
 +
* The 1.5 minute start up time issue (Windows Defender) needs to be investigated
 +
** Is this related to the signing problem?
 +
*** Dani: No, see {{bug|548397}}
 +
** What do we have to do to be "blessed" by Microsoft?
 +
***Dani: Not sure this is the solution as we do not even know what the problem is
 +
* There is a perception that Eclipse on Windows is not as smooth/performant as Linux now
 +
** This is a bit troubling, since windows is still our most significant platform (by downloads)
 +
** Do we need to look for ways to increase participation in SWT on Win?
 +
* Do we need better coding pattern/style guidelines?
 +
** Particularly for "clean up" patches that touch a wide range of code
 +
***Dani: I think so, see [https://www.eclipse.org/lists/eclipse-pmc/msg03670.html Andrew's note to the PMC mailing list]
 +
 
 +
 
 +
'''Jun 11, 2019''' - McQ, Dani, Alex, Lars, Tom
 +
 
 +
* 2019-06 release
 +
** RC2 shipped on time
 +
** No pending request
 +
** Lars: Opening next release stream - felt too long due to amount of incoming gerrits. It's a nice problem to have but no change planned on the topic so far.
 +
* Gerrit down
 +
** Dani called webmaster, negotiated it to be made tier 1
 +
* Emeritus status for historical committers
 +
** Foundation is dropping the feature overall so no plans to nominate new people from the last group of removed committers
 +
* No bug report policy
 +
** Simple fixes do not require bug report
 +
** Dani: larger patches to require bug
 +
** McQ: reviewer should the have the right to request
 +
** Alex: requiring too many bugzillas is against young population used to github
 +
** AGREED - we stay as we are and reviewer has the right to ask for one if he feels the need
 +
* New committer process document - whoever has a comment to comment on the document
 +
* Modern eclipse
 +
** McQ: how to define what to work on without too much bias
 +
** Alex: new intern working on inline editing - an initiative to serve as example of modernization
 +
** AGREED - come up with list of things to work on
 +
** ACTION ITEM: Lars: to create initial document for list of things/initiatives
 +
* Dani not on call for the next 3 times (Eclipse Board meeting, manager training and vacation)
 +
 
 +
 
 +
'''May 28, 2019''' - McQ, Dani, Alex, Lars, Tom
 +
 
 +
* http client issue
 +
** should we ship old and new?
 +
** we initially decided to only ship new one.
 +
** ship old only gives ability to revert back, but still requires work on client
 +
** if a fix isn't available for using the new http client then we will consider shipping only the old one for 4.12
 +
** others can install the new http client if they want to try it out
 +
* message to Stephan
 +
** Note set, no additional information or status available
 +
* heading into RC builds for 4.12
 +
** end game plan created
 +
** finalizing the plan and closed after updating target environments
 +
* discussed {{bug|547011}}
 +
** decided to bump event bundle version to work around
 +
** need a new bug opened to enable us to detect this situation earlier
 +
* Major version increase on API removal discussion
 +
** announced API removals will not cause major version bumps
 +
** This potentially breaks others
 +
** We only do this on announced deprecations for 3 years.
 +
* Future of Eclipse IDE (McQ)
 +
** Power users for writing code.  A lot still use vanilla text editor ...
 +
** What is the value of the IDE in today's environment.  Deployment and monitor of applications is more important.
 +
** Are we not addressing the problems of today to make Eclipse the power tool of today.
 +
** Do we need support for new languages.
 +
** Language server help?
 +
** can we find some set of things to do to reduce friction to using Eclipse IDE?
 +
** remove notion of project natures?
 +
** asynchronous operations can help?
 +
** Make our lists of top things to do
 +
** get community involvement on prioritizing the list of important things to improve.
 +
* Alex out next week
 +
 
 +
'''May 21, 2019''' - McQ, Dani, Alex, Lars
 +
* Dani
 +
** M3 is this week, need to watch out for bugs and issues
 +
** New feature to make modal dialogs non-modal created a blocker but this has been fixed
 +
** Endgame plan will be send out by Dani by the end of this week
 +
** We only ship an HttpClient45 implementation with the latest ECF and no HttpClient4 anymore which may cause issue. Dani's team will send out a note tomorrow, Alex thinks that this should not create an issue
 +
** Release restrictions from the foundation are less strict for the next release (no IP log and release review for every release required anymore), we will follow this process
 +
* Discussion about Stephan Herrmann's email to the PMC and we need to check with Stephan
 +
** IBM may have an option to provide service releases
 +
** We should also look at the bug system to see what is important to the users
 +
 
 +
'''May 14, 2019''' - McQ, Dani, Alex, Tom
 +
* No complaints about our M2 delivery so far
 +
* M3 is next week
 +
** 200 bugs still open
 +
** People are just bumping them to the next milestone
 +
** Better to remove target milestone if you don’t actually believe it will be fixed by then
 +
* Jetty dev list note:
 +
** https://www.eclipse.org/lists/jetty-dev/msg03307.html
 +
** javax namespace stuff will move jakarta namespace
 +
** Jetty 9 and 10 will support what was there, but we will need to react at some point
 +
** Things in flux
 +
* Batik update — 4 of 5 CQs approved should be in for M3
 +
 
 +
 
 +
'''May 7, 2019''' - McQ, Lars, Dani, Alex
 +
* Gerrit verification jobs to give -1 on warnings
 +
** Dani: not easy, single file with warnings in Jenkins for all type of warnings
 +
** PMC is in favor of such solution but there are technical limitations to achieve it or it would require significant effort to get to warning free builds
 +
* ECF http client update
 +
** Dani: prefer to ship both old and new implementation, fine with new one only and reconsider
 +
** Alex: not in favor of shipping two implementations as that would make the testing harder, prefer to ship single one and that being the new one, reconsider if there is issue
 +
** ACTION: Dani to reply to Scott that Eclipse SDK will ship latest only and we would like to have it for testing purposes ASAP
 +
* Inactive committers
 +
** Dani: Notification sent and inactive committers that want to keep commit rights can do it now
 +
* 2019-06 M2
 +
** Dani: I-build delivered to M2
 +
* Dependency updates
 +
** Alex: Jetty is in progress to 9.4.18, permissions to publishing the version to p2 repo on behalf of Jetty project granted
 +
** Alex: Batik - work in progress
 +
 
 +
 
 +
'''April 30, 2019''' - McQ, Tom, Lars, Dani
 +
* M2 for us this week - will only contribute last good I-build - no real milestone week
 +
* Extend fast track for committers for all projects not just inactive ones
 +
** Tom: already following the proposed process
 +
** We can't force committers to accept a new committer (against EDP)
 +
** Unanimous decision to drop fast track program. Mentor/committer can propose any contributor if he can justify the nomination
 +
* Request for review on JDT mailing list
 +
** Wait for Stephan to respond for a day or two
 +
** Dani to contact Stephan if no response
 +
 
 +
 
 +
'''April 23, 2019''' - McQ, Alex, Dani, Tom
 +
* M1 train has been published but no official announcement was sent
 +
* Alex to update Jetty with latest security fixes
 +
 
 +
 
 +
'''April 16, 2019''' - Lars, Dani, Tom, McQ
 +
* M1 has shipped -- Lots of good stuff, see the N&N
 +
* Plan has been posted
 +
** Attempt to simplify the creation process, still WIP
 +
* Started working on identifying inactive committers
 +
** Inactive == haven't committed anything for 2 years
 +
* Looking at ways to ensure we have enough testing of new Java features
 +
** Main projects should run on widest ranges of versions, so can't just raise BREE there
 +
** Could add new test projects, and allow tests to be written with new constructs
 +
 
 +
 
 +
'''April 9, 2019''' - Alex, Dani, Tom, McQ
 +
* Dani
 +
** Lots of regressions Dani investigating
 +
*** cycle from tests (fixed)
 +
*** UI elements gone missing (fixed)
 +
** Get rid of the new index from JDT
 +
*** Needs lots of polish to get rid of bugs, but never showed performance improvements.
 +
*** Decided to disable the option to use it (code remains).  Open to others to help maintain.
 +
** Created initial 2019-06 (4.12) plan
 +
*** Still need individual plan bugs from leads (cough Equinox).
 +
** Created initial release record for 2019-06 (4.12)
 +
** Made a call for plan items for 2019-06 (4.12)
 +
** M1 this week
 +
*** Looks good so far.
 +
* Tom
 +
** Investigating parallel activation of bundles {{bug|540507}}
 +
* Alex
 +
** M1 fixes for SWT
 +
*** Fixes for other things in M1 some small regression in custom Linux environment.
 +
** M1 jsch update needed
 +
** Tom to Open bug for Apache Felix SCR update post M1
 +
** SWT issue
 +
*** SVG image support for Linux-only to start.  Need support for other platforms.
 +
*** Windows has a number of patches pending. (mostly cleanup patches?)
 +
*** Try to get more people on board for Windows support help.
 +
*** Ask for help on the platform list.  We have combined the projects and have more devs available to work on SWT if they are willing to help.
 +
*** For cleanup you need specific SWT knowledge.
 +
**** two types of cleanup - use quick fix from Eclipse - and real refactoring.
 +
** If we are to advance SWT development then we cannot continue with a single committer on a platform.  Need to promote the recruitment of new SWT committers.
 +
 
 +
 
 +
'''April 2, 2019''' - McQ, Dani, Lars, Tom
 +
* Planning for this release has started
 +
** Sub-projects need to have first cut of plan ready by a week from Friday
 +
* Also a week from Friday is our M1
 +
* Based on community feedback we will keep the update site for adding Java 11 support to the 2018-09 (4.9) release, the Marketplace entry remains removed
 +
 
 +
 
 +
'''March 26, 2019''' - McQ, Dani, Alex, Tom
 +
* Dani
 +
** Inactive committer cleanup progress.
 +
*** It is now harder.  Portal has been deactivated and the functionality to get inactive committers is gone.
 +
*** Looking to use some script originated by Lars for list of contributors.
 +
***  What is the timeline to be considered inactive again?  Ans. A year of inactivity will trigger the question.
 +
* Alex
 +
** Confirms that the new indexer has no value to Red Hat (see also March 5 and {{bug|544898}})
 +
** {{bug|545032}} Implement native ImageLoader (Linux only)
 +
*** Allows additional formats not previously supported to work with the native Linux implementation of SWT
 +
*** What kind of error message will be available on other platforms?
 +
*** Need to confirm the API doc is updated to indicate what formats are supported on what platforms. (Alex will take care of that in the javadoc)
 +
*** Has there been investigation into what later Java versions provide for image loading?
 +
**** No, could be done as part of investigating support on other platforms.
 +
*** Need to have an umbrella bug for the new functionality with additional children defects for the platforms that don't support the new formats. (Alex to open that)
 +
 
 +
 
 +
'''March 19, 2019''' - McQ, Lars, Dani
 +
* Dani
 +
** 4.11 on track - repositories and download page ready for tomorrow
 +
** Java 12 GA expected today
 +
** Will merge Java 12 work to master tomorrow or on Thursday
 +
** Will provide a Marketplace entry for Java 12 support for 4.11
 +
 
 +
 +
'''March 12, 2019''' - ???
 +
* Missing
 +
 
 +
 
 +
'''March 5, 2019''' - Tom, Alex, Dani
 +
* Dani
 +
** I will be away starting Friday and next week. No laptop ==> watch out for any 4.11 related issues
 +
** Tom, please update the status on the Equinox 4.11 plan
 +
** Tom: {{bug|544370}}: NoClassDefFoundError: org/apache/sshd/server/auth/AsyncAuthException from SshServ
 +
** {{bug|544833}}: Inactive committer cleanup for Platform for the 4.12 release
 +
*** Might be much more work since committer info from old portal is not available in the new PMI
 +
** Get rid of new indexer. Alex, not sure who from Red Hat mentioned it at EclipseCon Europe but there seemed to be interest to further work on this.
 +
*** Alex: Roland looked at it and could not see any benefit
 +
*** Current thinking: drop it, but Alex will double-check and report back in two weeks
 +
 
 +
 
 +
'''February 26, 2019''' - McQ, Tom, Alex, Lars, Dani
 +
* Dani
 +
** Issues with Mac signing
 +
*** McQ: we should ask the Foundation whether they can't set up a watchdog
 +
**** Dani: filed ({{bug|544915}})
 +
** Issues with JAR signing
 +
** Release on track
 +
** Prune inactive committers
 +
*** AGREED to do this like we did last year for Platform ({{bug|530200}})
 +
*** Lars for Platform. Tom for Equinox and Dani for JDT and PDE
 +
* Lars: move active committers to the list of contributors in the Acknowledgments
 +
** AGREED
 +
 
 +
 
 +
'''February 19, 2019''' - Tom, Alex, Dani, Lars
 +
* Lars: API removal announcement on cross project
 +
** AGREED: To send one mail per release for RC1 announcing all removals to reduce noise on the mailing list
 +
** In case of more important removal it can be announced individually.
 +
** Dani to open bugs for releases so it's handled properly.
 +
* Lars: Provisional API guidelines changes
 +
** Current approach with internal/provisional package names until API is stable is an issue because:
 +
*** It creates more work for maintainers to rename packages.
 +
*** It creates more work for adopters to change references once API is stable.
 +
** AGREED: Use the intended package name but mark it as x-internal until API is final. Lars will update the document.
 +
* Dani: End game plan posted
 +
 
 +
 
 +
'''February 12, 2019''' - Tom, Alex, Dani, Lars
 +
* Dani:
 +
** M3 next week.
 +
** Must start to work on IP log, release review and Endgame plan.
 +
* Alex: What's the future of ECF (not much happening there)? How feasible is it to replace ECF and HttpClient with new Java HTTP Client from Java 11?
 +
** Interesting to know, but unfortunately no resources to investigate this at the moment.
 +
* PMC decision regarding HttpClient for 2019-03: will ship what we have (4.5.5).
 +
 
 +
 
 +
'''February 5, 2019''' - Tom, Alex, Dani, Lars
 +
* Dani:
 +
** I-build contributed to 2019-03 M2, no complaints so far
 +
** Over 200 bugs for M3 with 2 weeks left, need to be looked at and target adjusted
 +
* Alex:
 +
** JIPPs are subject to update to new infra in the next few months. Releng JIPP is a matter of separate treatment.
 +
** As soon as most JIPPs (not Eclipse TLP only) are moved to new infra SWT will move to GTK 3.22 as a min version.
 +
** Sep 2019 release is the earliest possible for SWT GTK min version bump.
 +
* Tom:  
 +
** equinox.framework and bundles git repositories merge
 +
** APPROVED if history is preserved
 +
** Alex: new name of repo should be eclipse.equinox.* not rt.equinox
 +
** After merge Alex takes renaming rest of equinox repos with webmaster
 +
* Lars: Fosdem
 +
** IDE and Free Tools room
 +
** Netbeans and IntelliJ talks and interest
 +
 
 +
 
 +
'''January 29, 2019''' - McQ, Tom, Alex, Dani, Lars
 +
* Alex: Java 11, should we move the build to Java 11?
 +
** Agreed to move the Tycho snapshots for testing and move back to Tycho stable after M3
 +
* Dani: This week is M2, we will contribute the Wednesday I-Build with some sanity checks
 +
* Dani: Having problems with the asynchronous JDT UI initialization {{bug|543935}}
 +
 
 +
 
 +
'''January 22, 2019''' - McQ, Tom, Alex, Dani
 +
* Alex:Felix SCR update
 +
** Tom: Orbit update to make felix.scr bundle imports non-optional
 +
** Missing compile warning in the first build - not clear why it happened
 +
* Tom: Equinox tests move from runtime git repo
 +
** Needed because tests are not run on gerrit and not findable for contributors
 +
** Alex: how easy it is to find which one are for equinox and which should stay in runtime repo
 +
** Tom: to open bug with details
 +
 
 +
 
 +
'''January 15, 2019''' - McQ, Tom, Alex, Lars, Dani
 +
* Dani
 +
** We shipped 4.11 M1 last Friday - no issue so far
 +
** Created release record for 4.11 (mandatory to be there by 4.11 M1)
 +
 
 +
* Lars: {{bug|543218}} was a severe regression in M1
 +
 
 +
* Tom
 +
** Chatter about update configurator {{bug|542706}}
 +
** Alex: update configurator still there but not hooked into Equinox/p2/PDE anymore
 +
** Alex and Lars to update the bug report
 +
 
 +
 
 +
'''January 8, 2019''' - Dani, ?
 +
* We had a meeting, no notes were taken
 +
 
 +
 
 +
'''December 18, 2018''' - McQ, Tom, Alex, Dani
 +
* Talked about potential release train delay due to JAXB - nothing we have to worry about
 +
* Next call on January 8
 +
 
 +
 
 +
'''December 11, 2018''' - Tom, Lars, Dani
 +
* Dani: 4.10 looks good, work for 4.11 is open for development
 +
* Dani: Will add Bugzilla milestones
 +
* Tom: Will update Equinox to Java 8 soon will need to support Java 8 for quite some time in the future
 +
 
 +
 
 +
'''December 4, 2018''' - McQ, Alex, Tom, Lars, Dani
 +
* Dani away on Thursday and Friday.
 +
** Please keep an eye on RC2.
 +
** Please watch the release review ({{bug|541666}}).
 +
* Dani: 4.10 on good track but investigating last minute {{bug|542090}}.
 +
* {{Bug|541689}}: What needs to be done to add OpenJDK on Windows as a reference platform?
 +
** We will add this for now, but for 4.11 we will query the community which runtimes are actually used and/or tested.
 +
** Alex: We need to specify from where the OpenJDK runtime comes from.
 +
* Tom: When do we push 4.10 to Maven central?
 +
** Dani: ask on Releng list.
 +
* Alex: Help Center issue. What's the state?
 +
** Tom will investigate this a bit more this week. Probably no fix for RC2.
 +
 
 +
 
 +
'''November 27, 2018''' - Alex, Dani, McQ, Tom
 +
* Mailing lists
 +
** Discussion on merging various mailing lists {{bug|541508}}
 +
** Merge all platform-x lists into one (platform-dev?) list, except the current platform-releng-dev will remain separate.
 +
** merge all jdt lists into one list (jdt-dev?) list.
 +
** Considered merging the equinox-dev and p2-dev into one list (equinox-dev?), will leave separate for now because the two groups still seem to have distinct topics to discuss (even if the traffic is relatively low).
 +
** What is the target usage of the lists?  For the user community to ask questions or for the developers to have discussions around development of Eclipse?  At this point the traffic is low and the PMC does not see a need to discourage usage by the user community to ask questions.
 +
** Before merging we need a way to have responses sent to messages sent to the old archived mailing lists which directs them to the new list.
 +
* Rules for freeze/endgame
 +
** Consider allowing the gerrit reviews to act as the way to record approval by a member of the PMC and/or project lead instead of requiring that to be flagged in the bugzilla.  If the gerrit review was done by someone other than a member of the PMC or project lead then there still needs to be some record in the bugzilla that the required approval of the PMC or project lead was done.
 +
 
 +
 
 +
'''November 20, 2018''' - Alex, Lars, Dani, McQ
 +
* Dani reminded the team to update plans so we can do release review
 +
* Dani working on IP review
 +
* M3 this week; then API/feature freeze next week; then one more week and we’re done
 +
* JDT Code Mining went in today; test!; disabled by default
 +
* Demonstrated proof of concept, empty shell running on GTK4 alpha
 +
* {{bug|541307}} needs to be investigated; could be a blocker for PDE or Equinox
 +
* Seems to be general consensus that code clean-up is more important than maintaining git blame usefulness
 +
** Ref: https://www.eclipse.org/lists/eclipse-pmc/msg03568.html
 +
 
 +
 
 +
'''November 13, 2018''' - Alex, Lars, Dani, McQ
 +
* Plan update 4.10 plan update 1 from Dani
 +
** As Foundation still provides only SLES 12 we might still have to list it
 +
** SWT team tests on SLES15
 +
** Details: {{bug|541074}}
 +
* Train name update from Dani: We can keep "our" Eclipse IDE name, foundation dropped the idea of adding an additional identifier to the "Eclipse IDE" brand.
 +
* jsch - Dani checked if preferences are used and could not find any usage, Dani did not yet contact Thomas as JGit did not make any progress in the area. Alex did update Equinox.
 +
* Cherry-pick as strategy in Gerrit
 +
** {{bug|541021}}
 +
** Dani does not like the idea and voted against it
 +
** Alex: Linux tools and CDT are using Cherry-pick
 +
 
 +
-> Everyone agrees that the build infrastructure is getting worse and that we should find ways to speed up the build, Dani will follow-up with the foundation on that
 +
 
 +
 
 +
'''October 30, 2018''' - Alex, Lars, Dani, Tom
 +
* Dani: Update on release train name
 +
** Foundation accepts "Eclipse IDE" as long as the scope is clear
 +
** Foundation can use another name when the Eclipse IDE is shown along with other IDEs, e.g. Che. Possible name could be "Eclipse Classic IDE"
 +
* Increase major segment when deleting deprecated API
 +
** Discussed last year on [https://wiki.eclipse.org/Eclipse/PMC/Minutes_2017 October 10, 2017] but did not make an official decision
 +
** Disruption would be huge
 +
** Today we decided unanimously that in general we will NOT increase the major version when removing deprecated API
 +
*** There might be cases/bundles where we might be more aggressive
 +
 
 +
 
 +
'''October 23, 2018''' - No meeting due to EclipseCon Europe
 +
 
 +
 
 +
'''October 16, 2018''' - Alex, Lars, Dani, McQ
 +
* We all agreed that at this point, the right thing regarding renaming the project is to do nothing.
 +
* Delivered 2018-12 (4.10) M1 on Friday. No feedback on that so far. Train to deliver this Friday.
 +
* Dani gave an update on the work for the EDP.
 +
* Alex together with Mickael will make sure that the Unconference session at EclipseCon will be split into interest groups after initial discussion.
 +
 
 +
 
 +
'''October 9, 2018''' - Alex, Lars, Tom, Dani, McQ
 +
* 4.10 plan and release record published
 +
* 4.10 M1 looks good, low number of bugs
 +
* Project naming - pushback in planning council and there will be no change until Eclipse Foundation provides the document describing the rules names should comply with
 +
* Performance tests
 +
** Lars: jdt.core performance tests not running
 +
** Dani: performance tests running (mostly) since Photon, most work done by Sravan
 +
** Dani: results look sane but need to be checked thoroughly for some time to ensure all the infra runs proper
 +
** Alex: SWT perf tests for 4.9 properly shown improvement in startup initialization
 +
 
 +
 
 +
'''September 18, 2018''' - Alex, Lars, Dani, Tom, McQ
 +
* Release looks ok, respin was required
 +
* EPL 2.0 conversion was done for the Eclipse SDK but not for the e4 sub projects
 +
** Lars: e4 repository have not been converted
 +
** Dani: JDT, Equinox, PDE and Equinox have been converted so the Eclipse SDK has been converted
 +
** Lars plans to convert the e4 spies
 +
** Dani will inform Wayne/ Webmaster about the EPL 2.0 migration of the Eclipse SDK
 +
* Alex suggests deleting the long dead e4 repository like e4 JDT (no commits for 5 years, they should be archived) -> Alex to announce on e4 mailing list
 +
* Lars reports that SAP might get more involved, he delivered a workshop for them and they have very skilled developers which hopefully will contribute to the platform.
 +
* Dani: JDT will create a common plan for its components under https://wiki.eclipse.org/JDT/Plan/4.10, similar to platform.
 +
 
 +
 
 +
'''September 11, 2018''' - Alex, Lars, Dani, Tom
 +
* Dani: 4.9 Review is done and passed
 +
** Release is looking good for final phase
 +
** RC2 is done - no planned changes left for 4.9
 +
** Moving on for 4.10
 +
* Alex: 4.9 is in good shape now
 +
** Had last minute issues that almost made us miss RC2 date.  Felix SCR change in qualifier caused meta-data to be regenerated because of an upgrade in Tycho.  Tycho now published generic OSGi capabilities.  This lead to cases where Felix SCR would get included without equinox.ds.  That lead to issues with activating Felix SCR.
 +
** Tycho is fixed now to handle starting of Felix SCR, worked around issue for 4.9
 +
** For 4.10 dropped 32-bit and gtk2 now
 +
* Tom: org.eclipse.equinox.ds to be removed.  Decided to keep equinox.ds in the repository as part of the Equinox SDK feature, but it will not be shipped as part of the Eclipse SDK features.
 +
** Need to make sure other areas can handle equinox.ds missing (e.g PDE)
 +
* Dani: Informs us if the team attending Eclipse Day and EclipseCon events.
 +
* Via email: Pinging robot for bugs will be activated for all subcomponents of the Eclipse top level project, as it is currently not possible to activate the robot for only a sub-component.
 +
 
 +
'''September 04, 2018''' - Alex, Lars, McQ, Tom
 +
* CQ in JDT was approved to create code duplication. Lars asked what caused that.
 +
** Delay in JDT review, biggest blocker is still not in JDT
 +
** Large change, agreed with Dani to get review priority review in 4.10 from the JDT team
 +
* Alex/Tom - 4.9 RC2 status
 +
** Looks good, no know bugs
 +
* Lars: Activate autoclose for Platform bugs?
 +
** Lars argues that platform and e4 has too many old bugs so people are not looking at them
 +
** McQ is against autoclose
 +
** Agreed by al to enable "Pinging the user if this problem still exists" for selected components (Platform/UI) and see how much feedback we get.
 +
** Email send to McQ, Tom and Alex if we could also add e4 to that pinging list -> all agreed to enable it also for e4 bugs
 +
 
 +
'''August 28, 2018''' - Alex, Lars, Dani, Tom
 +
* Reminder - RC1 this week, RC2 next week
 +
* Dani on vacation starting this Friday
 +
* Dani will submit the release review and IP log before going on vacation (Wayne approved this)
 +
** Alex will handle all things that come up with that
 +
* EPL 2.0
 +
** Lars: almost done - few pending patches
 +
** Alex: boring work - hopefully EPL 3.0 only on 10 years
 +
 
 +
 
 +
'''August 21, 2018''' - Alex, Lars, Dani, Tom
 +
* Reminder - M3 this week RC1 next week
 +
* Milestone discussion
 +
** M2 and M3 are too close together.
 +
** Delivering M1 and M3 instead provides better space for the development team.
 +
** M1 will be short, but still should give us 1 month time to deliver. 
 +
** For 4.10 we will try delivering M1 and M3 milestones.
 +
* Dani will look at submitting the release review and IP log early since he will be out during the week they are due.
 +
** Alex will cover if that cannot be done
 +
* EDP update - Arch council is making changes ... should ease some things. 
 +
** For example, decoupling the project review from a project release.  Project releases still will require IPLogs
 +
* Lots of bugs still open against 4.9.
 +
** Team needs to adjust milestones accordingly before 4.9 is done
 +
* Java 11
 +
** Work almost done to support Java 11.
 +
** Initial support will be delivered in Marketplace only (no 4.9a planned).
 +
** First official release with Java 11 support will be 4.10
 +
 
 +
 
 +
'''August 14, 2018''' - McQ, Alex, Lars, Dani, Tom
 +
* Changing our test framework to use JUnit 5 always ({{bug|531057}})
 +
** In progress: suites are running, but some tests are aborting
 +
** Reports should be fine in next build
 +
* Release review and IP log will be coming soon
 +
** M3 next week, then one week for RC1 and one week for RC2
 +
** A lot of bugs in the backlog that need to have their milestone re-assigned
 +
* Once we get a few releases under our belt using the new process, we should do a retrospective looking at burn rates, quality, etc.
 +
** The good news is we no longer have to maintain two streams and back port changes.
 +
* Support for J9 shared classes merged into Equinox
 +
** Will not update launcher to specify them for this release
 +
** Need to provide doc on how users can specify the options themselves (via eclipse.ini)
 +
* McQ away for two weeks
 +
 
 +
 
 +
'''August 7, 2018''' - McQ, Alex, Lars, Dani
 +
* Dani: outstanding plan topics:
 +
** Target platforms should use SLES 15 (instead of 12)
 +
*** Dani to talk to SWT team about this
 +
** Remove RHEL 7.4 (current is 7.5)
 +
*** all agree to this
 +
* McQ to send note about Windows 32-bit EOL
 +
* Alex: ASM breakage in master — issue in Orbit; should be in next iBuild
 +
* Dani: shipped M2 last week everything went well
 +
 
 +
 
 +
'''July 31, 2018''' - Dani, Tom, Alex
 +
* Dani: For quality reasons, suggests to have an official M3 (August 24) since after RC1 (August 31) we will only have 1 week left
 +
** all agree to this
 +
* Dani: Initial 4.9 plan is ready but no feedback so far
 +
 
 +
 
 +
'''July 10, 2018''' - McQ, Dani, Tom, Alex
 +
* 32 bit support
 +
** Harder to find 32 bit JVM
 +
** Devs are not supposed to work on 32 bit OSes anymore
 +
** Agreement to drop support for 32 bit but keep sources and build support for some period to give people time to bring it back
 +
* GTK 2.x support in SWT
 +
** Planned to be removed for 2018-12 release
 +
** Needed so GTK 4.x port can be started prior to 4.0 release so SWT needs a taken into account from GTK devs
 +
** Bugs are not being looked at for some time already and GTK 3 has been the default for years now.
 +
* 4.9 release
 +
** M1 is this week
 +
** Platform will contribute I-build with some basic testing but not the full milestone which is to be done for the only milestone which is to be delivered for M2 of the SimRel
 +
 
 +
 
 +
'''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 [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 - 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: [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 12:24, 14 January 2020

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

January 14, 2020 - McQ, Alex, Dani, Tom

  • Dani: Switch to SUSE Enterprise 15, team is in favor to drop 12
  • Dani: Plan updated to remove Windows 7
  • Alex: Felix Dependencies for SCR done
    • confirm fix for bug 544571
    • releng disruptions during update, but recovered. More disruptions expected as we update dependencies for March release.
    • broken builds, need to get a list of issues. Seems to be more infrastructure issues. Need to report back to the foundation. Example, the signing issue that broken the respin.
  • Some discussion about gitlab option at foundation. bug 537913
    • What happens to gerrit work flow for review?
    • Would dropping bugzilla happen or can we migrate all issues?
    • Without migration it is a no-go for us
    • Currently no plans to move Eclipse project to gitlab at this time.


January 7, 2020 - McQ, Alex, Dani, Tom, Lars

  • Dani: Created initial 4.15 plan - please have a look
  • Dani: Created release record for 4.15
  • Dani: Sent a note to teams to create their 4.15 plan items/bugs
  • Dani: Do we want to drop support for Windows 7 (remove from Target Environments only)
    • Unanimous decision: Yes
  • Dani: Discuss (again, see below) resolution for stale bugs
    • We want to ask the webmaster that stale bugs are directly closed. ACTION ITEM for Lars
    • We will only auto/mass close existing stale bugs with notification turned off
  • Change rules about x-internal exports (bug 553709)
    • Decision:
    • - Newly added internal packages should not use x-internal exports unless there are very good reasons
    • - For existing packages the x-internal export can be removed with PMC approval


December 10, 2019 - Alex, Dani, Tom, Lars

  • Dani: RC2a respin to be promoted today
  • Dani: 4.15 M1 approaching fast (January 10)
  • Dani: master is open
  • Dani: Version bumps done for now
    • Rebase if needed Gerrit makes it being able to push without version bumps and breaks next build
    • Tool needs improvement to collect all version bumps needed to make initial bumps faster
  • Dani: How to make milestones used more
    • Have latest and deny things that have been since M1 and no one reported till RC1
    • Consider having latest unstable aka milestone channel which can be used by users/integrators
  • Tom: Java 8 support dropped - no decision to be made now


December 3, 2019 - Alex, Dani, McQ, Lars

  • Dani: RC2 this week. Supposed to be the end of 4.14 for us.
  • Dani: Rules for exporting packages as outlined in Export-Package :
    • Background: bug 544977.
    • We need to discuss whether we want to relax those rules.
    • Tom to file a bug report.


November 26, 2019 - Alex, Dani, McQ

  • GTK minimum version being upgraded: 3.14 -> March; 3.22 -> June
  • Target environments upgraded for 4.14, PMC members please verify
  • Standalone SWT download was broken in M3; Fixed in RC1
  • Mac downloads are now being notarized
  • Red Hat team will help with release engineering work


November 19, 2019 - Tom, Alex, Lars, Dani

  • Bumping GTK minimum version for SWT
    • No bump has been done in the last 2 years
    • GTK 4 is starting to shape up. In preparation we need to move up. 3.14 minimal version from 3.10 for March 2020 release. Will allow styling to go through our CSS engine. Will address many bugs because we override the behavior. Allows us to remove dead code.
    • For June release move to 3.22 release directly. Wayland is useless under 3.20
    • Will confirm with the SWT team that this is ok, will have an answer next week. PMC agrees to proceed as long as the development team is OK with it.
  • Dani: Fighting with build
    • Orbit checksums were not redone in latest (working on fix)
    • Issues with Mac signing - been really unreliable bug 553205
  • Dani: No IPLog needed this release, will need to be at least every year and we will do it in March.
  • SWT patch for Windows, allows to theme the scrollbar. Patch is stale now?
    • Can the team look at the patch and rework? We can review but likely not rework. bug 444560


November 12, 2019 - Tom, Alex, Lars, Dani

  • M3 next week
    • Many open bugs targeted for 4.14 M3 and 4.14
    • Request for contributors to act on them and retarget
  • Gerrit reviews
    • Dedicated time to spend on review patches from non-commiters and non-employees of IBM and Red Hat
    • Time still to be considered
  • Dani to check whether IP Log and review are needed for 4.14
  • Official build runs with Java 11 now
    • This is the runtime JVM used by the build system, nothing in the deliverables should require Java 11
    • Tools are catching up, reports had to be modified to work with it
    • If there is any issue noticed in deliverables, reports, download pages ... - please open a bug report and add Alex on cc
  • Pack200 (tom)
    • Test whether everything is fine if pack200 is gone is pending
    • Companies shipping only packed files will face issues
    • Ship alternative pack200 implementation? - better look at alternative compression if so critical
    • Build tools (e.g. reports generator) are using Pack200 classes directly, that would be a problem in the future
    • Drop packed files requirement for SimRel
      • If/when contribution requires Java 14 it's the only feasible thing to do, to be clarified in requirements


October 29, 2019 - Tom, McQ, Alex, Lars, Dani

  • Dani
    • still working on the PPC64LE issue
    • EclipseCon was great, met lots of people, JDT team plans to do more reviews in the future
      • Dani: missed Lars, Mickael, Andrey and others
    • Wayne and Markus might not continue to work on the release train, so this may end up an automatic process or a new working group may be founding another person
  • General discussion about unmaintained projects and how to deal with that

October 15, 2019 - Tom, Alex, Dani

  • Shipped 4.13 M1 on time
  • Quickly discussed Wayne's plans to reduce his time for the Release Train
  • Next week EclipseCon (no Dani)


October 08, 2019 - Tom, McQ, Alex, Dani, Lars

  • PPC64LE machine
    • Downtimes experienced with current one and general warning that there might be more
    • McQ: how many downloads do we have?
      • Dani: probably more in products rather than IDE downloads
    • PPC64LE workstation on the market (https://www.raptorcs.com/content/TL2DS1/intro.html) and Fedora looks into adding PPC64LE desktop spin
  • Jetty update test failures
    • Tom to ask Raymond to help us with it
  • 4.14 plan created
    • To be published once we gather the work items
  • Release record created
  • M1 this week
  • Gerrit submit
    • AGREED: Switch to "Rebase if Necessary"
    • Alex to take care of contacting admins to see change implemented


October 01, 2019 - Tom, McQ, Alex, Dani, Lars

  • Dani to look into plan and release record for 4.14
  • Stale bug reports should be closed as WONTFIX if there is not a response to the stale bug flag
  • Changes on Gerrit to allow fast-forward merges
    • deferred to next week


September 24, 2019 - Tom, McQ, Alex, Dani

  • discussed enabling fail on warnings on JDT projects
    • Dani to clarify with Roland


September 17, 2019 - Tom, McQ, Alex, Dani

  • Crash issue on win32 - respin done
  • Java 13 GA
    • marketplace entry works with M3 and onwards
    • merge into master starting
  • 4.13 GA
    • looks goods so far, packages are there
    • macos notarization still in process for EPPs


September 10, 2019 - Tom, McQ, Alex, Lars, Dani

  • Gerrits are failing
    • one failed because of missing version increase, some appear to be tooling issues
    • change went in to API tooling, which may fix it
    • do not merge failing gerrits
  • Many thanks to those who worked through the weekend to fix the Mac signing issue!


September 3, 2019 - Tom, McQ, Alex, Lars

  • Discussed status of RC3
    • This Friday for Platform - two known issues being looked at
    • bug 550672 - Alex - Still no final solution to the problem. May result in backing out fix to bug 548002
    • bug 550606 - Tom - at first seemed like a major regression that could require a revert of fix to bug 548877. Alex - has been determined to be a very limited scenario that we feel is not blocking the release and does not warrant reverting to fix.
  • Discussion of download stats. Much improved over the past year and looks to be double what the Photon release was a year ago for the 2019-06 release.
    • Some thoughts on what has caused the increased interest. Lars - much work around quality and performance. Alex - a result of a broader community involvement and other development plugins for eclipse gaining popularity which drive Eclipse downloads.


August 27, 2019 - Tom, Dani, Alex, Lars

  • Dani - Status update
    • RC1 this Friday for Platform - on track
    • Still working on Notarize Mac app (bug 549814)
  • Dani on vacation next week, starting this Friday
    • ==> please watch out for approval requests for API and feature changes after RC1
  • Lars - new filter icon (bug 465914)
    • all agree to be willing to change the icon
    • Dani: not just a funnel, but maybe a combination of sieve and funnel, or a good sieve icon
    • Lars: will make some suggestion in the bug report
  • Lars - compare panel orientation: should we change the default to what's in Gerrit? (bug 501752)
    • Agreement to try in 4.14 M1


August 20, 2019 - Tom, Dani, Alex, Lars

  • Dani - Status update
    • Tests are looking good for M3
    • Dani team gave focus to new Search, found several UX issues, like shortcuts
    • NPE Bug in the JDT quick outline, got fixed and rebuild was triggered
    • Resource packs were donated by Redhat, IBM and vogella GmbH to platform, discussion how long it will take for the foundation to update
    • Dani to discuss the build infrastructure with the foundation
  • Parallel activation for the IDE - Tom
    • Tom stated that it will be very time consuming to enable this
    • Might cause lots of issues during startup, i.e. deadlocks or missing DI due to activation order
    • Result: definitely nothing we should just do, without seeing a clear benefit during startup and it would require lots of efforts to get this well tested
  • Process removal of views - Dani /Lars
    • NavigatorView is deprecated but plugin.xml extension is not deprecated as we have no means of doing that
    • Suggestion from Lars: Announcement of removal now and mark for deletion
    • Suggestion from Dani: Replace the implementation
    • Alex: Adding it to the label of the view

Result: Send out send to cross that we want to delete the view, outdate the label with "Deprecate" and mark it for deletion.

Tom: Do we need a way to deprecate an individual extension? Discussion about and general agreement that this would not help clients.

August 13, 2019 - Tom, Dani, Alex, Lars

  • Dani: Mass changes only up to M1?
    • Lars - If everyone agrees then post M1 changes can happen
    • Tom - What makes it a mass change?
    • Alex - doesn't see the need for timeline on guideline, just make it across the build
    • -1 review always blocks the merge until some agreement is made on the change
    • Committers are not required to have review and it is up to the committer to ask for a review
    • JDT has additional concerns because a branch is needed to do next Java release development. Should just be a restriction for JDT to decide when mass changes can be made.
    • Resolution:
      • Mass changes are requested not to be more than 50 files in general if they can be split up but ...
      • Don't force it to be split for cases it is difficult to do so
      • A committer can block a mass change (like any other change) with -1 if there are good arguments
      • Don't restrict mass changes to specific milestones
      • Cleanups are allowed at any time during development cycle
      • Should reviewers be added??
        • No adding reviewers is not required by committers
        • Project leads should monitor Gerrit queues - PMC agreed
  • General discussion about JDT team changes with Java release cycle ...
    • expect large changes for Java 14 (e.g. Valhalla)
  • Alex - What happens when our dependencies require java 11?
    • Particularly for help, Lucene and Jetty
  • Lars - Fix in toolbar (bug 549898) that exposed another bug that is old
    • If not fixed do we need to revert original issue?
  • Dani talks about resource packs and possibility of companies donating resources to the Eclipse Project: https://www.eclipse.org/lists/eclipse.org-project-leadership/msg00181.html


August 6, 2019 - McQ, Tom, Dani


July 30, 2019 - McQ, Alex, Dani

  • Nothing to discuss.


July 23, 2019 - McQ, Tom, Dani

  • Nothing to discuss.


July 16, 2019 - Alex, Tom

  • Bouncycastle MessageDigets plugin inclusion (bug 541781)
    • Alex: Which feature should contain it so it's published?
    • Tom: Let's discuss on the bundle but usability of current equinox features is questionable.
    • Alex: Let's sanitize them in this case.
    • Tom: +1, we need to figure what the deprecation policy (if any) there is for features.
  • Merge of rt.equinox.bundles and framework git repos
    • Tom: still interested in it but very low priority
    • Alex: interested in it for the sake of rename of repos from rt.equinox to eclipse.equinox


July 9, 2019 - Dani, Tom

  • Dani: M1 this week. Looks good so far.
  • We will not suspend the calls during summer.


July 2, 2019 - Alex, Tom

  • General chat about bugzilla vs gerrit only workflow. No binding decisions due to lack of quorum.


Jun 25, 2019 - Alex, Lars

  • General chat about state of affairs due to lack of quorum


Jun 18, 2019 - McQ, Lars, Tom

  • The 1.5 minute start up time issue (Windows Defender) needs to be investigated
    • Is this related to the signing problem?
    • What do we have to do to be "blessed" by Microsoft?
      • Dani: Not sure this is the solution as we do not even know what the problem is
  • There is a perception that Eclipse on Windows is not as smooth/performant as Linux now
    • This is a bit troubling, since windows is still our most significant platform (by downloads)
    • Do we need to look for ways to increase participation in SWT on Win?
  • Do we need better coding pattern/style guidelines?


Jun 11, 2019 - McQ, Dani, Alex, Lars, Tom

  • 2019-06 release
    • RC2 shipped on time
    • No pending request
    • Lars: Opening next release stream - felt too long due to amount of incoming gerrits. It's a nice problem to have but no change planned on the topic so far.
  • Gerrit down
    • Dani called webmaster, negotiated it to be made tier 1
  • Emeritus status for historical committers
    • Foundation is dropping the feature overall so no plans to nominate new people from the last group of removed committers
  • No bug report policy
    • Simple fixes do not require bug report
    • Dani: larger patches to require bug
    • McQ: reviewer should the have the right to request
    • Alex: requiring too many bugzillas is against young population used to github
    • AGREED - we stay as we are and reviewer has the right to ask for one if he feels the need
  • New committer process document - whoever has a comment to comment on the document
  • Modern eclipse
    • McQ: how to define what to work on without too much bias
    • Alex: new intern working on inline editing - an initiative to serve as example of modernization
    • AGREED - come up with list of things to work on
    • ACTION ITEM: Lars: to create initial document for list of things/initiatives
  • Dani not on call for the next 3 times (Eclipse Board meeting, manager training and vacation)


May 28, 2019 - McQ, Dani, Alex, Lars, Tom

  • http client issue
    • should we ship old and new?
    • we initially decided to only ship new one.
    • ship old only gives ability to revert back, but still requires work on client
    • if a fix isn't available for using the new http client then we will consider shipping only the old one for 4.12
    • others can install the new http client if they want to try it out
  • message to Stephan
    • Note set, no additional information or status available
  • heading into RC builds for 4.12
    • end game plan created
    • finalizing the plan and closed after updating target environments
  • discussed bug 547011
    • decided to bump event bundle version to work around
    • need a new bug opened to enable us to detect this situation earlier
  • Major version increase on API removal discussion
    • announced API removals will not cause major version bumps
    • This potentially breaks others
    • We only do this on announced deprecations for 3 years.
  • Future of Eclipse IDE (McQ)
    • Power users for writing code. A lot still use vanilla text editor ...
    • What is the value of the IDE in today's environment. Deployment and monitor of applications is more important.
    • Are we not addressing the problems of today to make Eclipse the power tool of today.
    • Do we need support for new languages.
    • Language server help?
    • can we find some set of things to do to reduce friction to using Eclipse IDE?
    • remove notion of project natures?
    • asynchronous operations can help?
    • Make our lists of top things to do
    • get community involvement on prioritizing the list of important things to improve.
  • Alex out next week

May 21, 2019 - McQ, Dani, Alex, Lars

  • Dani
    • M3 is this week, need to watch out for bugs and issues
    • New feature to make modal dialogs non-modal created a blocker but this has been fixed
    • Endgame plan will be send out by Dani by the end of this week
    • We only ship an HttpClient45 implementation with the latest ECF and no HttpClient4 anymore which may cause issue. Dani's team will send out a note tomorrow, Alex thinks that this should not create an issue
    • Release restrictions from the foundation are less strict for the next release (no IP log and release review for every release required anymore), we will follow this process
  • Discussion about Stephan Herrmann's email to the PMC and we need to check with Stephan
    • IBM may have an option to provide service releases
    • We should also look at the bug system to see what is important to the users

May 14, 2019 - McQ, Dani, Alex, Tom

  • No complaints about our M2 delivery so far
  • M3 is next week
    • 200 bugs still open
    • People are just bumping them to the next milestone
    • Better to remove target milestone if you don’t actually believe it will be fixed by then
  • Jetty dev list note:
  • Batik update — 4 of 5 CQs approved should be in for M3


May 7, 2019 - McQ, Lars, Dani, Alex

  • Gerrit verification jobs to give -1 on warnings
    • Dani: not easy, single file with warnings in Jenkins for all type of warnings
    • PMC is in favor of such solution but there are technical limitations to achieve it or it would require significant effort to get to warning free builds
  • ECF http client update
    • Dani: prefer to ship both old and new implementation, fine with new one only and reconsider
    • Alex: not in favor of shipping two implementations as that would make the testing harder, prefer to ship single one and that being the new one, reconsider if there is issue
    • ACTION: Dani to reply to Scott that Eclipse SDK will ship latest only and we would like to have it for testing purposes ASAP
  • Inactive committers
    • Dani: Notification sent and inactive committers that want to keep commit rights can do it now
  • 2019-06 M2
    • Dani: I-build delivered to M2
  • Dependency updates
    • Alex: Jetty is in progress to 9.4.18, permissions to publishing the version to p2 repo on behalf of Jetty project granted
    • Alex: Batik - work in progress


April 30, 2019 - McQ, Tom, Lars, Dani

  • M2 for us this week - will only contribute last good I-build - no real milestone week
  • Extend fast track for committers for all projects not just inactive ones
    • Tom: already following the proposed process
    • We can't force committers to accept a new committer (against EDP)
    • Unanimous decision to drop fast track program. Mentor/committer can propose any contributor if he can justify the nomination
  • Request for review on JDT mailing list
    • Wait for Stephan to respond for a day or two
    • Dani to contact Stephan if no response


April 23, 2019 - McQ, Alex, Dani, Tom

  • M1 train has been published but no official announcement was sent
  • Alex to update Jetty with latest security fixes


April 16, 2019 - Lars, Dani, Tom, McQ

  • M1 has shipped -- Lots of good stuff, see the N&N
  • Plan has been posted
    • Attempt to simplify the creation process, still WIP
  • Started working on identifying inactive committers
    • Inactive == haven't committed anything for 2 years
  • Looking at ways to ensure we have enough testing of new Java features
    • Main projects should run on widest ranges of versions, so can't just raise BREE there
    • Could add new test projects, and allow tests to be written with new constructs


April 9, 2019 - Alex, Dani, Tom, McQ

  • Dani
    • Lots of regressions Dani investigating
      • cycle from tests (fixed)
      • UI elements gone missing (fixed)
    • Get rid of the new index from JDT
      • Needs lots of polish to get rid of bugs, but never showed performance improvements.
      • Decided to disable the option to use it (code remains). Open to others to help maintain.
    • Created initial 2019-06 (4.12) plan
      • Still need individual plan bugs from leads (cough Equinox).
    • Created initial release record for 2019-06 (4.12)
    • Made a call for plan items for 2019-06 (4.12)
    • M1 this week
      • Looks good so far.
  • Tom
    • Investigating parallel activation of bundles bug 540507
  • Alex
    • M1 fixes for SWT
      • Fixes for other things in M1 some small regression in custom Linux environment.
    • M1 jsch update needed
    • Tom to Open bug for Apache Felix SCR update post M1
    • SWT issue
      • SVG image support for Linux-only to start. Need support for other platforms.
      • Windows has a number of patches pending. (mostly cleanup patches?)
      • Try to get more people on board for Windows support help.
      • Ask for help on the platform list. We have combined the projects and have more devs available to work on SWT if they are willing to help.
      • For cleanup you need specific SWT knowledge.
        • two types of cleanup - use quick fix from Eclipse - and real refactoring.
    • If we are to advance SWT development then we cannot continue with a single committer on a platform. Need to promote the recruitment of new SWT committers.


April 2, 2019 - McQ, Dani, Lars, Tom

  • Planning for this release has started
    • Sub-projects need to have first cut of plan ready by a week from Friday
  • Also a week from Friday is our M1
  • Based on community feedback we will keep the update site for adding Java 11 support to the 2018-09 (4.9) release, the Marketplace entry remains removed


March 26, 2019 - McQ, Dani, Alex, Tom

  • Dani
    • Inactive committer cleanup progress.
      • It is now harder. Portal has been deactivated and the functionality to get inactive committers is gone.
      • Looking to use some script originated by Lars for list of contributors.
      • What is the timeline to be considered inactive again? Ans. A year of inactivity will trigger the question.
  • Alex
    • Confirms that the new indexer has no value to Red Hat (see also March 5 and bug 544898)
    • bug 545032 Implement native ImageLoader (Linux only)
      • Allows additional formats not previously supported to work with the native Linux implementation of SWT
      • What kind of error message will be available on other platforms?
      • Need to confirm the API doc is updated to indicate what formats are supported on what platforms. (Alex will take care of that in the javadoc)
      • Has there been investigation into what later Java versions provide for image loading?
        • No, could be done as part of investigating support on other platforms.
      • Need to have an umbrella bug for the new functionality with additional children defects for the platforms that don't support the new formats. (Alex to open that)


March 19, 2019 - McQ, Lars, Dani

  • Dani
    • 4.11 on track - repositories and download page ready for tomorrow
    • Java 12 GA expected today
    • Will merge Java 12 work to master tomorrow or on Thursday
    • Will provide a Marketplace entry for Java 12 support for 4.11


March 12, 2019 - ???

  • Missing


March 5, 2019 - Tom, Alex, Dani

  • Dani
    • I will be away starting Friday and next week. No laptop ==> watch out for any 4.11 related issues
    • Tom, please update the status on the Equinox 4.11 plan
    • Tom: bug 544370: NoClassDefFoundError: org/apache/sshd/server/auth/AsyncAuthException from SshServ
    • bug 544833: Inactive committer cleanup for Platform for the 4.12 release
      • Might be much more work since committer info from old portal is not available in the new PMI
    • Get rid of new indexer. Alex, not sure who from Red Hat mentioned it at EclipseCon Europe but there seemed to be interest to further work on this.
      • Alex: Roland looked at it and could not see any benefit
      • Current thinking: drop it, but Alex will double-check and report back in two weeks


February 26, 2019 - McQ, Tom, Alex, Lars, Dani

  • Dani
    • Issues with Mac signing
      • McQ: we should ask the Foundation whether they can't set up a watchdog
    • Issues with JAR signing
    • Release on track
    • Prune inactive committers
      • AGREED to do this like we did last year for Platform (bug 530200)
      • Lars for Platform. Tom for Equinox and Dani for JDT and PDE
  • Lars: move active committers to the list of contributors in the Acknowledgments
    • AGREED


February 19, 2019 - Tom, Alex, Dani, Lars

  • Lars: API removal announcement on cross project
    • AGREED: To send one mail per release for RC1 announcing all removals to reduce noise on the mailing list
    • In case of more important removal it can be announced individually.
    • Dani to open bugs for releases so it's handled properly.
  • Lars: Provisional API guidelines changes
    • Current approach with internal/provisional package names until API is stable is an issue because:
      • It creates more work for maintainers to rename packages.
      • It creates more work for adopters to change references once API is stable.
    • AGREED: Use the intended package name but mark it as x-internal until API is final. Lars will update the document.
  • Dani: End game plan posted


February 12, 2019 - Tom, Alex, Dani, Lars

  • Dani:
    • M3 next week.
    • Must start to work on IP log, release review and Endgame plan.
  • Alex: What's the future of ECF (not much happening there)? How feasible is it to replace ECF and HttpClient with new Java HTTP Client from Java 11?
    • Interesting to know, but unfortunately no resources to investigate this at the moment.
  • PMC decision regarding HttpClient for 2019-03: will ship what we have (4.5.5).


February 5, 2019 - Tom, Alex, Dani, Lars

  • Dani:
    • I-build contributed to 2019-03 M2, no complaints so far
    • Over 200 bugs for M3 with 2 weeks left, need to be looked at and target adjusted
  • Alex:
    • JIPPs are subject to update to new infra in the next few months. Releng JIPP is a matter of separate treatment.
    • As soon as most JIPPs (not Eclipse TLP only) are moved to new infra SWT will move to GTK 3.22 as a min version.
    • Sep 2019 release is the earliest possible for SWT GTK min version bump.
  • Tom:
    • equinox.framework and bundles git repositories merge
    • APPROVED if history is preserved
    • Alex: new name of repo should be eclipse.equinox.* not rt.equinox
    • After merge Alex takes renaming rest of equinox repos with webmaster
  • Lars: Fosdem
    • IDE and Free Tools room
    • Netbeans and IntelliJ talks and interest


January 29, 2019 - McQ, Tom, Alex, Dani, Lars

  • Alex: Java 11, should we move the build to Java 11?
    • Agreed to move the Tycho snapshots for testing and move back to Tycho stable after M3
  • Dani: This week is M2, we will contribute the Wednesday I-Build with some sanity checks
  • Dani: Having problems with the asynchronous JDT UI initialization bug 543935


January 22, 2019 - McQ, Tom, Alex, Dani

  • Alex:Felix SCR update
    • Tom: Orbit update to make felix.scr bundle imports non-optional
    • Missing compile warning in the first build - not clear why it happened
  • Tom: Equinox tests move from runtime git repo
    • Needed because tests are not run on gerrit and not findable for contributors
    • Alex: how easy it is to find which one are for equinox and which should stay in runtime repo
    • Tom: to open bug with details


January 15, 2019 - McQ, Tom, Alex, Lars, Dani

  • Dani
    • We shipped 4.11 M1 last Friday - no issue so far
    • Created release record for 4.11 (mandatory to be there by 4.11 M1)
  • Tom
    • Chatter about update configurator bug 542706
    • Alex: update configurator still there but not hooked into Equinox/p2/PDE anymore
    • Alex and Lars to update the bug report


January 8, 2019 - Dani, ?

  • We had a meeting, no notes were taken


December 18, 2018 - McQ, Tom, Alex, Dani

  • Talked about potential release train delay due to JAXB - nothing we have to worry about
  • Next call on January 8


December 11, 2018 - Tom, Lars, Dani

  • Dani: 4.10 looks good, work for 4.11 is open for development
  • Dani: Will add Bugzilla milestones
  • Tom: Will update Equinox to Java 8 soon will need to support Java 8 for quite some time in the future


December 4, 2018 - McQ, Alex, Tom, Lars, Dani

  • Dani away on Thursday and Friday.
    • Please keep an eye on RC2.
    • Please watch the release review (bug 541666).
  • Dani: 4.10 on good track but investigating last minute bug 542090.
  • bug 541689: What needs to be done to add OpenJDK on Windows as a reference platform?
    • We will add this for now, but for 4.11 we will query the community which runtimes are actually used and/or tested.
    • Alex: We need to specify from where the OpenJDK runtime comes from.
  • Tom: When do we push 4.10 to Maven central?
    • Dani: ask on Releng list.
  • Alex: Help Center issue. What's the state?
    • Tom will investigate this a bit more this week. Probably no fix for RC2.


November 27, 2018 - Alex, Dani, McQ, Tom

  • Mailing lists
    • Discussion on merging various mailing lists bug 541508
    • Merge all platform-x lists into one (platform-dev?) list, except the current platform-releng-dev will remain separate.
    • merge all jdt lists into one list (jdt-dev?) list.
    • Considered merging the equinox-dev and p2-dev into one list (equinox-dev?), will leave separate for now because the two groups still seem to have distinct topics to discuss (even if the traffic is relatively low).
    • What is the target usage of the lists? For the user community to ask questions or for the developers to have discussions around development of Eclipse? At this point the traffic is low and the PMC does not see a need to discourage usage by the user community to ask questions.
    • Before merging we need a way to have responses sent to messages sent to the old archived mailing lists which directs them to the new list.
  • Rules for freeze/endgame
    • Consider allowing the gerrit reviews to act as the way to record approval by a member of the PMC and/or project lead instead of requiring that to be flagged in the bugzilla. If the gerrit review was done by someone other than a member of the PMC or project lead then there still needs to be some record in the bugzilla that the required approval of the PMC or project lead was done.


November 20, 2018 - Alex, Lars, Dani, McQ

  • Dani reminded the team to update plans so we can do release review
  • Dani working on IP review
  • M3 this week; then API/feature freeze next week; then one more week and we’re done
  • JDT Code Mining went in today; test!; disabled by default
  • Demonstrated proof of concept, empty shell running on GTK4 alpha
  • bug 541307 needs to be investigated; could be a blocker for PDE or Equinox
  • Seems to be general consensus that code clean-up is more important than maintaining git blame usefulness


November 13, 2018 - Alex, Lars, Dani, McQ

  • Plan update 4.10 plan update 1 from Dani
    • As Foundation still provides only SLES 12 we might still have to list it
    • SWT team tests on SLES15
    • Details: bug 541074
  • Train name update from Dani: We can keep "our" Eclipse IDE name, foundation dropped the idea of adding an additional identifier to the "Eclipse IDE" brand.
  • jsch - Dani checked if preferences are used and could not find any usage, Dani did not yet contact Thomas as JGit did not make any progress in the area. Alex did update Equinox.
  • Cherry-pick as strategy in Gerrit
    • bug 541021
    • Dani does not like the idea and voted against it
    • Alex: Linux tools and CDT are using Cherry-pick

-> Everyone agrees that the build infrastructure is getting worse and that we should find ways to speed up the build, Dani will follow-up with the foundation on that


October 30, 2018 - Alex, Lars, Dani, Tom

  • Dani: Update on release train name
    • Foundation accepts "Eclipse IDE" as long as the scope is clear
    • Foundation can use another name when the Eclipse IDE is shown along with other IDEs, e.g. Che. Possible name could be "Eclipse Classic IDE"
  • Increase major segment when deleting deprecated API
    • Discussed last year on October 10, 2017 but did not make an official decision
    • Disruption would be huge
    • Today we decided unanimously that in general we will NOT increase the major version when removing deprecated API
      • There might be cases/bundles where we might be more aggressive


October 23, 2018 - No meeting due to EclipseCon Europe


October 16, 2018 - Alex, Lars, Dani, McQ

  • We all agreed that at this point, the right thing regarding renaming the project is to do nothing.
  • Delivered 2018-12 (4.10) M1 on Friday. No feedback on that so far. Train to deliver this Friday.
  • Dani gave an update on the work for the EDP.
  • Alex together with Mickael will make sure that the Unconference session at EclipseCon will be split into interest groups after initial discussion.


October 9, 2018 - Alex, Lars, Tom, Dani, McQ

  • 4.10 plan and release record published
  • 4.10 M1 looks good, low number of bugs
  • Project naming - pushback in planning council and there will be no change until Eclipse Foundation provides the document describing the rules names should comply with
  • Performance tests
    • Lars: jdt.core performance tests not running
    • Dani: performance tests running (mostly) since Photon, most work done by Sravan
    • Dani: results look sane but need to be checked thoroughly for some time to ensure all the infra runs proper
    • Alex: SWT perf tests for 4.9 properly shown improvement in startup initialization


September 18, 2018 - Alex, Lars, Dani, Tom, McQ

  • Release looks ok, respin was required
  • EPL 2.0 conversion was done for the Eclipse SDK but not for the e4 sub projects
    • Lars: e4 repository have not been converted
    • Dani: JDT, Equinox, PDE and Equinox have been converted so the Eclipse SDK has been converted
    • Lars plans to convert the e4 spies
    • Dani will inform Wayne/ Webmaster about the EPL 2.0 migration of the Eclipse SDK
  • Alex suggests deleting the long dead e4 repository like e4 JDT (no commits for 5 years, they should be archived) -> Alex to announce on e4 mailing list
  • Lars reports that SAP might get more involved, he delivered a workshop for them and they have very skilled developers which hopefully will contribute to the platform.
  • Dani: JDT will create a common plan for its components under https://wiki.eclipse.org/JDT/Plan/4.10, similar to platform.


September 11, 2018 - Alex, Lars, Dani, Tom

  • Dani: 4.9 Review is done and passed
    • Release is looking good for final phase
    • RC2 is done - no planned changes left for 4.9
    • Moving on for 4.10
  • Alex: 4.9 is in good shape now
    • Had last minute issues that almost made us miss RC2 date. Felix SCR change in qualifier caused meta-data to be regenerated because of an upgrade in Tycho. Tycho now published generic OSGi capabilities. This lead to cases where Felix SCR would get included without equinox.ds. That lead to issues with activating Felix SCR.
    • Tycho is fixed now to handle starting of Felix SCR, worked around issue for 4.9
    • For 4.10 dropped 32-bit and gtk2 now
  • Tom: org.eclipse.equinox.ds to be removed. Decided to keep equinox.ds in the repository as part of the Equinox SDK feature, but it will not be shipped as part of the Eclipse SDK features.
    • Need to make sure other areas can handle equinox.ds missing (e.g PDE)
  • Dani: Informs us if the team attending Eclipse Day and EclipseCon events.
  • Via email: Pinging robot for bugs will be activated for all subcomponents of the Eclipse top level project, as it is currently not possible to activate the robot for only a sub-component.

September 04, 2018 - Alex, Lars, McQ, Tom

  • CQ in JDT was approved to create code duplication. Lars asked what caused that.
    • Delay in JDT review, biggest blocker is still not in JDT
    • Large change, agreed with Dani to get review priority review in 4.10 from the JDT team
  • Alex/Tom - 4.9 RC2 status
    • Looks good, no know bugs
  • Lars: Activate autoclose for Platform bugs?
    • Lars argues that platform and e4 has too many old bugs so people are not looking at them
    • McQ is against autoclose
    • Agreed by al to enable "Pinging the user if this problem still exists" for selected components (Platform/UI) and see how much feedback we get.
    • Email send to McQ, Tom and Alex if we could also add e4 to that pinging list -> all agreed to enable it also for e4 bugs

August 28, 2018 - Alex, Lars, Dani, Tom

  • Reminder - RC1 this week, RC2 next week
  • Dani on vacation starting this Friday
  • Dani will submit the release review and IP log before going on vacation (Wayne approved this)
    • Alex will handle all things that come up with that
  • EPL 2.0
    • Lars: almost done - few pending patches
    • Alex: boring work - hopefully EPL 3.0 only on 10 years


August 21, 2018 - Alex, Lars, Dani, Tom

  • Reminder - M3 this week RC1 next week
  • Milestone discussion
    • M2 and M3 are too close together.
    • Delivering M1 and M3 instead provides better space for the development team.
    • M1 will be short, but still should give us 1 month time to deliver.
    • For 4.10 we will try delivering M1 and M3 milestones.
  • Dani will look at submitting the release review and IP log early since he will be out during the week they are due.
    • Alex will cover if that cannot be done
  • EDP update - Arch council is making changes ... should ease some things.
    • For example, decoupling the project review from a project release. Project releases still will require IPLogs
  • Lots of bugs still open against 4.9.
    • Team needs to adjust milestones accordingly before 4.9 is done
  • Java 11
    • Work almost done to support Java 11.
    • Initial support will be delivered in Marketplace only (no 4.9a planned).
    • First official release with Java 11 support will be 4.10


August 14, 2018 - McQ, Alex, Lars, Dani, Tom

  • Changing our test framework to use JUnit 5 always (bug 531057)
    • In progress: suites are running, but some tests are aborting
    • Reports should be fine in next build
  • Release review and IP log will be coming soon
    • M3 next week, then one week for RC1 and one week for RC2
    • A lot of bugs in the backlog that need to have their milestone re-assigned
  • Once we get a few releases under our belt using the new process, we should do a retrospective looking at burn rates, quality, etc.
    • The good news is we no longer have to maintain two streams and back port changes.
  • Support for J9 shared classes merged into Equinox
    • Will not update launcher to specify them for this release
    • Need to provide doc on how users can specify the options themselves (via eclipse.ini)
  • McQ away for two weeks


August 7, 2018 - McQ, Alex, Lars, Dani

  • Dani: outstanding plan topics:
    • Target platforms should use SLES 15 (instead of 12)
      • Dani to talk to SWT team about this
    • Remove RHEL 7.4 (current is 7.5)
      • all agree to this
  • McQ to send note about Windows 32-bit EOL
  • Alex: ASM breakage in master — issue in Orbit; should be in next iBuild
  • Dani: shipped M2 last week everything went well


July 31, 2018 - Dani, Tom, Alex

  • Dani: For quality reasons, suggests to have an official M3 (August 24) since after RC1 (August 31) we will only have 1 week left
    • all agree to this
  • Dani: Initial 4.9 plan is ready but no feedback so far


July 10, 2018 - McQ, Dani, Tom, Alex

  • 32 bit support
    • Harder to find 32 bit JVM
    • Devs are not supposed to work on 32 bit OSes anymore
    • Agreement to drop support for 32 bit but keep sources and build support for some period to give people time to bring it back
  • GTK 2.x support in SWT
    • Planned to be removed for 2018-12 release
    • Needed so GTK 4.x port can be started prior to 4.0 release so SWT needs a taken into account from GTK devs
    • Bugs are not being looked at for some time already and GTK 3 has been the default for years now.
  • 4.9 release
    • M1 is this week
    • Platform will contribute I-build with some basic testing but not the full milestone which is to be done for the only milestone which is to be delivered for M2 of the SimRel


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