Skip to main content
Jump to: navigation, search

Difference between revisions of "Eclipse/PMC"

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

Latest revision as of 11:09, 31 March 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

  • 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

Back to the top