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)
(269 intermediate revisions by 5 users not shown)
Line 10: Line 10:
  
 
= Meeting Minutes =
 
= Meeting Minutes =
−
'''Decemeber 12, 2017''' - McQ, Alex, Lars, Dani, Tom
 
−
* P2 capabilities work breaking Oomph and CBI ({{bug|528408}})
 
−
** Alex: Hidden bug due to adopters using internals.
 
−
** Alex: Code refactoring in p2 pushed to reduce the chance for such breakage.
 
−
** Alex: Oomph fixed its codebase to properly check instances so it works with p2 both prior and after adding capabilities.
 
−
** McQ: What do we do with p2?
 
−
** Alex: Open up the project as much as we can and recruit new committers by being really welcoming to people.
 
  
−
-> Conclusing to not respin M4 due to this bug as it's internal API which projects should not have used.
+
'''Mar 31, 2021''' - McQ, Tom, Alex, Lars
 +
* Java 16 jar signing issue
 +
** Tom wants to replace equinox implementation with builtin Jar file implementation so changes don't have to be done in Equinox on each release
 +
* JSP/Jetty story in IDE
 +
** Do we still need same functionality?
 +
** Alex - get out of the business for help system. Dependencies (jetty, lucene) generate more releng work than we can handle.
 +
** McQ - url for plugin help would be simplest and open it in browser
 +
** Any change (e.g. JSP removal) has to go through standard deprecation period, announcements and etc.
 +
** Alex to initiate communication on longer term plan with Holger who works on improvements to help system lately
  
−
* Project plan update
 
−
** Dani: No additional change came from anyone else in the PMC so update of executions environments is the only thing due.
 
  
−
'''Decemeber 05, 2017''' - McQ, Alex, Lars, Dani, Tom
+
'''Mar 31, 2021''' - McQ, Tom, Alex
−
* Vacation: Dani will be in vacation end of week, so other PMC member need to cover for him if something comes up for M4.
+
  
−
* Discussion about adding EGit to the SDK? ({{bug|528004}})
+
* PMC call time
−
** Dani using a shared installed to manage the EGit plug-in.
+
** Overlaps with Planning council call and both Tom and Alex can't make both
−
** McQ explains that he thinks EGit is required for a full package but does not feel strong about.
+
-> Decision: Skip PMC call every first Wed of the month
−
** Alex: It depends what "SDK" means: SDK to develop plug-ins or SDK to develop Eclipse Platform. We agreed on the former.
+
−
** Dani, Alex are against adding it because it adds maintaince burden and it is unclear which of the optional packages should be installed.
+
−
** Tom, Lars have no strong opinions
+
−
** All agree that managing to install this is an easy task
+
  
−
-> Conclusing to not include EGit in the SDK
+
* Webpage Hugo migration
 +
** Recommended by Eclipse Foundation and active contributor to do the conversion
 +
** Concerns about mixing old and new content are raised but they don't look severe
 +
** Supported by PMC
 +
-> Tom to handle initial communication on behalf of PMC
  
−
* Impact of cross discussion from David about API changes in which David implied that the platform cannot do API breakages
+
* Planning process relevance
−
** Dani clarified with David on the cross-mailing list, no changes for us for the process, as we only remove announced. See https://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg15032.html
+
** the planning process is not providing the detailed and usable plans from the past
 +
** not a pain point as fewer people participate it but looks like useless exercise quite often
 +
** to be discussed....
  
−
* URL handler registration of Eclipse with the OS
 
−
** SAP plans to contribute a way to register Eclipse to certain URLs. If the user clicks on such a URL, Eclipse would open and be able to show the file. This could be useful for installation of new items in the marketplacen client https://bugs.eclipse.org/bugs/show_bug.cgi?id=527579. VSCode allows this already vscode:extension/eamodio.gitlens.
 
−
** Redhat had similar requirements in the past
 
−
** Platform team expects that SAP will also maintain this contribution and take responsibility of it for future releases
 
−
** Dani (after meeting): I think extending the current file based mechanism is OK, but we won't register any (including URL) handler
 
  
−
-> Conclusion to work on this enhancement together with SAP, Alex plans to dedicate some time for discussing the technical solution. SAP should open a new bug and link all related bugs to this top-level bug so that the technical details can be discussed
+
'''Mar 24, 2021''' - Tom, Alex, Lars
  
−
* Discussion of building natives
+
* Pack 200 - API removal in 2 years - 2023-06
−
** moved building of SWT binaries for the 3 primary platforms to the Eclipse Foundation
+
** Should we turn off all pack 200 features in one year, make it consistent across all Java versions.
−
** unfortunately after that the Mac went down - fixed now
+
** 2022-06 - disable pack200 for all Java versions. Calling the deprecated API will be a no-op
−
** M4 SWT natives will be built on the Eclipse Foundation hardware
+
−
** Launcher still to be moved
+
  
−
'''November 28, 2017''' - McQ, Alex, Lars, Dani
+
* Pack 200 - When can we stop generating? Agreed on 2021-09 release. We should set the precedence as early as possible to stop producing pack200 artifacts.
−
* Alex: Release Change announcement
+
−
** Agreed that we won't mention the ramp-down process.
+
−
** Agreed to add API removal details.
+
−
** Still work in progress.
+
−
* Dani: API Removal process for the new release model
+
−
** Agreed to allow removal announcement in ever of the 4 releases. As a consequence every release can have API removals.
+
−
** https://wiki.eclipse.org/Eclipse/API_Central/Deprecation_Policy already reflects this.
+
−
* Dani: Meeting notes
+
−
** McQ suggested that who joins last has to do it. Dani: not so good since it won't contain the notes for the discussions that happened before.
+
−
** Will do it based on rotation and ability to actually write down the notes.
+
−
** Dani to do it for this call.
+
−
* Dani: Photon plan update
+
−
** Will add Java 9 as supported VM.
+
−
** Anything else? If so, send Dani a note or update {{bug|527964}}
+
−
* McQ: Rename Eclipse Project to Eclipse SDK
+
−
** We should only do it when forced by the Foundation and/or Board
+
−
** We would need a plan before starting such an effort.
+
  
−
'''November 14, 2017''' - Dani, McQ, Alex, Tom
+
* split packages
−
* Dani:
+
** Causing issues with mandatory directive and p2 {{bug|360659}} and with tycho.
−
** Presented our new release model to Planning Council. Was welcomed. No objections. But needs discussion what the Release Train will do.
+
** Currently tycho requires some work arounds for usage of split packages
−
** RC1 went well, RC2 this week.
+
** Can we work to get rid of split packages. We agreed to investigate the work and move to combine split packages if possible.
  
−
'''November 07, 2017''' - 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. Development is possible until RC1, so this will result in a freeze period of approx. 2 weeks.
 
−
* For releases versions of the platform we will use semantic versioning as before (4.8, 4.9, 4.10, ..)
 
−
* Eclipse SDK will use versions not branding names unless the release train moves also the same cycle.
 
−
* Splash will continue show the release year and month
 
  
−
'''October 31, 2017''' - Dani, McQ, Martin, Alex,
+
'''Mar 17, 2021''' - McQ, Tom, Alex, Lars
−
* Tom: '''Bugzilla Landing Page''' - EMO said both PMCs need to be contacted
+
* SWT Chromium support
−
** Bug IDs, Equinox product and components remain in place, only the landing page will be updated
+
** Still no recent version of Chromium with security patches
−
* Dani: '''M3 Respin'''
+
** Will be dropped in M1 (if no recent version is provided in the next weeks or if no one steps up)
−
** Issue had been found by a team member, but got lost between different teams
+
−
** Resolved and respun very fast, the fix is out now
+
−
* Dani: '''Release Cycles and Java Alignment'''
+
−
** Planning Council F2F meeting was at EclipseCon Europe; planning call will be on Thursday
+
−
** 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
+
−
** In case the Oracle release should slip, it will be most likely be named 18.4 (whatever month the release ends up in)
+
−
* All: '''Platform Release Rhythm'''
+
−
** At ECE, many people were surprised about changing release rhythm but the plan was generally appreciated
+
−
** 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>
+
* Pack 2000 support
 +
** not supported anymore as of Java 14
 +
** will be deprecated and marked for removal
  
−
<hr/>
+
* Moving Eclipse repos to Github
−
'''October 17, 2017''' - Dani, McQ, Martin, Lars, Alex
+
** Moving to Github might simplify and therefore increase contributions
−
* '''Conf.system:''' Fallback to McQ's number is not a good solution (can't give out the moderator code)
+
** Huge amount of work in releng
−
** Foundation (Denis) is aware of the problem, looking for a solution sooner than later
+
** Potentially we should all subprojects at the same time
−
** Skype group call, or zoom.us would work for Dani and McQ
+
** We check if the foundation plans to move everything to Gitlab
−
* Dani: '''{{bug|526065}} Java 9 to Oxygen.1a beta update issue'''
+
−
** Users who had the Java 9 beta installed and "update" to Oxygen.1a are broken
+
−
** McQ: Updating from "beta" to "final" is not necessarily supposed to be working (Lars disagrees)
+
−
** Not yet sure what's causing the issue .. p2 bug, or different groupID for Java9beta
+
−
** 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'')
+
−
* Lars: '''Release Cycle Discussion'''
+
−
** McQ still in favor of making every milestone a release
+
−
*** 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, ...)
+
−
*** 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/>
+
'''Mar 10, 2021''' - McQ, Tom, Alex
−
'''October 3, 2017''' - Dani, McQ, Alex, Martin
+
* Moving to Jetty 10 for next release
−
* '''Conf system woes''' - Dani couldn't dial in, Denis restarted the bridge leaving Martin and Alex in a Zombie bridge
+
* platform-dev discussion about move to GitHub
−
** '''ACTION McQ''' will send out conf.details using IBM's bridge
+
** conversation is useful, but would take a lot of planning
−
* {{bug|520720}} Mickael's question on Performance improvement
+
** lots of current rel eng dependencies on Gerrit
−
** Dani: There is already an asynchronous RequestLayout API for clients, and APIs already suggest clients use the async one
+
*** need more community help for rel eng issues
−
*** Therefore, changing the synchronous API to work asynchronously doesn't look right.
+
** a massive amount of history in our Bugzilla
−
** Alex: We seem to be mixing two aspects here -- agree regarding RequestLayout concerns, but why should the ProgressMonitor one be a problem?
+
* release record and proto-plan created for 4.20
−
*** 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
+
−
*** '''ACTION Dani''' will do a careful review of the ProgressMonitor part and deny the generic RequestLayout part
+
−
* Dani: '''Equinox Restructuring''' request for the move is in, will work with Tom and Foundation forward
+
−
* 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
+
'''Febr 17, 2021''' - Lars, Alex, McQ
−
* {{bug|520176}} '''MacOSX 10.13 (High Sierra) Menus Disabled'''
+
* Looks good for 4.19 release
−
** Only non-English Locales are affected
+
* Mac ARM has to wait for the 4.20 release, as the team fights multiple issues
−
** For 4.7.1a and Photon, a fix is in
+
* Top-level project page can currently only be edited by Tom, other PMC members also have access to it https://projects.eclipse.org/projects/eclipse/who
−
** Foundation [https://www.eclipse.org/org/press-release/20170925criticalbug.php Press Release (Newsletter)] is out with information how to work around
+
−
** Tweets are around as well -- keep spreading the message
+
−
* '''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/>
+
'''Dec 15, 2020''' - Lars, Alex, McQ
−
'''September 12, 2017''' - McQ, Alex, Dani
+
* 06. January 2021 is the next meeting
−
* Dani asked Alex to look into {{bug|517063}} with high prio. We need this for M2.
+
* How can PMC increase the awareness of the project leads / committers?
−
* Dani: sub-project merge
+
** Maybe invite the project leads once per month to the PMC meeting?
−
** McQ and Lars approved my message regarding sub-project. Will send out the note today.
+
** Discussion how we can increase the JDT community
−
** Still an issue with IP log not being merged
+
−
** 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/>
+
'''Dec 01, 2020''' - Lars, Alex, McQ
−
'''August 29, 2017''' - McQ, Dani, Martin
+
* RC1 is out; final touches on RC2
−
* All: '''Conference System Woes''' - 3 tries for McQ (race conditions?), 2 tries for Martin (silence first), 10 tries for Dani
+
* How can we remove the confusion about "e4" project?
−
* Dani: '''Subproject Merge''' done after some hiccups, no complaints since Fri
+
** e4 has always been intended to be a sandbox project where people could try things that are experimental or are on a longer timeline
−
** Subprojects are now "archived" with a comment that they got merged into the parent project
+
** Should be renamed to make it clear this isn't about leftovers from the Eclipse 4.0 work (maybe "eNext"?)
−
** '''AI Dani''' planning to send another notification to mailing lists:
+
** Should clean up repos
−
*** former PLs to become Repo Maintainers responsible for signoff and planning
+
*** Remove repos that just hold code that has already moved to the platform
−
*** Bugzilla remaining the same
+
*** Remove repos that are no longer getting any investment
−
*** Some former subproject leads already stepped up as combined project co-leads (Lars, Lakshmi, Sarika)
+
*** Work toward moving things that are active/useful into the platform (e.g. "spies" to PDE)
−
** McQ: Move forward towards the new structure, but there's also need to push for responsibility among the subcomponents (finding go-to persons...)
+
−
* Dani: '''StyledText improvement request on the ML''' (Pluggable selection model)
+
−
** point to the e4 incubator for experiments, encourage innovation though might be quite hard and pervasive
+
−
* 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/>
+
'''Nov 24, 2020''' - Lars, Alex, McQ
−
'''August 22, 2017''' - Alex, Dani, Martin
+
* PMC is considering the potential of an SDK / IDE working group at the foundation
−
* 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/>
+
* Discussion Do we need the extra releng work to create p2 repositories for milestones?
−
'''August 15, 2017''' - Alex, Dani
+
** Lot of extra work and sometimes goes wrong
−
* Dani: '''subproject merge''' initiated - waiting for webmasters
+
** All I-Builds are anyway available
−
* Dani: Provided Photon (4.8) release record and plan - please provide comments
+
−
* Alex and Dani discussed feature/bundle version issues - next builds should be better
+
  
−
<hr/>
+
-> PMC decided to drop the additional p2 repository
 +
-> Alex will be sending out an email about it to inform potential users of the special p2 repos
  
−
'''August 8, 2017''' - Alex, Martin, Dani
+
** Discussion about the purpose of the milestone week at all
−
* 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.
+
-> Decision not to change the process for now, as the additional testing and focus has also some benefits
−
* Dani: starting the '''planning record for Photon''' to announce participation in M1
+
−
** Toplevel items: JUnit5, Java9. Subplans on the Wiki.
+
−
* Dani: '''subproject merge''' - wanted to wait for M1, but should be done this week
+
−
* Alex: '''ppc64be''' - Sravan is waiting on final decision whether it will be removed in Photon
+
−
** Dani: PMC decision was settled, so removed from Eclipse plan - IBM ''might'' still continue building it for internal use
+
  
−
<hr/>
 
−
'''August 1, 2017''' - no call
 
  
−
'''July 25, 2017''' - Alex, Lars, Dani
+
'''Nov 17, 2020''' - Lars, Alex, Tom, McQ
−
* 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
+
* Release 4.18 winding down
−
* Discussion if CVS should be removed from the SDK build, Alex +1, Lars +1, Dani +1
+
** SWT churn for Linux and Mac Big Sur
−
* 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
+
** Does not appear the Foundation got the new Mac Hardware for testing
 +
* Planning Council discussion
 +
** Dani filled the Eclipse TLP representation role on the Council
 +
** Alex can take the lead to that role
 +
** Alex will look to find a replacement for the tools TLP representative
  
−
'''July 18, 2017''' - McQ, Alex, Lars, Dani
 
−
* project merge review awaiting go from Wayne - Dani pinged again in the bug report
 
−
* Dani will kick off planning for Photon a bit earlier since he will be in Bangalore the next 12 days. Platform UI already started.
 
−
* M1 on August 11
 
−
<hr/>
 
−
'''July 11, 2017''' - no meeting
 
  
−
'''July 4, 2017''' - no meeting
+
'''Nov 10, 2020''' - Lars, Alex, Tom, McQ
 +
* Still dealing with the loss of Dani
 +
* Discussed representation of JDT on PMC
 +
* Stabilizing for M3
 +
* Some releng issues with Java 15 and 16
 +
* Tom began investigating p2 ECF httpclient dependency
  
−
<hr/>
 
−
'''June 27, 2017''' - McQ, Dani, Martin, Alex
 
−
* '''Equinox Merge to the Eclipse TLP'''
 
−
** Keep Equinox as a separate Project, to allow independent Equinox releases without Platform (and keep Bugzilla simple)
 
−
** 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
 
−
* '''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/>
+
'''Nov 10, 2020''' - Lars, Alex, Tom, McQ
−
'''June 20, 2017''' - MQ, Dani, Lars, Alex
+
* Still dealing with the loss of Dani
−
* Attracting new contributors discussions - code cleanup and deletion of old paths needed
+
* Discussed representation of JDT on PMC
−
** Alex: Big issue to get people working on codebase and considering many now irrelevant paths in the codebase
+
* Stabilizing for M3
−
** Dani: Cleanups should be done by the one starting them through the whole SDK
+
* Some releng issues with Java 15 and 16
−
** 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
+
* Tom began investigating p2 ECF httpclient dependency
−
** 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/>
 
−
'''Juni 13, 2017''' - MQ, Dani, Lars
 
−
* Dani: Release review for 4.7 was successful
 
−
* 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
+
'''Nov 3, 2020''' - Lars, Alex, Tom, McQ
−
** Planned for M1, desired to be coordinated with the move of Equinox to Platform
+
* Dani!
−
** 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
 
−
* Dani: Please approve or disapprove the release review
 
−
* Dani: '''Starting the Debugger doesn't work always'''
 
−
** Occurs for Lars, but isn't reproducible - one of the top 3 things to fix if steps to reproduce are found
 
−
** Lars: Equinox replaced the DS implementation in 4.7, the issue is probably related
 
−
** 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.
 
−
** Martin: try with a reverse debugger like [http://chrononsystems.com/products/chronon-time-travelling-debugger/download Chronon] ?
 
−
*** 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
 
−
* 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/>
+
'''Oct 27, 2020''' - Lars, Tom
−
'''May 23, 2017''' - Alex, Martin, Dani, McQ
+
* Nothing to discuss
−
* 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/>
 
−
'''May 16, 2017''' - Alex, Martin, Dani, Lars
 
−
* Plan Update - updated on Wiki, main plan updated, please provide feedback until tomorrow latest:
 
−
** Has Updates to delivered / not delivered, and Target Operating Environment
 
−
* {{bug|509922}} Performance Tests: Header is wrong, but it really compares against 4.6.1: results are created but report is wrong
 
−
** Code should have been improved through many action enablement changes and startup improvments
 
−
** 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/>
+
'''Oct 20, 2020''' - Lars, Tom, McQ, Alex
−
'''May 9, 2017''' - Alex, Martin, Dani, McQ
+
* EclipseCon is running virtual this week
−
* Dani: '''JSR376 Jigsaw''': 10 said yes and 13 said no; a new spec to be provided within 30 days
+
* Agreement that removal of API should only before M1 release
−
** From a technical perspective, should be possible to resolve within 30 days
+
* Proof of concept for using Java 11 http client instead of ECF should be done
−
** JDT team implementing a compiler; IBM implementing a JVM, that's completely separate concerns!
+
* if we remove ECF we should send out an announcement and keep it for at least one release
−
** For implementing a compiler, the last spec is quite old, that is not good enough
+
* Decision to start using the @Deprecated(since = "x.y.z", forRemoval = true) for planned API removals if the bundle can use Java 11, wiki for API removal should be updated
−
** 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/>
+
'''Oct 6, 2020''' - Dani, Tom, McQ, Alex
−
'''May 2, 2017''' - Dani, Lars, Martin, Alex, McQ
+
* M1 under control
−
* Lars: '''Regex Evaluator Plugin'''
+
* Release train materials being worked
−
** Basically a view where one can input a regex and text, and see if it matches
+
* Moved to Jetty 9.4.32
−
** Would like to add to e4 incubator, goal to eventually add into Platform/Text or similar
+
* ECF — need to simplify how we consume http client
−
** McQ: Where it the boundary between e4 and Platform? How do people kick off little projects .. e4 incubator?
+
** could use Java11 http client instead, but this would require significant development effort
−
** '''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.
+
** Tom/Alex to take an initial stab at understanding scope + open bugs
−
* Dani: Endgame plan sent - Oxygen looking good, not too many bugs open
+
* Proposal: remove API once a year
−
* Dani: '''JSR Jigsaw Ballot'''
+
** Given the already long time for consumers to respond to API deprecation, PMC decision was to continue to allow API removal in any release. It was felt that the incremental benefit was outweighed by the need to be able to move forward quickly.
−
** 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/>
+
'''Sep 15, 2020''' - Dani, Tom, Lars, Alex
−
'''Apr 18, 2017''' - Dani, Lars, Martin, Alex, McQ
+
* M1
−
* Dani: '''RH and Java9 Jigsaw'''
+
** Next week M1 - Alex to send reminder note
−
** 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]
+
** Holiday in India on this Friday
−
** 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/>
+
* Y-Build for Java 16
−
'''Apr 11, 2017''' - McQ, Lars, Alex, Dani
+
** Builds should be fixed and can continue to progress on Java 16
−
* Dani: Update from last Planning Council call:
+
−
** 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.
+
−
** Issues with Neon.3. A respin might be necessary. For details see https://dev.eclipse.org/mhonarc/lists/eclipse.org-planning-council/msg02741.html.
+
−
* 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/>
+
* SCR upgrade
−
'''Apr 04, 2017''' - Dani, Martin, Alex
+
** Some issues with EBR maven plugin
−
* Martin: {{bug|514257}} and [https://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg14316.html cross-project Neon.3 wiring issue]
+
** causes versions to be incorrectly represented in p2 meta-data
−
** Problem: External libs don't deal with versions the same way we do
+
** Orbit needs a new lead, will end up impacting us if no replacement found
−
** 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/>
+
* Tycho being updated to be able to OSGi-fy JARs if they are not there yet.
−
'''Mar 28, 2017''' - McQ, Alex, Lars, Dani
+
** How to use this for a feature?
−
* Replacement for Sergey
+
** Behaves much like Orbit to produce new versions of the artifact.
−
** let's wait and see how things go
+
** Could be the solution for Orbit needs.
−
** 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/>
+
'''Sep 22, 2020''' - no meeting
−
'''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/>
 
−
'''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/>
+
'''Sep 15, 2020''' - McQ, Dani, Lars, Tom, Alex
−
'''Feb 28, 2017''' - Sergey, Alex, Martin, McQ
+
* Dani: Java 15 released today
−
* Alex: '''Short update on Neon.3'''
+
** 4.17 release together with Marketplace for Java 15 support are ready
−
** 2 jdt.core bugs asking for PMC approval - regressions compared to Neon.2, approved
+
** JDT Java 15 to be merged this week
−
** PPC rebuild is in, so looking good
+
* Dani: Zoom call with password unless each of the PMC members can be added as meeting owner so can start the meeting
−
* Sergey will leave Eclipse work after end of March
+
* Alex: 4.18 stream opened and releng work calmed down
−
* Martin: '''RCPTT / Reddeer / Testing'''
+
* Lars: Cleanup of migration guides
−
** Reddeer: No tests that check Platform only - everything is on higher level today (WTP, server connectors etc)
+
** Dani: this will break existing links, so existing content have to stay unless someone does all the work to fix our plans and other links that will break
−
** Runs on Neon.2 right now inside RH - the infrastructure isn't built for consuming daily builds
+
** McQ: help system needs work to focus on the latest stuff/release, what should we do to achieve it? How can we better shape the help system now that having all content ofline is not a requirement?
−
** Would take some effort reducing to Platform only - no time for this in the RH team at the moment
+
** Alex: do not ship migration, n&n,etc. but rather point to website url from help system
−
** '''AI Martin''' will look at integrating RCPTT as time permits; would like {{bug|505826}} resolved ideally
+
** Alex: this would also reduce manual work for releng (+1 by Dani)
−
*** See https://github.com/moberhuber/eclipse.platform.rcptt-tests
+
** ACTION ITEM: Alex to work on n&n in help system to use the website content directly as a proof of concept for further work
−
*** And https://github.com/eclipse-testing/eclipse-platform
+
  
−
<hr/>
 
−
'''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/>
+
'''Sep 01, 2020''' - Lars, Alex
−
'''Feb 15, 2017'''
+
* RC1 is fine, no additional requests for RC2
  
−
<hr/>
 
−
'''Feb 8, 2017''' - Dani, Alex, Martin, Lars
 
−
* Dani: '''{{bug|509412}}''' - Adopt newer JSch for Platform 4.6.3
 
−
** Alex is fully consumed with Webkit work for Oxygen
 
−
** 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
 
−
** 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/>
+
'''August 25, 2020''' - Tom, Lars, Alex, Dani
−
<strike>Feb 1, 2017 - cancelled</strike>
+
* Dani: sent out Endgame plan, RC1 this week, vacation starting on Friday
−
<hr/>
+
* Alex informed about Red Hat's Releng participation
  
−
'''Jan 24, 2017''' - Dani, Lars, Martin, Alex
 
−
* 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 18, 2020''' - Tom, Lars, Dani
−
'''Jan 17, 2017''' - Dani, Sergey, Alex, Lars, Martin, McQ
+
* Dani to create and send out Endgame plan
−
* Sergey: '''Merging platform.resources with platform.ui'''
+
* Looking into Mac Big Sur launching issue ({{bug|565913}})
−
** 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)
+
−
*** Opening up to Platform UI would encourage more people to actually contribute to resources. Strive for shared access on components that are interrelated
+
−
** Dani: Merging into platform.ui would mean making Dani and Lars the leaders for signoff - that causes too much burden
+
−
** Sergey: Platform/Team has actually more synergy with Platform/UI than resources
+
−
** Alex: For gcc for example, there is a notion of "maintainers" per git repo for signoffs - that's independent of leadership or commit rights
+
−
*** McQ: Not sure how adding another role would simplify things ?
+
−
** Sergey: The problem for signoffs is not is much the volume of commits, but the volume of failing tests
+
−
** 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
+
−
** 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 ?
+
−
** McQ: Propose applying the recent simplification of gaining commit rights (for "known" committers)
+
−
* Lars: '''Removing javax.xml'''
+
−
** Was introduced only for very old JRE's , it is part of the JRE now
+
−
** 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
+
−
** Lars: With javax.annotation, that was solved with smart reexporting
+
−
** McQ: OK with removal when we can confirm we're not breaking things
+
−
** Dani: Whoever requested removal should double-check whether the API is the same.
+
−
**'''AI Lars''' send a note to Tom Watson as the submitter.
+
−
* Dani: '''Project Updates'''
+
−
** Deadlines upcoming for CQs and APIs - see Endgame Plan, please provide feedback
+
−
* McQ: '''UI Testing and Jubula'''
+
  
−
<hr/>
+
 
−
'''Jan 10, 2017''' - Dani, Lars, Martin, Alex, Sergey, McQ - Special Guest: Alex Schladebeck
+
'''August 11, 2020''' - Alex, Dani, Tom, McQ
−
* Dani: '''Platform Bits on Maven Central''' - Now available thanks to Stephan Herrmann
+
* Eclipse Foundation is getting access to an Apple Silicon dev kit
−
* Dani: '''Board Committer Rep Elections''' opening
+
** Will make it available to SWT devs via cloud connectivity
−
* Dani: After David Williams' move, Wayne is looking for a Planning Council Chair; Fred Gurr has taken over Simrel Releng
+
* M3 next week; RC1 following week
−
* Dani: objenesis (Mockito / Easymock dependency) and Java9 - will wait for how upstream is planning to address issues
+
* ARM64 port seems to be working fine, except for browser widget (still investigating)
−
* Lars: '''Equinox move to Platform''' - no updates - '''AI Dani''' talk to Tom again
+
 
−
* McQ / AlexS: '''Jubula'''
+
 
−
** 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
+
'''August 4, 2020''' - Alex, Lars, Dani
−
** 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)
+
* no topics to discuss
−
** Dani: On EGit SWTBot tests, too many libraries to install, how to run on Gerrit HIPP slaves
+
 
−
** 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.
+
 
−
*** 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
+
'''July 28, 2020''' - Tom, McQ
−
*** Compared to SWTBot, Jubula is 90% blackbox (code highlevel actions rather than things like calling setText())
+
* no topics to discuss
−
*** UI Tests typically take longer than unittests by definition (due to setup, teardown, ...), so might not be applicable for Gerrit triggers
+
 
−
*** Dani: Would like to run a first test on CentOS first, as part of the integration tests
+
 
−
*** Lars: Robustness of the tests? - SWT on Mac is problematic, but Linux and Windows should be OK.
+
'''July 21, 2020''' - Tom, Dani, Alex, McQ, Lars
−
*** 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''')
+
* no topics to discuss
−
*** Getting a first test up and running ? - Maybe around 1 week, depends on what to do ?
+
* Alex on vacation next week
−
**** Lars: Would like something for quick access. Martin would something for "fresh download" (fresh config area + workspace) maybe combined with quick access.
+
 
−
*** '''AI AlexS''' send slides
+
 
−
*** '''AI Dani + Lars''' propose scenarios. Check possible owners of the initiative on Platform/UI side
+
'''July 14, 2020''' - Tom, Dani, Alex, McQ, Lars
−
*** '''AI AlexS''' check possible PlatformUI Contributors from Jubula team to get started
+
* Project status
 +
** M1 shipped last week
 +
** Draft Plan for 4.17 posted - additional fixes done after review
 +
** Release record created for 4.17
 +
* CQ process discussion - new clearly defined process
 +
** Note sent to Wayne to get clarifications on handbook, Wayne has made some edits in response.  We need to review latest handbook
 +
** Should simplify IP clearance for third party libraries
 +
*** If a bundle is approved by clearly defined it can be added with no CQ as long as the mavin URLs/coordinates are vetted by clearly defined
 +
*** Orbit should soon automate the linking to clearly defined approvals for bundles added.  Currently a work in progress by Roland at Orbit.
 +
*** The ratings system at clearly defined is not used.  Only the license check is used.
 +
** PMC needs to review latest handbook on the topic ... As of now we should move forward with the new process
 +
*** If concerns arise later we will need to take actions to correct
 +
* {{bug|565066}} - Needs some attention to the solution and testing
 +
** attempt to make incremental installation be consistent with resolution of a fresh install (or -clean).
 +
 
 +
 
 +
'''June 23, 2020''' - no call
 +
 
 +
'''June 16, 2020''' - no call
 +
 
 +
'''June 9, 2020''' - Alex, Dani, McQ, Lars, Tom
 +
* McQ: message to guide the community got no public reactions so far
 +
* Dani: bug reports needed for JDT, do we have PMC agreement?
 +
** Alex: For me that was approved after jdt-dev vote ended
 +
** AGREED
 +
* Dani: RC2 done, no major bug so far but still monitoriing for regressions
 +
* Alex: 4.17 stream open, not finished until 4.16 if final so all apichecks and etc. are in proper shape
 +
* Tom: OSGi R8 merge after stabilizing 4.17 stream
 +
* Tom: OSGi Move to Java 8 right after that
 +
* Dani: Switch to Java 11 as min version as it was already announced to happen in 4.17 stream shortly
 +
 
 +
 
 +
'''June 2, 2020''' - Alex, Dani, McQ, Lars, Tom
 +
* Inactive committer clean up for Eclipse project for the 4.16 release started via {{bug|563720}}
 +
* Infrastructure is really slow for RC2 release
 +
* RC2 bug queue is really low, one restart issue which is currently under investigated by Tom
 +
* Discussion about the JDT cleanup e-mails
 +
** Need to ensure community discussions are positive and respectful.
 +
** Expectations here should come from leadership
 +
*** LibreOffice did this in the past to great success.
 +
** Committers can vote against bugs but the tone of the discussion is important.
 +
** PMC will respond via the public mailing list within a week
 +
 
 +
 
 +
'''May 26, 2020''' - Alex, Dani, McQ
 +
* Closed all M3 bugs; RC1 looking good
 +
* Tips&tricks, new&noteworthy, contributions to the newsletter in progress
 +
* Chromium integration CQ approved -- https://dev.eclipse.org/ipzilla/show_bug.cgi?id=21808
 +
 
 +
 
 +
'''May 19, 2020''' - Tom, Dani, Lars, Alex
 +
* Dani: Issues with the build infrastructure, might endanger M3, the team got a working build for testing
 +
* Dani: PowerPC hardware was donated so builds are starting again for it
 +
* Alex: CQ process might get simpler based on blog post from Wayne, Alex to test and validate with Wayne https://blogs.eclipse.org/post/wayne-beaton/revising-eclipse-ip-due-diligence-process-third-party-content
 +
* Lars: Question if we want to allow "EGit" commit style in Eclipse top-level project. Agreement was to allow it but not to recommend it or enforce it
 +
 
 +
 
 +
'''May 12, 2020''' - Tom, Dani, McQ, Lars, Alex
 +
* Update to themes
 +
** Preference being added for choosing square vs round tabs
 +
** Intern from Alex's team is taking up the work
 +
** Update to Windows theme to be Windows 10
 +
* Alex brings up changes to CQ requirements. Need to read up on Wayne's post about this and discuss in a future call if we can change how the project does CQs
 +
* Who is running dark theme?
 +
** Need someone to cover test of Dark Theme on Linux.  Lars indicated that he runs with Linux Dark Theme and can help in coverage
 +
** Dani described the various members of his team that cover the rest of the platforms
 +
* Request to contribute to article on what is new in the release for a June newsletter.  Lars to contribute improvements in the Dark theme.  General request to others to contribute anything else.
 +
* ppc64le build troubles
 +
** Been having ongoing issues with the university hosted ppc64le machine we use to build support for ppc64le
 +
** Currently the ppc64le build has been disabled
 +
** Need to find alternatives
 +
*** May be able to use something from IBM public cloud
 +
*** Other suggestions: McQ - look towards using emulation, Alex - could do cross-compilation
 +
** Need to plan if ppc 10 will supported in the future
 +
 
 +
 
 +
'''May 5, 2020''' - Dani, Alex, Lars, McQ, Tom
 +
 
 +
* M2 shipped on time
 +
** Dark theme rebuild for M2 due to severe issue
 +
* ICU4J removal note sent
 +
** Lars - 2 years notice period needed?
 +
** Agreement: it's needed as we expose it in API and still have usages in internals so we need time to clean up ourself
 +
** EPPs cleanup - some blocked by JDT still using it, some by WTP, Rust probably the first one to be icu4j clean
 +
* Roundes vs square ctabfolder
 +
** Number of themes to be reduced
 +
** Performance not being measurable
 +
** Agreement: add preference to switch the rounded vs
 +
** Agreement: when preference is available Square is default
 +
* Windows theme update -
 +
** Fix colors to match Windows 10
 +
** GTK looks way more sane as more effort has been invested to keep it current
 +
** Don't set colors but use the colors from the OS theme is the recipe
 +
** Ugly white line on windows dark theme needs bugzilla open
 +
 
 +
 
 +
'''April 28, 2020''' - Dani, Alex, Lars
 +
 
 +
* PMC decided that the OS specific themes should be removed, https://bugs.eclipse.org/bugs/show_bug.cgi?id=562227
 +
* Windows light theme should become better https://bugs.eclipse.org/bugs/show_bug.cgi?id=551462
 +
* Dani - This week is M2, no special freeze or testing but we will contribute our build from Friday to the simrel
 +
* Databinding analyis was done by Jens Lindstroem and it looks good for an API compliant solution
 +
* Alex will prepare the information for cross that we will drop ibm icu from the SDK build
 +
 
 +
 
 +
'''April 21, 2020''' - McQ, Alex, Tom, Lars
 +
* Q: How do we deal with ICU removal from data binding?
 +
** Need to follow standard API removal rules
 +
*** Deprecate old API and offer new API
 +
*** Remove deprecated API after 2 years
 +
** Can we put the old stuff in a fragment that could be removed?
 +
* Theming: rounded tabs versus square tabs ({{bug|562221}})
 +
** Should we offer it at all?
 +
** Alex: Don’t increase the number of themes or options
 +
** Lars: Square tabs are faster
 +
** If speed is significant, we should consider changing the default
 +
 
 +
 
 +
'''April 14, 2020''' - McQ, Dani, Alex, Tom, Lars
 +
* Dani
 +
** M1 shipped, no problems so far
 +
** Using ECJ from M1 to build the SDK has some issues, there are people working on it
 +
** 4.16 plan to be published this week
 +
* Unanimous decision to continue to use Zoom as usual
 +
 
 +
 
 +
'''April 7, 2020''' - McQ, Dani, Alex, Tom, Lars
 +
* Dani
 +
** Created [https://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/eclipse/development/plans/eclipse_project_plan_4_16.xml 4.16 plan]
 +
** Created [https://bugs.eclipse.org/bugs/show_bug.cgi?id=561643 release record for 4.16]. Corresponding bug is {{bug|561643}}
 +
** Sent note to add planning bugs for 4.16
 +
** '''Please review and provide feedback if any'''
 +
** After some infrastructure issues we have a good test build and currently things look good for M1 this week
 +
* Alex seconded the infrastructure issues and missing test results
 +
* ICU4J ({{bug|560312}}): we decided to remove it piece by piece from projects where possible and where someone is interested to do it. The ICU bundle itself will stay, and we will follow the API removal process when we are ready to remove it, i.e. no usage in the SDK anymore
 +
 
 +
 
 +
'''March 31, 2020''' - Dani, Alex, McQ, Tom, Lars
 +
* Dani: Contacted the ICU4J owner. He updated {{bug|560312}}, PMC members will review the comment and we will discuss next week
 +
* Dani: Planning bugs are created slowly for 4.16. Will send a reminder to the list to submit more. Started to work on plan and release record.
 +
 
 +
 
 +
'''March 24, 2020''' - Alex, McQ, Tom
 +
* Dani: Regrets for the call (Eclipse Board call)
 +
* Alex: status updates
 +
** JDT merged Java 14 in master
 +
** Build instability due to infra status
 +
* Alex: OSGi R8 modules support - what is it?
 +
** Tom: ability to represent external content in the OSGi framework
 +
** Alex: Will it allow shipping eclipse plugins as JPMS modules to ease native library handling?
 +
** Tom: Haven't found any clear example how JPMS handles this, so good example is needed before could be looked further.
 +
 
 +
 
 +
'''March 17, 2020''' - Alex, McQ, Lars Tom, Dani
 +
* ICU4J use still under discussion
 +
** Dani still to contact ICU4J owner
 +
* Shipping Java 14 and 4.15 this week
 +
* Java 14 work will be merged to master on Wednesday
 +
 
 +
 
 +
'''March 10, 2020''' - Lars, Tom
 +
* Dani: Regrets for the call (vacation)
 +
* ICU4J use still under discussion
 +
** if we can be confident that performance and language support are of *similar* quality, we should work towards removing icu4j because it reduces complexity for us, in addition allowing for smaller RCP apps
 +
** note that we already have mixed usage -- some components using icu4j and some not
 +
* to clarify approvals that require a project lead can be done by a project lead for any of the Eclipse Project subprojects
 +
** as usual, the project lead should take care to understand the change and its implications before approving
 +
* we will move to Jetty 10 (and thus to Java 11) for the fall release
 +
* RH will be leading releng for 4.16
 +
 
 +
 
 +
'''March 3, 2020''' - no meeting
 +
 
 +
 
 +
'''February 25, 2020''' - Dani, McQ, Tom, Alex
 +
* Dani: Created and sent Endgame plan
 +
* Dani: Submitted IP Log: https://dev.eclipse.org/ipzilla/show_bug.cgi?id=21716
 +
* Alex: SWT on Linux in 4.16 to require Gtk 3.20 to simplify CSS machinery and prep for GTK4
 +
* Alex: ICU4J removal
 +
** Dani: ICU4J reacts faster to changes and supports more features (new Japanese era)
 +
** Alex: It might but Eclipse fails at keeping up so current version shipped with Eclipse misses features that the JVM supports (latest CLDR)
 +
** Dani: Asks for a proof that JVM is better that ICU
 +
** Alex: Which metrics to be measured?
 +
** Dani: Will check with ICU guy about that and whether it's still needed
 +
 
 +
 
 +
'''February 18, 2020''' - McQ, Alex, Dani, Lars, Tom
 +
* Dani: need to work on IP Log, Release Review and Endgame Plan
 +
* Lars: ECF - will we update to the latest
 +
** Alex: is in the works. Scott needs to provide us with the update
 +
* Tom: Found an issue with JUnit 5 launching but not reproducible with latest I-build
 +
** Dani: File a bug if you have steps or contact Noopur directly
 +
* Dani: Update on X-builds and tags
 +
 
 +
 
 +
'''February 11, 2020''' - McQ, Alex, Dani, Lars, Tom
 +
* Alex: Infrastructure is very instable, how can be complain to the foundation?
 +
** Alex: Eclipse foundation server team not responding to complains and seem unclear about the source of the issue
 +
** Discussion about makes a stronger statement to the foundation about the bad state of the infrastructure
 +
** McQ: Suggestion to send a note as PMC to the foundation
 +
** Dani: First we should ask webmaster why this takes so long
 +
** Alex: Marketplace infrastructure is also in bad state
 +
*** Dead marketplace entries are not getting removed https://bugs.eclipse.org/bugs/show_bug.cgi?id=550713
 +
*** No clean contact person from the foundation
 +
*** Marketplace is also not Open Source hence we cannot fix thing ourself.
 +
 
 +
-> Alex to contact Denis and to cc the other PMC members
 +
 
 +
'''February 4, 2020''' - McQ, Dani, Tom
 +
* OSGi Spec talk
 +
** OSGi R8 Core will be done this year.
 +
** May be ready for 4.16, but no rush if it slips to 4.17
 +
** Will not put anything in master until spec is final which makes it more likely to be 4.17
 +
 
 +
 
 +
'''January 28, 2020''' - McQ, Alex, Dani, Tom, Lars
 +
* Ongoing saga of the EPP packages
 +
** Markus did it last week
 +
** PMC discussed possible futures here, but no conclusions
 +
** Discussion also happening at the board level
 +
* M2 is this week
 +
* Pushing for JUnit updates for M2
 +
 
 +
 
 +
'''January 21, 2020''' - Dani, Tom, Lars
 +
* Dani: EPP builds still missing, Dani contacted Markus Knauer to update EPP for M1, release train is at risk if nobody steps up
 +
* New test failures are investigated, action plan is to restart the test, if they still fails restart the machine and if the tests still fail, see if a revert fixes the test
 +
 
 +
 
 +
'''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
  
 
= Archive =
 
= Archive =
 +
* [[Eclipse/PMC/Minutes 2019 | Archive of Meeting Minutes from 2019]]
 +
* [[Eclipse/PMC/Minutes 2018 | Archive of Meeting Minutes from 2018]]
 +
* [[Eclipse/PMC/Minutes 2017 | Archive of Meeting Minutes from 2017]]
 
* [[Eclipse/PMC/Minutes 2016 | Archive of Meeting Minutes from 2016]]
 
* [[Eclipse/PMC/Minutes 2016 | Archive of Meeting Minutes from 2016]]
 
* [[Eclipse/PMC/Minutes 2015 | Archive of Meeting Minutes from 2015]]
 
* [[Eclipse/PMC/Minutes 2015 | Archive of Meeting Minutes from 2015]]

Revision as of 11:09, 21 April 2021

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

Mar 31, 2021 - McQ, Tom, Alex, Lars

  • Java 16 jar signing issue
    • Tom wants to replace equinox implementation with builtin Jar file implementation so changes don't have to be done in Equinox on each release
  • JSP/Jetty story in IDE
    • Do we still need same functionality?
    • Alex - get out of the business for help system. Dependencies (jetty, lucene) generate more releng work than we can handle.
    • McQ - url for plugin help would be simplest and open it in browser
    • Any change (e.g. JSP removal) has to go through standard deprecation period, announcements and etc.
    • Alex to initiate communication on longer term plan with Holger who works on improvements to help system lately


Mar 31, 2021 - McQ, Tom, Alex

  • PMC call time
    • Overlaps with Planning council call and both Tom and Alex can't make both

-> Decision: Skip PMC call every first Wed of the month

  • Webpage Hugo migration
    • Recommended by Eclipse Foundation and active contributor to do the conversion
    • Concerns about mixing old and new content are raised but they don't look severe
    • Supported by PMC

-> Tom to handle initial communication on behalf of PMC

  • Planning process relevance
    • the planning process is not providing the detailed and usable plans from the past
    • not a pain point as fewer people participate it but looks like useless exercise quite often
    • to be discussed....


Mar 24, 2021 - Tom, Alex, Lars

  • Pack 200 - API removal in 2 years - 2023-06
    • Should we turn off all pack 200 features in one year, make it consistent across all Java versions.
    • 2022-06 - disable pack200 for all Java versions. Calling the deprecated API will be a no-op
  • Pack 200 - When can we stop generating? Agreed on 2021-09 release. We should set the precedence as early as possible to stop producing pack200 artifacts.
  • split packages
    • Causing issues with mandatory directive and p2 bug 360659 and with tycho.
    • Currently tycho requires some work arounds for usage of split packages
    • Can we work to get rid of split packages. We agreed to investigate the work and move to combine split packages if possible.


Mar 17, 2021 - McQ, Tom, Alex, Lars

  • SWT Chromium support
    • Still no recent version of Chromium with security patches
    • Will be dropped in M1 (if no recent version is provided in the next weeks or if no one steps up)
  • Pack 2000 support
    • not supported anymore as of Java 14
    • will be deprecated and marked for removal
  • Moving Eclipse repos to Github
    • Moving to Github might simplify and therefore increase contributions
    • Huge amount of work in releng
    • Potentially we should all subprojects at the same time
    • We check if the foundation plans to move everything to Gitlab


Mar 10, 2021 - McQ, Tom, Alex

  • Moving to Jetty 10 for next release
  • platform-dev discussion about move to GitHub
    • conversation is useful, but would take a lot of planning
    • lots of current rel eng dependencies on Gerrit
      • need more community help for rel eng issues
    • a massive amount of history in our Bugzilla
  • release record and proto-plan created for 4.20


Febr 17, 2021 - Lars, Alex, McQ

  • Looks good for 4.19 release
  • Mac ARM has to wait for the 4.20 release, as the team fights multiple issues
  • Top-level project page can currently only be edited by Tom, other PMC members also have access to it https://projects.eclipse.org/projects/eclipse/who


Dec 15, 2020 - Lars, Alex, McQ

  • 06. January 2021 is the next meeting
  • How can PMC increase the awareness of the project leads / committers?
    • Maybe invite the project leads once per month to the PMC meeting?
    • Discussion how we can increase the JDT community


Dec 01, 2020 - Lars, Alex, McQ

  • RC1 is out; final touches on RC2
  • How can we remove the confusion about "e4" project?
    • e4 has always been intended to be a sandbox project where people could try things that are experimental or are on a longer timeline
    • Should be renamed to make it clear this isn't about leftovers from the Eclipse 4.0 work (maybe "eNext"?)
    • Should clean up repos
      • Remove repos that just hold code that has already moved to the platform
      • Remove repos that are no longer getting any investment
      • Work toward moving things that are active/useful into the platform (e.g. "spies" to PDE)

Nov 24, 2020 - Lars, Alex, McQ

  • PMC is considering the potential of an SDK / IDE working group at the foundation
  • Discussion Do we need the extra releng work to create p2 repositories for milestones?
    • Lot of extra work and sometimes goes wrong
    • All I-Builds are anyway available

-> PMC decided to drop the additional p2 repository -> Alex will be sending out an email about it to inform potential users of the special p2 repos

    • Discussion about the purpose of the milestone week at all

-> Decision not to change the process for now, as the additional testing and focus has also some benefits


Nov 17, 2020 - Lars, Alex, Tom, McQ

  • Release 4.18 winding down
    • SWT churn for Linux and Mac Big Sur
    • Does not appear the Foundation got the new Mac Hardware for testing
  • Planning Council discussion
    • Dani filled the Eclipse TLP representation role on the Council
    • Alex can take the lead to that role
    • Alex will look to find a replacement for the tools TLP representative


Nov 10, 2020 - Lars, Alex, Tom, McQ

  • Still dealing with the loss of Dani
  • Discussed representation of JDT on PMC
  • Stabilizing for M3
  • Some releng issues with Java 15 and 16
  • Tom began investigating p2 ECF httpclient dependency


Nov 10, 2020 - Lars, Alex, Tom, McQ

  • Still dealing with the loss of Dani
  • Discussed representation of JDT on PMC
  • Stabilizing for M3
  • Some releng issues with Java 15 and 16
  • Tom began investigating p2 ECF httpclient dependency


Nov 3, 2020 - Lars, Alex, Tom, McQ

  • Dani!


Oct 27, 2020 - Lars, Tom

  • Nothing to discuss


Oct 20, 2020 - Lars, Tom, McQ, Alex

  • EclipseCon is running virtual this week
  • Agreement that removal of API should only before M1 release
  • Proof of concept for using Java 11 http client instead of ECF should be done
  • if we remove ECF we should send out an announcement and keep it for at least one release
  • Decision to start using the @Deprecated(since = "x.y.z", forRemoval = true) for planned API removals if the bundle can use Java 11, wiki for API removal should be updated

Oct 6, 2020 - Dani, Tom, McQ, Alex

  • M1 under control
  • Release train materials being worked
  • Moved to Jetty 9.4.32
  • ECF — need to simplify how we consume http client
    • could use Java11 http client instead, but this would require significant development effort
    • Tom/Alex to take an initial stab at understanding scope + open bugs
  • Proposal: remove API once a year
    • Given the already long time for consumers to respond to API deprecation, PMC decision was to continue to allow API removal in any release. It was felt that the incremental benefit was outweighed by the need to be able to move forward quickly.


Sep 15, 2020 - Dani, Tom, Lars, Alex

  • M1
    • Next week M1 - Alex to send reminder note
    • Holiday in India on this Friday
  • Y-Build for Java 16
    • Builds should be fixed and can continue to progress on Java 16
  • SCR upgrade
    • Some issues with EBR maven plugin
    • causes versions to be incorrectly represented in p2 meta-data
    • Orbit needs a new lead, will end up impacting us if no replacement found
  • Tycho being updated to be able to OSGi-fy JARs if they are not there yet.
    • How to use this for a feature?
    • Behaves much like Orbit to produce new versions of the artifact.
    • Could be the solution for Orbit needs.


Sep 22, 2020 - no meeting


Sep 15, 2020 - McQ, Dani, Lars, Tom, Alex

  • Dani: Java 15 released today
    • 4.17 release together with Marketplace for Java 15 support are ready
    • JDT Java 15 to be merged this week
  • Dani: Zoom call with password unless each of the PMC members can be added as meeting owner so can start the meeting
  • Alex: 4.18 stream opened and releng work calmed down
  • Lars: Cleanup of migration guides
    • Dani: this will break existing links, so existing content have to stay unless someone does all the work to fix our plans and other links that will break
    • McQ: help system needs work to focus on the latest stuff/release, what should we do to achieve it? How can we better shape the help system now that having all content ofline is not a requirement?
    • Alex: do not ship migration, n&n,etc. but rather point to website url from help system
    • Alex: this would also reduce manual work for releng (+1 by Dani)
    • ACTION ITEM: Alex to work on n&n in help system to use the website content directly as a proof of concept for further work


Sep 01, 2020 - Lars, Alex

  • RC1 is fine, no additional requests for RC2


August 25, 2020 - Tom, Lars, Alex, Dani

  • Dani: sent out Endgame plan, RC1 this week, vacation starting on Friday
  • Alex informed about Red Hat's Releng participation


August 18, 2020 - Tom, Lars, Dani

  • Dani to create and send out Endgame plan
  • Looking into Mac Big Sur launching issue (bug 565913)


August 11, 2020 - Alex, Dani, Tom, McQ

  • Eclipse Foundation is getting access to an Apple Silicon dev kit
    • Will make it available to SWT devs via cloud connectivity
  • M3 next week; RC1 following week
  • ARM64 port seems to be working fine, except for browser widget (still investigating)


August 4, 2020 - Alex, Lars, Dani

  • no topics to discuss


July 28, 2020 - Tom, McQ

  • no topics to discuss


July 21, 2020 - Tom, Dani, Alex, McQ, Lars

  • no topics to discuss
  • Alex on vacation next week


July 14, 2020 - Tom, Dani, Alex, McQ, Lars

  • Project status
    • M1 shipped last week
    • Draft Plan for 4.17 posted - additional fixes done after review
    • Release record created for 4.17
  • CQ process discussion - new clearly defined process
    • Note sent to Wayne to get clarifications on handbook, Wayne has made some edits in response. We need to review latest handbook
    • Should simplify IP clearance for third party libraries
      • If a bundle is approved by clearly defined it can be added with no CQ as long as the mavin URLs/coordinates are vetted by clearly defined
      • Orbit should soon automate the linking to clearly defined approvals for bundles added. Currently a work in progress by Roland at Orbit.
      • The ratings system at clearly defined is not used. Only the license check is used.
    • PMC needs to review latest handbook on the topic ... As of now we should move forward with the new process
      • If concerns arise later we will need to take actions to correct
  • bug 565066 - Needs some attention to the solution and testing
    • attempt to make incremental installation be consistent with resolution of a fresh install (or -clean).


June 23, 2020 - no call

June 16, 2020 - no call

June 9, 2020 - Alex, Dani, McQ, Lars, Tom

  • McQ: message to guide the community got no public reactions so far
  • Dani: bug reports needed for JDT, do we have PMC agreement?
    • Alex: For me that was approved after jdt-dev vote ended
    • AGREED
  • Dani: RC2 done, no major bug so far but still monitoriing for regressions
  • Alex: 4.17 stream open, not finished until 4.16 if final so all apichecks and etc. are in proper shape
  • Tom: OSGi R8 merge after stabilizing 4.17 stream
  • Tom: OSGi Move to Java 8 right after that
  • Dani: Switch to Java 11 as min version as it was already announced to happen in 4.17 stream shortly


June 2, 2020 - Alex, Dani, McQ, Lars, Tom

  • Inactive committer clean up for Eclipse project for the 4.16 release started via bug 563720
  • Infrastructure is really slow for RC2 release
  • RC2 bug queue is really low, one restart issue which is currently under investigated by Tom
  • Discussion about the JDT cleanup e-mails
    • Need to ensure community discussions are positive and respectful.
    • Expectations here should come from leadership
      • LibreOffice did this in the past to great success.
    • Committers can vote against bugs but the tone of the discussion is important.
    • PMC will respond via the public mailing list within a week


May 26, 2020 - Alex, Dani, McQ


May 19, 2020 - Tom, Dani, Lars, Alex

  • Dani: Issues with the build infrastructure, might endanger M3, the team got a working build for testing
  • Dani: PowerPC hardware was donated so builds are starting again for it
  • Alex: CQ process might get simpler based on blog post from Wayne, Alex to test and validate with Wayne https://blogs.eclipse.org/post/wayne-beaton/revising-eclipse-ip-due-diligence-process-third-party-content
  • Lars: Question if we want to allow "EGit" commit style in Eclipse top-level project. Agreement was to allow it but not to recommend it or enforce it


May 12, 2020 - Tom, Dani, McQ, Lars, Alex

  • Update to themes
    • Preference being added for choosing square vs round tabs
    • Intern from Alex's team is taking up the work
    • Update to Windows theme to be Windows 10
  • Alex brings up changes to CQ requirements. Need to read up on Wayne's post about this and discuss in a future call if we can change how the project does CQs
  • Who is running dark theme?
    • Need someone to cover test of Dark Theme on Linux. Lars indicated that he runs with Linux Dark Theme and can help in coverage
    • Dani described the various members of his team that cover the rest of the platforms
  • Request to contribute to article on what is new in the release for a June newsletter. Lars to contribute improvements in the Dark theme. General request to others to contribute anything else.
  • ppc64le build troubles
    • Been having ongoing issues with the university hosted ppc64le machine we use to build support for ppc64le
    • Currently the ppc64le build has been disabled
    • Need to find alternatives
      • May be able to use something from IBM public cloud
      • Other suggestions: McQ - look towards using emulation, Alex - could do cross-compilation
    • Need to plan if ppc 10 will supported in the future


May 5, 2020 - Dani, Alex, Lars, McQ, Tom

  • M2 shipped on time
    • Dark theme rebuild for M2 due to severe issue
  • ICU4J removal note sent
    • Lars - 2 years notice period needed?
    • Agreement: it's needed as we expose it in API and still have usages in internals so we need time to clean up ourself
    • EPPs cleanup - some blocked by JDT still using it, some by WTP, Rust probably the first one to be icu4j clean
  • Roundes vs square ctabfolder
    • Number of themes to be reduced
    • Performance not being measurable
    • Agreement: add preference to switch the rounded vs
    • Agreement: when preference is available Square is default
  • Windows theme update -
    • Fix colors to match Windows 10
    • GTK looks way more sane as more effort has been invested to keep it current
    • Don't set colors but use the colors from the OS theme is the recipe
    • Ugly white line on windows dark theme needs bugzilla open


April 28, 2020 - Dani, Alex, Lars


April 21, 2020 - McQ, Alex, Tom, Lars

  • Q: How do we deal with ICU removal from data binding?
    • Need to follow standard API removal rules
      • Deprecate old API and offer new API
      • Remove deprecated API after 2 years
    • Can we put the old stuff in a fragment that could be removed?
  • Theming: rounded tabs versus square tabs (bug 562221)
    • Should we offer it at all?
    • Alex: Don’t increase the number of themes or options
    • Lars: Square tabs are faster
    • If speed is significant, we should consider changing the default


April 14, 2020 - McQ, Dani, Alex, Tom, Lars

  • Dani
    • M1 shipped, no problems so far
    • Using ECJ from M1 to build the SDK has some issues, there are people working on it
    • 4.16 plan to be published this week
  • Unanimous decision to continue to use Zoom as usual


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

  • Dani
    • Created 4.16 plan
    • Created release record for 4.16. Corresponding bug is bug 561643
    • Sent note to add planning bugs for 4.16
    • Please review and provide feedback if any
    • After some infrastructure issues we have a good test build and currently things look good for M1 this week
  • Alex seconded the infrastructure issues and missing test results
  • ICU4J (bug 560312): we decided to remove it piece by piece from projects where possible and where someone is interested to do it. The ICU bundle itself will stay, and we will follow the API removal process when we are ready to remove it, i.e. no usage in the SDK anymore


March 31, 2020 - Dani, Alex, McQ, Tom, Lars

  • Dani: Contacted the ICU4J owner. He updated bug 560312, PMC members will review the comment and we will discuss next week
  • Dani: Planning bugs are created slowly for 4.16. Will send a reminder to the list to submit more. Started to work on plan and release record.


March 24, 2020 - Alex, McQ, Tom

  • Dani: Regrets for the call (Eclipse Board call)
  • Alex: status updates
    • JDT merged Java 14 in master
    • Build instability due to infra status
  • Alex: OSGi R8 modules support - what is it?
    • Tom: ability to represent external content in the OSGi framework
    • Alex: Will it allow shipping eclipse plugins as JPMS modules to ease native library handling?
    • Tom: Haven't found any clear example how JPMS handles this, so good example is needed before could be looked further.


March 17, 2020 - Alex, McQ, Lars Tom, Dani

  • ICU4J use still under discussion
    • Dani still to contact ICU4J owner
  • Shipping Java 14 and 4.15 this week
  • Java 14 work will be merged to master on Wednesday


March 10, 2020 - Lars, Tom

  • Dani: Regrets for the call (vacation)
  • ICU4J use still under discussion
    • if we can be confident that performance and language support are of *similar* quality, we should work towards removing icu4j because it reduces complexity for us, in addition allowing for smaller RCP apps
    • note that we already have mixed usage -- some components using icu4j and some not
  • to clarify approvals that require a project lead can be done by a project lead for any of the Eclipse Project subprojects
    • as usual, the project lead should take care to understand the change and its implications before approving
  • we will move to Jetty 10 (and thus to Java 11) for the fall release
  • RH will be leading releng for 4.16


March 3, 2020 - no meeting


February 25, 2020 - Dani, McQ, Tom, Alex

  • Dani: Created and sent Endgame plan
  • Dani: Submitted IP Log: https://dev.eclipse.org/ipzilla/show_bug.cgi?id=21716
  • Alex: SWT on Linux in 4.16 to require Gtk 3.20 to simplify CSS machinery and prep for GTK4
  • Alex: ICU4J removal
    • Dani: ICU4J reacts faster to changes and supports more features (new Japanese era)
    • Alex: It might but Eclipse fails at keeping up so current version shipped with Eclipse misses features that the JVM supports (latest CLDR)
    • Dani: Asks for a proof that JVM is better that ICU
    • Alex: Which metrics to be measured?
    • Dani: Will check with ICU guy about that and whether it's still needed


February 18, 2020 - McQ, Alex, Dani, Lars, Tom

  • Dani: need to work on IP Log, Release Review and Endgame Plan
  • Lars: ECF - will we update to the latest
    • Alex: is in the works. Scott needs to provide us with the update
  • Tom: Found an issue with JUnit 5 launching but not reproducible with latest I-build
    • Dani: File a bug if you have steps or contact Noopur directly
  • Dani: Update on X-builds and tags


February 11, 2020 - McQ, Alex, Dani, Lars, Tom

  • Alex: Infrastructure is very instable, how can be complain to the foundation?
    • Alex: Eclipse foundation server team not responding to complains and seem unclear about the source of the issue
    • Discussion about makes a stronger statement to the foundation about the bad state of the infrastructure
    • McQ: Suggestion to send a note as PMC to the foundation
    • Dani: First we should ask webmaster why this takes so long
    • Alex: Marketplace infrastructure is also in bad state

-> Alex to contact Denis and to cc the other PMC members

February 4, 2020 - McQ, Dani, Tom

  • OSGi Spec talk
    • OSGi R8 Core will be done this year.
    • May be ready for 4.16, but no rush if it slips to 4.17
    • Will not put anything in master until spec is final which makes it more likely to be 4.17


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

  • Ongoing saga of the EPP packages
    • Markus did it last week
    • PMC discussed possible futures here, but no conclusions
    • Discussion also happening at the board level
  • M2 is this week
  • Pushing for JUnit updates for M2


January 21, 2020 - Dani, Tom, Lars

  • Dani: EPP builds still missing, Dani contacted Markus Knauer to update EPP for M1, release train is at risk if nobody steps up
  • New test failures are investigated, action plan is to restart the test, if they still fails restart the machine and if the tests still fail, see if a revert fixes the test


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

Archive

Retrieved from "https://wiki.eclipse.org/index.php?title=Eclipse/PMC&oldid=443062"

Back to the top