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)
(135 intermediate revisions by 5 users not shown)
Line 8: Line 8:
 
= 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 Wednesday at 10.30am EST'''.
  
 
= Meeting Minutes =
 
= Meeting Minutes =
'''October 30, 2013''' - McQ, Dani, Andrew, Martin
 
* Andrew: Excited by {{bug|}} Kris Daniel '''patch for Shared Installs'''
 
* Andrew: ECE Hackathon went well; "Let's make Eclipse Fun Again" BoF
 
* McQ: Hackathon next week for BlueMax cloudfoundry (Orion)
 
  
<hr/>
+
'''November 25, 2015''' - McQ, Martin, Alex
'''October 16, 2013''' - John, Dani, Andrew, Martin
+
* Alex: '''Bumping SWT to Java8'''
* Dani: '''Good progress on Java 8''' - {{bug|380190}} compiler work done - going to send something
+
** Lars wants to use Lambdas {{bug|481195}}; Markus keller wants static helper methods;
* Martin: {{bug|402509}} Context Menu Filtering : Paul set to 4.4 for discussion as part of UI review; Martin still interested, could help with some resources (testing, or even implementation when architectural guidance is given)
+
** Stephan Herrmann - University Research for Thread safety through typed annotations
* '''IDE Working Group''' ([[IDE Working Group Proposal]])
+
*** Are they ready to contribute? - Probably yes, needs to be clarified; having better dev support for Thread Safety will be a huge help
** John: from PMC point of view, a good thing: sponsored contributors would be just like another group of contributors
+
*** Dani: Thinks that going to Java8 feels a bit early for SWT, which is at the bottom of the technology stack ... would prefer 1 year later
** Some companies prefer making code contributions but for other companies this is very impractical and might work better with a [http://images3.wikia.nocookie.net/__cb20130603225716/leagueoflegends/images/6/66/Iffem_shut-up-and-take-my-money.jpg shut up and take my money] model.
+
*** John: Lambda support doesn't necessarily require SWT to be Java 8 itself (it could just be more lambda friendly)
* Andrew: '''Krzystof Daniel for commit rights on p2'''
+
**** Won't help with base listeners, but probably with mouse events and related .. follow up in the bugreport
** It appears to be resolved already but we hope it doesn't have to come to this in the future.
+
**** Labdas are more than syntactic sugar, it's more efficient ... still there is more value in Thread safety annotations
** Recent studies show that timely responses within 1 day (even "we'll respond in a month") will dramatically increase engagement
+
*** McQ: Assumes there would be an extensive discussion on cross-project anyways ... but there is evidence now we could get value from doing this.
 +
* Dani: '''Update on Move of platform.text'''
 +
** Approval from IP, will soon move to platform.ui - will keep platform.text bugzilla.
 +
* John: '''FEEP'''
 +
** As discussed on the [[Architecture Council]]
 +
* McQ: '''Platform Support'''
 +
** Many Platforms are not really active - IBM keeps alive some of them, for example RHEL4
 +
** Recent mailinglist asking for Mac 32bit, have we done enough on announcements ?
 +
** '''Agreement''' there's no case for catering more to people who don't read announcements and follow the project. Having a mailinglist ask once in a while is OK.
 +
** Dani: Planning Update for Neon / M4 - please comment on the bug.  
 +
*** John: Plan document is not really exhaustive on the oldest working Platform - RHEL4 surely won't work in Neon.
 +
** Alex: Consider a "Build your Own" approach for the more obscure Platforms? - Frees us from keeping older binaries in sync
 +
*** Did that for ARM32 and ARM64 in master - can build by just calling maven
 +
*** McQ: Who would ever validate that scripts are still valid... (Linux community: provides no binaries at all, who validates?)
 +
*** Alex: Providing scripts is a lot less work than providing stable and widely compatible binaries (about 1/3 of the work)
  
 
<hr/>
 
<hr/>
'''October 9, 2013''' - John, Dani, Andrew, Martin
+
'''November 18, 2015''' - Alex, John, Dani
* John: '''Builds''' - looks like things are under control
+
* Dani: EclipseCon NA 2016 submission from our team:
* John: '''Help System Security Bug''' - {{bug|418443}} only when help server is run on https, thus not an issue when run locally
+
** https://www.eclipsecon.org/na2016/session/scaling-eclipse-high-dpi-dots-inch-monitors-challenges-and-solutions
 +
** https://www.eclipsecon.org/na2016/session/java-9-support-eclipse
 +
* John: mentioned FEEP
 +
** Alex has concerns that there's not an equal opportunity for everyone
 +
* Alex: new Lucene version: would like to put it in
 +
** cross-projects has already been asked and we got no negative vote
 +
** CQs are approved
 +
** seems to be blocked by Orbit
 +
** ==> Alex to find out why and report back next week in the PMC call
  
 
<hr/>
 
<hr/>
'''October 2, 2013''' - McQ, John, Dani
+
 
* no discussion topics
+
'''November 11, 2015''' - McQ, John, Dani
 +
* Discussed new meeting time that works for Martin
 +
** John to send a note that proposes Tuesday, 11:00 EST / 17:00 CET (starting in two weeks)
 +
* John: Alex mentioned at EclipseCon that there's no one in SWT team overlooking cross-platform, e.g. to craft new APIs
 +
** owning one platform is a full-time job
 +
** would need another person in SWT
 +
** for now one of the two co-leads needs to own that task - Dani to talk to Pradeep and the co-leads
 +
* John to Dani: how was EclipseCon
 +
** Dani: Great! Lots of talking to people; spent quite some time at the Hackathon; only saw 4 talks
  
 
<hr/>
 
<hr/>
'''September 25, 2013''' - McQ, Andrew, Martin, John
 
* Andrew: '''Commercial Support Thread''' - Directory of consultants to effect change when needed
 
** Foundation to employ developers to "do whatever is best for the Platform" : Who decides on features, and where does the funding come from ?
 
** There is precedent of Foundations employing developers... but don't think that "developers for hire" model could work
 
  
* Martin: '''ide-dev''' discussion
+
'''October 28, 2015''' - McQ, John, Alex, Dani
** A Platform team tries to come up with features and architecture that they think is valuable...
+
* Dani: Discuss new meeting time that works for Martin
** but there's not the same drive towards a product / UX that a commercial product has
+
** decided that John will send out a doodle poll
** Because of the nature how we do things, it's harder to get to a polished UX
+
* Dani: Discuss our position regarding the removal of committer emeritus ({{bug|480670}})
 +
** everyone agreed that we would like to keep this for the following reasons:
 +
*** it is a good way reward those committers who invested lots of their time and made significant contributions to a project
 +
*** it makes no sense to remove something that currently works and ask projects to maintain this on their website
 +
** we have to make sure that the emeritus list doesn't get stale
  
 
<hr/>
 
<hr/>
'''September 18, 2013''' - McQ, Dani, Martin, Andrew
+
 
* Mozilla: Orion vs CodeMirror as Editor - Speed of progressing on Editor features, Community size ?
+
'''October 21, 2015''' - McQ, Alex, Dani
** CodeMirror addons can't be absorbed at Orion (licenses, provenance, etc.)
+
* Dani: so far no negative vote in the vote to move platform.text into platform.ui
** Can we prove that the Orion editor is better ?
+
* McQ: Martin can no longer join, McQ would like to move the meeting
** What matters is our amount of commitment to "Development in the Cloud"
+
** detailed several alternatives but no fit yet
 +
** decided to continue the discussion in our next meeting
  
 
<hr/>
 
<hr/>
'''September 11, 2013''' - McQ, John, Dani, Martin
+
 
* John: '''RC4''' navigaton history fix ({{bug|416902}}) - review
+
'''October 14, 2015''' - McQ, John, Alex, Dani
* McQ: Focusing Ottawa on Orion
+
* Dani: Community asked to move platform.text into platform.ui (see [https://dev.eclipse.org/mhonarc/lists/platform-text-dev/msg00484.html https://dev.eclipse.org/mhonarc/lists/platform-text-dev/msg00484.html])
* Martin: '''[[E4/Scripting]]''' progress. Homepage has links onto Requirements, EclipseCon Europe talk and more
+
** 3 solutions:
** McQ: Overlap with RAP when JavaScript is being used ?
+
*** make the move
* John: Krzystof Daniel of Red Hat for committer / component lead
+
*** make a more radical move to merge everything into 'Platform'
 +
*** leave things as is and let new people join platform.text
 +
** McQ: merging everything together is not an option. Skills are too different. Resources, Debug and SWT need to be kept separate.
 +
** Dani: fine with the move as long as it does not serve as argument to merge everything into one pot
 +
** Alex: committers need to accept the move
 +
** PMC decision: OK with the move but Dani to ask the platform.text and platform.ui committers whether they are both OK with it. Dani to become co-lead of Platform UI
 +
 
 +
* John from Board Meeting: Eclipse Foundation wants to change perception that Eclipse is just an IDE. Therefore they would like to change the name of our project ("Eclipse").
 +
** McQ:
 +
*** this will not be for free. The name is used at many places (code, webpage, Help) and also by companies in their marketing
 +
*** maybe we just have to accept we made a mistake in the beginning and now live with it
 +
*** can't think of a good name - which indicates we shouldn't change it ("Platform" is not good and "Eclipse SDK" or "Eclipse IDE" hide that it is the base for "RCP" apps)
 +
** decided to talk about this again in the next call
  
 
<hr/>
 
<hr/>
'''September 4, 2013''' - No meeting
 
  
'''August 28, 2013''' - Dani, John, Martin
+
'''October 7, 2015''' - McQ, John, Alex, Dani, Martin
* Dani: '''Stardust adding features to SR1''' - Planning Council exception - no objections
+
* Dani: '''{{bug|108668}} Default Text Encoding UTF-8 ?'''
* John: '''language tooling on [http://dev.eclipse.org/mhonarc/lists/ide-dev/ ide-dev]''' - where to host the work ?
+
** On Linux and Mac, the Platform encoding is UTF-8 ; on Windows it's Cp1252 in most countries around the globe, even with Windows 10
** Eclipse project/e4 proposed
+
** Using the Platform encoding ensures interoperability with all local tools (editors, compilers, ...)
** Dani: '''What's the goal?''' - make it easier adding new languages, or refactor existing projects ?
+
*** '''Desire for UTF-8 only for Windows exchanging files with users on other systems'''
*** Martin interested in cross-language crossreferencing
+
*** '''Changing the encoding of an existing workspace after the fact is a no go''' (risk of data corruption when loading/saving a file, some encodings are lossy)
**** Lua tooling / C bindings, Java/JNI, Python C bindings, TCF, CORBA generated stubs/proxies, ...
+
*** '''Using an encoding different than the OS encoding is problematic too''' (risk of data corruption when importing or D&D files from the OS)
*** Easier to create tooling for JVM-based languages
+
** Proposal 1: UTF-8 on new empty workspaces on Windows ? --&gt; Might mean that external tools don't work as expected
*** Common support for refactoring
+
** Proposal 2: Make users aware (Restore Oomph Welcome, which was disabled via {{bug|459486}}) ? --&gt; But many users don't understand implications, other tools also don't do this
*** ...
+
** Proposal 3: Ask for encoding when team-sharing since only team-shared projects cause issues (eg EGit hook) ? --&gt; But on "push" it may be too late
** AC could be involved - makes sense for AC to be involved in a working group
+
** Martin: Encoding describes content, so should be managed with the content (as a project setting)
*** In the end, it boils down to who steps up writing code
+
*** '''--&gt; Proposal 4: Move to a model where we encourage setting the project-level encoding preference'''
* Martin: short update on scripting-dev ... making progress, code has been provided, e4 proposed as a home, no feedback yet
+
**** When creating a project, set the workspace default on project level automatically --&gt; ensures that projects remain sane over their lifetime
 +
**** For projects lacking the project-level preference, introduce a Problem Marker (Warning) with quick fix to either UTF-8 or workspace default
 +
** '''Decision:'''
 +
*** '''We won't change the workspace default''' -- no use breaking existing users
 +
*** '''We'll set the project encoding pro-actively'''
 +
** Open questions:
 +
*** Do we need tooling to convert project from encoding A to encoding B (if project preference was set incorrectly initially) ?
 +
*** Shall we try setting source encoding on drag-and-drop, or shall the project dictate the policy ?
  
 
<hr/>
 
<hr/>
'''August 21, 2013''' - Dani, John, Andrew, Martin
+
'''September 30, 2015''' - McQ, John, Alex, Dani
* Dani: '''Still need the links to the torrents?''' Can we measure usage of torrents ? "Eclipse SDK" traffic is low these days anyways, would make sense for EPP only if ever
+
* Dani: will send a note to PMC list asking to approve new Debug leadership (Sarika)
* Martin: Some traffic these days on the [http://dev.eclipse.org/mhonarc/lists/eclipse-scripting-dev/ eclipse-scripting-dev] mailing list
+
* Dani: we should finalize our API removal discussion from last week
** John: Some UI would likely be simpler with e4 now ...
+
** agreed that APIs marked for removal have to be annotated with @noreference, @noextend and @noimplement
** e4 would be a possible initial place for the project (incubator), initial basic hooks could even be put into the Platform
+
** agreed that components should be allowed to remove API but they have to provide good reasons
* Luna M1 went pretty well
+
** agreed that we won't allow to delete APIs simply because they are deprecated
 +
** agreed that the PMC will decide case by case i.e. there will be no general rule
 +
** regarding version numbering we decided to also decide this case by case
 +
** Dani to update the removal document and have it reviewed by the PMC
  
 
<hr/>
 
<hr/>
'''August 14, 2013''' - Dani, Andrew
+
 
* Dani: no changes to release pace for Luna. For details see [[Planning_Council/August_7_2013]]
+
'''September 23, 2015''' - Dani, John, Alex, Martin
 +
* Dani: '''JDT Core''' - Co-lead going to step up
 +
* Dani: '''API Removal Discussion'''
 +
** Q1: When do we actually delete API? What's the benefit compared to the pain that we cause ?
 +
*** Example of methods that don't do anything any more or do wrong things -- those should be removed
 +
*** Example TableTreeViewer : Continue having the API doesn't hurt, there's no significant benefit removing it
 +
**** Alex: TableTree was completely broken on GTK for 2-3 years ... keeping such components that don't work properly lowers the quality
 +
**** Dani: Is there actual proof of bugs ? Or could it be working fine on Windows RCP ? If it's deprecated, people use it at own risk; do we really need to break them, if it provides value to some people on some Platforms ?
 +
**** John: In TableTreeViewer case, EMF had some generic code (was unclear if the path was ever taken) and CDT could update easily
 +
*** '''Summary''': scheduling for removal is OK with good arguments. Give Adopters a chance to respond before removal takes place.
 +
 
 +
** Q2: '''How to deal with the versions?'''
 +
*** Dani: Updating the major causes major pain on everyone (adoption work), so this should be avoided
 +
**** Actively developed plugins will notice source breakage when recompiling anyways -- no need to update the major for them.
 +
**** For dormant plugins (not recompiled), everyone will break when updating the major although only few may be affected - is it worth notifying those small percentage that might break ?
 +
**** Plugins who don't care recompiling may have to live with ClassNotFoundException
 +
**** Tooling exists: API Use Scan Tools can discover incorrect API references that are not announced by the versions
 +
*** '''Summary:''' Handle the Major with care -- in most cases, the cost of updating the major is not justified by the benefit.
 +
 
 +
** John: '''Announcement''' When thinking about removing something, we should announce that far and wide and ask for feedback
 +
*** Martin: But which channel is as effective as actually removing it ? There's always who don't actually listen...
 +
*** John: Still, giving a possibility to listen is important. Agree that mentioning in the release docs is not enough.
 +
*** Dani: When making a release, also send message with a link to the removals page (for all removals that are planned)
 +
** John: Mechanisms for maintaining binary compatibility while only breaking source compatibility (but it's a lot of work!)
 +
*** Dani: Agree, in this case better just leave it in there
 +
 
 +
** Alex: What to do next time, can we remove more stuff ?
 +
*** Martin: Should be at the discretion of the committers. They do the work. If they see the need for removal, they should be allowed to do so (as long as they play by the rules, like early announcement). Need to define what the rules are.
 +
 
 +
** John: There was an interesting discussion on cross-project, asking for well-known points in time where major breakage can occur
 +
*** Eg release but without all the deprecated at certain well-known point in time eg every 3-5 years
 +
*** '''AI''' ''continue that discussion on the Architecture Council''
 +
 
 +
** '''Summary:''' Essentially do what we did, plus more communication upfront, allow people to respond before deletion happens (to avoid churn)
 +
*** Committers still need to be able to delete stuff when they find it necessary.
 +
*** Updating the major (or not) to be decided case by case, but in many cases "breaking everyone" is not justified against "notifying few dormant plugins".
 +
 
 +
* Alex: '''Bumping the minimum GTK version again''' (may cause issues on Platforms like AIX -- to be discussed when it's time)
 +
 
  
 
<hr/>
 
<hr/>
'''August 7, 2013''' - Dani, Andrew, Martin, McQ
+
'''September 16, 2015''' - John, Martin
* Dani - '''Moving to more frequent releases''' to be discussed at the PC today
+
* John: '''API Removal Discussion'''
** McQ believes that aggregating monthly releases into a train can't work given the size of the train, so the monthly release wouldn't be useful to anyone
+
** No urgency now -- changes have been reverted for now, and scheduled for 2017
** Martin agrees that as a commercial adopter, stability (of the yearly train) is key: new features are interesting in one or two projects but not in the train
+
** Updating the major of a bundle knowingly breaks everyone/most adopters
** Moving faster with the train can't be at the expense of no longer getting backports of bugfixes to those releases that I have chosen to adopt !
+
*** In the past, breaking changes have often been small enough to work without increasing the major
** McQ: No more SR releases, but only converge the development streams every 4 months ? - Backports could be made but adopters would have to build themselves.
+
*** One can argue that removing TableTreeViewer is big enough to warrant updating the major
* What causes most grief when adopting a new Platform version ?
+
** Versioning packages has not been done in the past due to the huge upcoming maintenance effort when starting to do so
** Notifications have proven most problematic .. on either Resource / project system or XML / EMF models: subtle change of behavior can have a big impact when notifications trigger other notifications
+
** "Release Version" is decoupled from "bundle versions" already (and may move to date-based versions eg "2016.1" with rolling updates moving forward
*** Can it be fixed with a community effort ? [Not sure, most problems are in layers on top of the platform...]
+
** --&gt; will have more discussion next week
  
 
<hr/>
 
<hr/>
'''July 31, 2013''' - Dani, John, Andrew, Martin
+
'''September 9, 2015''' - Dani, Alex, Martin, John, McQ
* ide-dev list : "Eclipse as an IDE" from a cross project / cross PMC point of view
+
* John: '''Planning Council Updates'''
** Tools + Equinox + Packages ...
+
** 4 planned releases (March, June, September, December -- essentially end of each quarter) with flexible contents
* The "Uber Package..."
+
** Mid December rather than end to avoid churn, so this one is a little shorter
** Not recommendable. Better to improve Marketplace ... not all Train projects are on the Marketplace.
+
** Only June is "major" - allowing to drop off, or breaking changes; others are "minor"  
** Dani: As per the downloads page, it looks like the standard package doesn't have marketplace client ? - Martin: might be filtered; might be worth a bug if not visible.
+
** McQ want to reduce the number of simultaneous streams -- if "master" is more stable more often that's OK, but avoid too many "live" streams
*** filed {{bug|414305}}
+
 
* Looking forward to discussions on ide-dev.
+
* Software is getting more important - would be good to better support multicore
 +
 
 +
* John: '''IntelliJ change in licensing / sales model'''
 +
** Many eclipse-positive comments on the announcement blog
 +
** Possibility putting Money on Eclipse Development may become interesting for companies in this context
  
 
<hr/>
 
<hr/>
'''July 24, 2013''' - McQ, Dani, John
+
'''September 2, 2015''' - Dani, Alex, Martin, John
* Brief planning discussion. Kepler SR1 end-game plan released. Luna M1 is August 9th.
+
* Dani: '''EclipseDay India''' on Saturday, 200 attendees wanted to join, hat to cut to 150
* We will resume architecture team meetings on August 7th. John to remind team next week.
+
** Keynote by Mike Milinkovich - large Community
* John will be away Aug 1-16
+
  
'''July 17, 2013''' - McQ, Dani, John, Andrew
+
* Dani: '''Policy for and Mars.2'''
* Brief discussion of the "code smells" thread on cross-project list
+
** Do we want to stick to the "Service" model or allow feature updates ?
* Overall positive discussion and we hope to see good things come out of it
+
** Mars.1 winding down -- sticking to "Critical Fixes Only" for that
 +
** Too much in the maintenance stream causes risk of defocus ... are there relevant features that are worth the extra effort ?
 +
** Dani: Suggests to require PMC Approval for adding a feature in - example candidate: Improvements for HiDPI
 +
*** Also: What about version number (2nd digit version update), IP disclosures, Translations ... ?
 +
*** Dani would suggest sticking to 3rd digit update only in the marketing release number; but a Release Review would be needed
  
'''June 26, 2013''' - McQ, Dani, Martin, Andrew, John
+
'''August 26, 2015''' -  
* Andrew: '''Orion Browser API Standardization'''
+
* Dani/Alex/Martin can't join (traveling)
* John: '''More process around Kepler Maintenance Stream''' - 1 reviewer, similar to RC1 ?
+
  
 
<hr/>
 
<hr/>
'''June 19, 2013''' - John, Dani, Martin
+
'''August 19, 2015''' - Alex, Dani
* John/Dani: '''Kepler Retrospect'''
+
* nothing to discuss
** JDT Versioning: Bundles and features at 3.10 for Luna, Marketing version at 4.4
+
** Freeze Plan: Worked fine for Platform, but others on the Train didn't quite play by the rules
+
*** Dani to replace John on the Planning Council (phone meeting once per month)
+
* '''Rules of Engagement for Maintenance Releases'''
+
** JDT is in the middle of a release cycle, since doing Java 8
+
* {{Bug|411132}} '''Security Advisory''' regarding raw Javadoc - Eclipse help system not vulnerable, suggest improving the docs around "Help" setting to disallow opening external links
+
  
 
<hr/>
 
<hr/>
'''June 12, 2013''' - McQ, John, Martin, Dani, Andrew
+
'''August 12, 2015''' - John, Dani
* John: '''EclipseCon France Report''' - 2 day board meeting was good: strategic planning for what the Foundation should focus on
+
* John asked whether we run on Windows 10
* Dani: 4.3 ramp-down looks good ... but other projects on the release train ship significant changes late ?!?
+
** Dani: yes, the team already tested on it a few weeks ago. Runs smoothly one bug so far. Browser widget works despite new browser (Edge)
* Dani: Java 8 looking good
+
** ''Martin (added after the meeting): A CDT update is needed to keep the Terminal from hanging (see {{bug|474327}}, will release with Mars.1). Got some duplicates already. Workaround is switch the Win10 Console to "Legacy Mode".''
* John: Planning - e4 vs compatibility layer
+
* Dani would like to get plan feedback by Friday EOD
** McQ: Because we want e4 to be a complete Platform, it makes sense to look at our own editors and see what it takes to have them run on pure e4
+
** But that's on a case-by-case basis only
+
** There's still a lot of confusion around e4
+
  
 
<hr/>
 
<hr/>
'''May 29, 2013''' - Dani, Andrew, Martin
+
'''August 5, 2015''' - McQ, John, Dani, Alex, Martin
* Dani: '''4.3 Release Update''' - looking good, some minor doc fixes only for RC4.
+
* PC meeting later today (planning calendar, calling SR1/2 "Update 1/2" instead
* Martin: '''4.3 Standard Package''' with egit and mpc - also looking good.
+
** adding another release before Christmas might be a next step - even if Platform contributes identical bits
** Minor binary diffs traced down to an "encoding" flag in the JAR format which is not significant (see {{bug|408944}})
+
 
** Automated comparison of SDK against EPP are still possible when unzipping all Jar's and comparing the contents (actually listing contents with unzip -v is also fine)
+
* Dani: '''[[Eclipse/Mars Retrospective]]'''
 +
** Move more components to Tycho build? (Would still need Ant to test against final build/bits)
 +
** Contribution Review Dates: joined by some components but not all
 +
** Error Reporter: Interesting to look at top ten but the sheer number is too big
 +
*** John - based on Orion experience with similar error reporting :
 +
**** Looking at changes in reported issues is more interesting than looking at reports themselves
 +
**** Reports help getting contributions (But, Dani finds that "just adding a null check" is often not what's desired for Java .. though helpful for Javascript)
 +
 
 +
* Dani: Foundation IP team doesn't require updating copyright notices per contribution any more (since that information is in git anyways)
 +
** The Project has to agree
 +
** Some contributors like to have their name in the source -- that's OK, no requirement to remove author information, but no requirement to add either
 +
** Won't remove existing lists (they never claimed to be complete, since there always was the "...and others" copyright notice
 +
** Dani to sent [https://dev.eclipse.org/mhonarc/lists/eclipse-pmc/msg02422.html request for voting]
 +
 
 +
* Dani: Switching to '''Jetty 9.3.x (which requires JRE 8)'''
 +
** JRE 8 from Oracle (and also from IBM) exists for all Reference Platforms
 +
** Except Solaris, because we only support Solaris 32-bit and the JRE only exists as 64-bit
 +
** But the Plan for Neon is to have 64-bit Solaris support
 +
** New Language features in Java 8 are adopted, contributors would like to start using Java 8
 +
** McQ: In the past, staying on older Java was desired to enable more widespread use ... today, this argument does not seem valid any more, in fact likely more contributions / community is enabled by moving to Java 8
 +
** Dani: Only concern is some "non reference" Platforms like HP-UX might not have JREs initially; but that's OK as long as the reference platforms are good
 +
** '''AGREEMENT''' to move to JRE 8 and allow projects to use Java 8 in their code.
 +
 
 +
* Dani: Looking for a contributor for SWT improvements for GTK3
 +
 
 +
* Martin: '''libwebkitgtk-3 on Ubuntu 14 forcing GTK 2''' not working ?
 +
** Alex: Using libwebkitgtk-4 which is much more stable, but not implementing the full SWT API
 +
** Most distros don't ship libwebkit for gtk-2 any more since it's not supported upstream any more and has many security issues
 +
 
 +
* Alex: '''Build SWT at the Foundation'''
 +
** Work with the Foundation going well, expect to have RHEL machines deployed at the foundation next month
 +
 
  
 
<hr/>
 
<hr/>
'''May 22, 2013''' - Dani, Martin, John, McQ
+
'''July 15, 22 and 29, 2015''' -- no meeting
* John: '''4.3 Update''' - still 100 bugs open with 4.3 target milestone, need a reminder
+
** There's still some [[Platform_UI/Plan/4.3 | Platform/UI 4.3 Backlog]] - some keybindings, activation, about dlg; need to make some decisions what's in or what's out
+
** Don't work on the list until the last day ... for any 2 bugs fixed, there's probably 1 introduced so need to ramp down
+
** Release review: Docs, N&N looking good
+
* Google Android announcement - IntelliJ is well integrated and polished, but Eclipse has more plugins ... the 2 concepts are somewhat at odds
+
** Just one in the large ecosystem - but need to watch for a trend of others moving away
+
  
 
<hr/>
 
<hr/>
'''May 15, 2013''' - Dani, Martin, John, McQ
+
'''July 8, 2015''' - McQ, Dani, John, Martin, Alex
* John: Switching focus from Orion to Eclipse Platform for the endgame - will be away first week of June
+
* John: '''Cross-Language Tooling Discussion''' on the eclipse.org-architecture-council and ide-dev mailing lists
* Mike Milinkovich did a demo on Orion in the Zurich lab and at the Eclipse Stammtisch Zurich
+
* decided to cancel the upcoming July meetings
  
 
<hr/>
 
<hr/>
'''May 8, 2013''' - Dani, Martin, John, Andrew, McQ
+
'''July 1, 2015''' -- no meeting
* Dani: {{bug|403149}} '''Removing Tycho Dependency''' - AI John comment on the bug
+
** Martin would like to see a simple Doc page somewhere that explains how to fix the versions
+
** Dani thinks that any serious build would update pom versions automatically as part of the build
+
* Martin: {{bug|402509}} context menu filtering - request gentle nudge
+
* John: Will '''switch to Asterisk''' for the PMC from next week on - '''AI McQ''' update the invite
+
  
 
<hr/>
 
<hr/>
'''May 1, 2013''' - John, Dani, Andrew, McQ
+
'''June 24, 2015''' - McQ, Dani, Martin, Alex
* John: LTS now running IBM Juno maintenance builds in LTS forge. Some small details still being worked out.
+
* Dani: '''Java 9''' - <a href="http://marketplace.eclipse.org/content/eclipse-java%E2%84%A2-9-support-beta-mars">EAR Feature Patch</a> on the Marketplace NOW
* Dani: Gerrit can be configured to deny non-fast-forward merges. We agreed to request that all Eclipse project Gerrit repositories be configured in this way. See {{bug|402791}} for details.
+
** No JARs any more - JRE is doing things internally using "jimage" format; updated search etc to create projects and work against them
* Dani: Request for JUnit bundle to stop re-exporting Hamcrest bundle. Hamcrest was originally part of JUnit so this was done for compatibility reasons. We agreed that we will not do this because it breaks all users of JUnit bundle. See {{bug|403676}} for details.
+
** If the Jimage filesystem provider isn't backported, one has to run the IDE on Java9 in order to code Java9
 +
** Modules are just a list of packages (and can refer to other modules) - no real JSR describing the plan yet - seems like just a replacement of "Profiles" (and JARs)
  
 
<hr/>
 
<hr/>
'''April 24, 2013''' - John, Dani, Martin
+
'''June 17, 2015''' - Dani, John, Martin, Alex
* Dani: '''Upload Freeze Plan'''
+
* John: '''Mars''' Platform in good shape for Mars - EPP respin for Error Reporting
* Dani: '''Java 8 Update'''
+
* Dani: '''Crashes with Java 8''' - Potentially will add to the online README
* John: '''Pawel stepping down as Platform/Debug Lead'''
+
** Happens in the JIT, with latest Oracle Java 8 (with 8 Cores and very specific circumstances)
** Leaves Pin & Clone orphaned for next year. Working sets for expression view also not in Kepler.
+
** See {{Bug|465693}} - Probably https://bugs.openjdk.java.net/browse/JDK-8078262
 +
* Alex: '''XDG Application''' - looks like Docker but a similar idea
 +
** Environment description of the runtime - helps specifying the line-up of library versions that we test against and use
 +
** Big part of GNOME / GTK already pushing for it, might make sense to consider alignment
 +
** GNOME working towards compiling with a really old compiler, such that the physically identical bits can run against a large set of distros
 +
** See https://wiki.gnome.org/Projects/SandboxedApps
 +
** But if you want to try it out please read https://blogs.gnome.org/alexl/2015/06/17/testing-rawhide-apps-using-xdg-app/
  
 
<hr/>
 
<hr/>
'''April 17, 2013''' - John, Dani, Martin
 
* Martin: '''New Classic Package''' - Will commit SDK branding, and Egit Capability def
 
** CSS - Should inherit proper styling from Platform (most probably OK)
 
* John: '''API Baselines''' - remind teams to set API baselines
 
* Martin: {{bug|402509}} context menu filtering - request gentle nudge
 
* John: [[Platform_UI/Plan/4.3 |Triage of Platform UI issues to be addressed]]
 
  
 +
'''June 10, 2015''' - Dani, Alex, Martin
 +
* Dani: 4.5RC4 looking good, no more fixes planned
 +
* Dani: Working on Java 9 feature patch
 +
* Alex: PC discussing a change in the release train
 +
** Current common ground seems to be a request for more release points, and projects could decide whether they do features or maintenance
 +
** From Platform point of view, stability is key. Some key contributors not interested doing
 +
** Martin: How to also cater to contributors who want their contributions released soon ?
 +
*** Martin Idea: With Tycho, building the Platform is easier so ask contributors build themselves
 +
*** Or, open up a new "experimental" stream ?
 +
*** Dani Idea: Market milestone builds differently, as "fully consumable" would serve the same purpose
 +
* Martin: Tested eclipse-installer (Oomph), looking really really good now
  
 
<hr/>
 
<hr/>
'''April 3, 2013''' - McQ, Dani, John, Andrew
+
'''June 3, 2015''' - Alex, Dani, Martin, McQ, John
* John: Kepler draft plan update ready, please take a look and provide comments
+
* Dani: '''Mars Endgame'''
* We discussed EclipseCon. It was a very good event for Eclipse project. On desktop community is moving forward on Eclipse 4. There was lots of good feedback, and very little grumbling. Orion was very well represented, lots of talks and demos from several companies adopting it.
+
* Dani: Please vote for release review
  
 
<hr/>
 
<hr/>
'''March 20, 2013''' - McQ, Dani, Martin, Andrew
+
'''May 20, 2015''' - Dani, Alex, Martin, McQ
* Dani: '''Java 8''' - jdt.core making very good progress - almost everything compiles in the editor
+
* Dani: '''Security Update''' - Platform work done, Orbit updated, reached out to Wayne and other affected projects.
* Dani: '''pom files update''' - to be discussed in the arch call
+
* Dani: '''RC2 Build''' - too many bugs assigned, Lars on Vacation, Dani will fill in
* Martin: {{bug|402509}} '''Context Menus''' - no feedback, ping again
+
* McQ: '''Too Many Platforms Built?''' - Who's really hurt by "too many builds" ?
* Martin: {{bug|145635}} '''Pin & Clone'''
+
** Will meet with Mike & Foundation tomorrow, Alex is also interested (Dani to check).
** Dani - the feature itself is good and makes sense, would also like it in JDT
+
** '''The UI metaphor is new and would need some testing in the Field''' - McQ would like the patch in ASAP in a way that doesn't cause more swirl to start experimenting
+
** CDT would need to adopt it, upstream changes needed
+
** Current implementation showed quite a lot of ripples and bugs
+
*** Current impl breaks existing workflows, that's the big problem
+
** John: only 1 milestone left, if it appears in M7 and breaks any adopters they have little time to react;
+
*** Can loop-in JDT and CDT, but there might be others ...
+
*** Was PTP involved in any way ? They could also be broken, they have very special requirements
+
** McQ: Do we have ownership of this work ? - If we have a clear need and a clear owner working on it we could give it a try
+
** '''AI Martin''' (1) Clarify with CDT why they didn't like the feature and what are their plans; all the rest comes after that eg PTP, Pawel, can it be done in a non-breaking way
+
* John: {{bug|402912}} '''Significant Memory Leak in M6''' fixed this week: noticable if eclipse running for a long time
+
** Workaround for M6: Turn off Workbench Autosave feature by setting it to 0
+
** ''AI Post to cross-project'' - people doing demos at Eclipsecon might want to use the workaround
+
* Martin: {{bug|397896}} '''New Classic Package''' - initial package done but unusable while the SDK branding bundle's contents is not migrated
+
** Martin will continue pushing for this to happen - fallback would be not
+
** Not much risk in judging whether it's good or not, only binary diff needed
+
* John: {{bug|380325}} '''Java 7 filesystem fragment'''
+
** McQ do we know performance implications, could we get rid of the native bundles ?
+
** Martin would like to have the fragment in all builds, to make it easier to test performance etc implications
+
* Martin: {{bug|403589}} '''eclipse.inf'''
+
** Different binary bits depending on distribution channel is bad ... Tycho removed
+
** Defect in post-processing (why does it add eclipse.inf) or defect in bundle preparation (why isn't eclipse.inf in there) ?
+
** Maybe related to pack200 conditioning - Martin thinks that eclipse.inf was used in the past as a marker to know whether pack200 conditioning has happened ... now downstream aggregator conditions and adds eclipse.inf
+
** '''AI John investigate'''
+
  
 
<hr/>
 
<hr/>
'''March 13, 2013''' - McQ, John, Martin, Dani
+
'''May 13, 2015''' - McQ, John, Alex, Martin
* Andrew: '''{{bug|397896}} final throughts on the EPP package'''
+
* John, Dani - Mars Endgame looking good
** Move forward with [https://bugs.eclipse.org/bugs/show_bug.cgi?id=397896#c17 ]
+
* Alex - {{bug|465874}} Lucene 5 looking good, almost done - Ready to commit as soon as CQs are in and Mars+1 is open
** Testing - could find someone if it's just "use during the test pass"
+
* JDT for Java 9 - will need a wider discussion with EMO on make it easier to publish the work, e.g. in normal builds
** Q: Can the EPP build be done frequently so it's available 1 week before the milestone for testing ?
+
* Martin: '''{{bug|402509}} context menu filtering'''
+
** Would like to get some advice from Platform on the approach; some trajectory of a solution moving forward
+
** Not a must-have for Kepler, but would like to see where this is heading
+
** '''AI McQ''' find Platform folk to discuss this
+
* John: '''Eclipse 4 API Status'''
+
** Publishing a "usable subset" of the former provisional API as final: model, core services; consume injection
+
** Allows building a real Eclipse 4 App now on API
+
*** Mostly clean-up, documentation; removing some bad stuff
+
*** Writing an App on Kepler E4 API might actually be able to run on Juno
+
** Some of the advanced stuff remains provisional for now, eg define injection
+
* John: '''Plan Update''' - No permission to update in the PMI
+
* McQ: '''CBI''' / Bad Launcher
+
** Have an idea that doing some little extra work after the CBI build might be good enough for now
+
** HP-UX CBI Build doesn't start out of the box (will likely stay a known issue for M6)
+
* Martin: '''{{bug|380325}} Java7 EFS Plugin''': Build ?
+
  
 
<hr/>
 
<hr/>
'''March 6, 2013''' - McQ, John, Martin, Andrew
+
'''May 6, 2015''' - McQ, Dani, Martin, John
* Martin: '''{{bug|402509}} context menu filtering'''
+
* Dani: '''Java 9 timing''' - slight delay
** AI Martin ask engineers document what we're doing today
+
* Dani: RC1 preps
* Martin: '''{{bug|397896}} EPP vs Classic''' - how to proceed
+
** 2-day test pass went fine - 2 severe issues found, will be addressed
** Martin's recent findings on Marketplace
+
** Request to watch PMC mailing list for API exceptions and defect approvals
*** There's p2, Marketplace, Packages in the Open but they are only parts of the solution
+
* John: '''PC Discussion on Release Cycles'''
*** There's commercial installers from EclipseSource (Yoxos), Genuitec, IBM
+
** Multiple releases per year PLUS maintenance streams seems like overkill
*** John: p2 simplified UI (eg Webtools Server Adaptors; Mylyn)
+
** Consider an approach like Orion that just moves constantly forward
** What's missing ? David too booked ?
+
** Especially for the Platform, being rock solid is most important. Still to attract new contributors we need to allow more frequent "feature updates".
* John: '''CBI Builds in Kepler''' - SDK in good shape but repo and Equinox downloadpage not quite right yet, some might take until M6
+
*** A model where both "stable/maintenance" _and_ "features" are contributed to the train might be too much work/overhead.
* John: '''Delete old Platform/UI Branches''' - any PMC Policy ? No, convert branches to tags
+
*** Consider a model like Ubuntu, ... with some release numbers being "stable/LTS base" and others being "in-between feature releases" ?
* John: '''API Freeze next week''' - some (modest) new Eclipse 4 API's
+
*** Consider a model like LTS for maintenance fixes / aside mainstream just moving forward ?
** McQ recommends going for a "complete, but minimal subset of what people will want to do", rather than too many convenience methods
+
 
** John: Some API has been provisional for 3 years - can't make wholesale changes now for the fun of it
+
 
*** May phase in some changes by adding @noreference rather than deleting stuff
+
'''April 15, 2015''' - Dani, John, McQ, Alex, Martin
*** In some cases there's pressure to use interfaces rather than classes, in order to be able and leverage Java 8 constructs
+
* Dani: '''Java 1.7 Changes'''
* Orion - anybody going to JSConf ?
+
** Some bundles have been moved to a 1.7 BREE by new committers, even after API freeze
 +
** Rule has always been "we move up when there's a reason to move up". We won't move up without reason.
 +
*** Dani: Moving the BREE may even cause API changes, so should only be done when incrementing the minor version (5% risk)
 +
*** Alex: Such updates allow staying current and not get to "rewrite is needed" state (thus needed) but has to happen before M6 (API freeze)
 +
** Alex suggest not accepting additional changes, but not reverting either (to avoid churn)
 +
* Dani: '''Batik 1.6 update'''
  
 
<hr/>
 
<hr/>
'''February 27, 2013''' - John, Andrew, Dani
+
'''April 8, 2015''' - Dani, Martin, Alex, John, McQ
* Nothing noteworthy
+
* Dani: '''Batik''' - Platform is good, Train may need to update, perhaps updating one bundle only would suffice. John will follow up.
 +
* Alex: '''SWT for GTK 3 News'''
 +
** GTK port finally decoupled from X11 - it renders on Wayland now, can switch the renderer to a pure HTML one
 +
** This opens up opportunities (but depends on hosts that have GTK).
 +
 
  
 
<hr/>
 
<hr/>
'''February 20, 2013''' - McQ, John, Dani, Martin, Andrew
+
'''April 1, 2015''' - McQ, Alex, Martin, Dani (Regrets: John travelling)
* John: '''Orion Release Review''', please give feedback
+
* Alex: '''GTK 3.16''' seeing issues again - fixed some crashes, but scrolling is still entirely broken
 +
** SWT uses a number of things that GTK declares as "implementation detail"
 +
* PMC approval on piggyback CQ's (AC question forwarded by John)
 +
** Dani sent [https://dev.eclipse.org/mhonarc/lists/eclipse-pmc/msg02332.html our position] to John in order to update the AC
  
 
<hr/>
 
<hr/>
'''February 13, 2013'''
+
'''March 18, 2015''' - Dani, Alex, Martin, McQ, John
* {{bug|156134}} re-exporting debug dependencies
+
* John: '''EclipseCon''' - Bigger this year due to LocationTech (750 attendees)
 +
** Mark Reinhold keynote and "after-session" on Java 9
 +
** Much interest in Orion JS tooling / editor, also on desktop
 +
** Public face of Eclipse Platform at the conference was much more diverse than in the past (Lars Vogel, Max Anderson, Google ...)
 +
* Dani: {{bug|458730}} '''Mars Plan Update'''
 +
* Dani: '''e4 project leadership''' approved by EMO
 +
* Dani: Szymon Brandys resigned as Platform/Resources co-lead. Need to +1 on the mailing list
  
 
<hr/>
 
<hr/>
'''February 6, 2013''' - John, Dani, Martin
+
 
* John: '''M5a and SR2 RC4'''
+
'''March 11, 2015 - no meeting (EclipseCon)'''
* John: Pawel and Platform / Debug work (Pin & Clone)
+
** Only adopt when it's really ready and satisfies all criteria, otherwise not into Kepler
+
** Maybe pull out Debug plugins into a feature of their own ?
+
  
 
<hr/>
 
<hr/>
'''January 30, 2013''' - McQ, John, Dani, Martin, Andrew
+
 
* John: '''SR2 RC3''' looking good - want to know about any remaining issues
+
'''March 4, 2015''' - Dani, McQ, Martin, John
* Dani: '''Java 8 Update''' - Markus Keller will move from JDT UI to JDT Core, taking over JSR-308
+
* Dani: '''e4 leadership''' - Dani will volunteer to co-lead
* John: '''NODE Dependency in Orion (exempt pre-req)'''
+
* Dani: '''BREEs''' - documentation about how to pick the EE
** Not shipping NODE ourselves, pushing to NODE package manager instead (or clone from git)
+
** Recommending the "earliest generally supported JRE that provides the capabilities you need"
** Andrew: Is it a workswith ?
+
** Would like an URL on the page pointing to the most recent plan (talking to Wayne)
** Martin: Is there any overlap with the Java portion ?
+
* John: '''greatfix contest'''
*** The server code is completely distinct from Java, but the same client can interact with both
+
** Dani: Working well - some very small contributions but some also very large (eg Customize Perspective fixes)
 +
* John: '''EclipseCon''' - numbers looking good; join Planning Council Breakfast as delegate for Dani
  
 
<hr/>
 
<hr/>
'''January 24, 2013''' -  
+
'''February 25, 2015''' - Dani, Martin McQ
* Martin: '''4.3 and 3.8 dual-stream''' - [http://www.eclipse.org/projects/project-plan.php?projectid=webtools#themes_and_priorities Webtools project plan]
+
* No topics
** egit, mylyn, dtp have been doing both n + n-1 for a long time
+
** Technically, running on both should be possible if Platform API is used (except for the changes in Theming)
+
** The Eclipse Community needs to advance the latest (4.3)
+
** IBM product teams have been told not to forward at all if they can't forward to 4.x - shipping on 4.2
+
** John: Having '''wider ranges of tolerance''' is something we should be able to do (otherwise our plugin system is failing)
+
** John: Java8 will be the first killer feature in 4.x
+
* Dani: '''Java 8'''
+
** Will provide feature patches as soon as it makes sense - early draft, participating in expert group
+
** Want to have the compiler and editor ready when Java 8 goes GA - initial refactoring etc in SR1 - full feature set in the next release
+
* John: '''CBI update'''
+
** Consider switch after M5
+
  
 
<hr/>
 
<hr/>
'''January 17, 2013''' - McQ, John, Martin
+
'''February 18, 2015''' - Dani, Alex, Martin
* John: '''{{bug|397896}} EPP vs Classic'''
+
* Alex: '''Building Native Launchers'''
** Could volunteer to own the EPP package from Platform POV
+
** Current way of building is kinda unpredictable - even if getting some agreement on versions to use, results are kinda unpredictable
** Then Wayne would own the decision of RCP/RAP vs Classic - what's the difference, keep both or unify
+
** Pushing towards Hudson RHEL builders at least at the EF to get more transparency and automation - attempt to mimic the infrastructure at IBM
* John: '''Test Failures on I-Builds'''
+
** Looking at 3 primary architectures (at the EF) for Linux vs. secondary architectures (non-public builders potentially)
** Move away tests that have been failing for 9 months
+
* Dani: Great initiative, but other (non-EF) builders must not be broken
** Dani: Most tests are actually down to 0 failures
+
** EF doesn't allow any commercial tools (but currently, e.g. Windows launchers are built with MSVS)
* John: '''CBI / Maven Builds'''
+
* Alex is willing to spend time to get Linux builds running; but can't help with other architectures
** Appears to be fragile at the moment - Maven .micro releases are breaking the build!
+
** Martin: great approach - for Windows, using a cross-compiler on Linux might be interesting (after Linux native works)
 +
* Alex: This is just phase one - getting rid of the binaries in git repos might be phase 2 (since the checked-in binaries easily cause inconsistencies between Java and Native side)
 +
** Martin: Checked-in binaries help consumers and contributors who just want to make a Java change
 +
** Dani: Checked-in binaries are also used for comparing build results for expected vs accidental changes
 +
 
 +
* Alex: '''{{bug|459399}} - Policy for recommended minimum execution environments for bundles'''
 +
** Dani: It works today
 +
*** To run Eclipse, Java 8 or Java 9 can be used (minimum BREE has no impact)
 +
*** To modify the source, a new JRE can be used but then the Execution Environment Descriptions need to be installed
 +
** Policy as discussed in the past: Each project can increase the BREE if there is a real need (such as generifying) and no upstream clients are broken
 +
*** But don't change the BREE without justification -- changing the BREE always has some effect, such as new warnings that would need to be addressed
 +
*** Suggested BREE for new bundles has already been changed by Lars
 +
* Alex: Even for bundles in "maintenance mode", old BREE causes issues for people who build from source (who have to change compilers etc)
 +
* No conclusion so far (Alex and Dani disagree)
 +
 
 +
* Dani: '''e4 leadership'''
 +
** Mature bits being moved to Eclipse - e4 remaining as an incubator to keep alive for experiments with low entry barrier
  
 
<hr/>
 
<hr/>
'''January 10, 2013''' - McQ, John, Dani, Martin
+
'''February 11, 2015''' - Dani, Alex
* McQ: '''CBI''' - Switching Platform build to CBI for SR2 is not doable
+
* no topics
** Want to make CBI work for Juno since it's the LTS stream
+
** CBI SDK builds are good at this point, it's only a couple of minor issues (shape of repos, download page, ...
+
** When to switch to CBI in the Kepler Stream ? - Proposal do do it immediately
+
* CBI patches waiting for Platform to pick up
+
  
 
<hr/>
 
<hr/>
'''January 3, 2013''' - McQ, Andrew, John, Dani
 
* Andrew will recommend good conferences to promote Orion
 
  
 +
'''February 4, 2015''' - Dani, Alex, Martin
 +
* Alex: With GTK-3.15.[345] , Eclipse is entirely unusable
 +
** Alex has some dirty workarounds to make it start, but still many issues like trees not painted, ...
 +
** Crash on startup identified to be GTK bug. Fix to be released in 3.15.6 https://git.gnome.org/browse/gtk+/commit/?id=edec64cda3d4518b4e87d5ea5d287d4570ba9933
 +
* Dani: Working on Solaris 64-bit
 +
 +
<hr/>
 +
 +
'''January 28, 2015''' - Dani, Alex, John
 +
* Dani: Switch Mac OS X 10.9 with 10.10 in Mars target environments
 +
** No objections
 +
* Alex: Looking for any Eclipse related activity @Fosdem
 +
<hr/>
 +
 +
'''January 21, 2015''' - Dani, Alex, Martin, McQ
 +
* Alex: '''Process for allowing non-committers extended bugzilla privileges (for bug triage)?'''
 +
** Dani: Yes a process exists. Send bugzilla username to Dani.
 +
* Alex: '''New resource for helping with SWT'''
 +
* Dani: '''Platform/UI co-lead'''
 +
* Dani: Solaris: Java 8 will only support 64 bits on both Intel and SPARC --&gt; IBM SWT Team considering to invest in getting patches in for 64-bit Solaris
 +
 +
<hr/>
 +
'''January 14, 2015''' - Dani, Alex, Martin, McQ, John
 +
* Dani: Update on Platform/UI Leadership: Daniel Rolka left IBM and for now has no time to contribute. He stepped down as co-lead and nominated Lars Vogel
 +
* Dani: Solaris x86 64-bit support - patches exist, but no machine available. No luck to get one from Oracle or via Eclipse Foundation. We will not support Solaris x86 64-bit unless someone makes a machine available
 +
<hr/>
 +
 +
'''January 7, 2015''' - Dani, Alex, Martin, McQ, John
 +
* Dani: '''Platform/UI Leadership'''
 +
* John: '''Git security issue''' - pick up a patch for Jgit in the packages before SR2? - Mostly an EPP
 
<hr/>
 
<hr/>
  
 
= Archive =
 
= Archive =
 +
* [[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 2012 | Archive of Meeting Minutes from 2012]]
 
* [[Eclipse/PMC/Minutes 2011 | Archive of Meeting Minutes from 2011]]
 
* [[Eclipse/PMC/Minutes 2011 | Archive of Meeting Minutes from 2011]]
 
* [[Eclipse/PMC/Minutes 2010 | Archive of Meeting Minutes from 2010]]
 
* [[Eclipse/PMC/Minutes 2010 | Archive of Meeting Minutes from 2010]]
 
* [[Eclipse/PMC/Minutes 2009 | Archive of Meeting Minutes from 2009]]
 
* [[Eclipse/PMC/Minutes 2009 | Archive of Meeting Minutes from 2009]]

Revision as of 12:41, 24 November 2015

Documents

Some documents written and/or used by the PMC:

Meeting Schedule

The Eclipse Project PMC has a weekly phone meeting every Wednesday at 10.30am EST.

Meeting Minutes

November 25, 2015 - McQ, Martin, Alex

  • Alex: Bumping SWT to Java8
    • Lars wants to use Lambdas bug 481195; Markus keller wants static helper methods;
    • Stephan Herrmann - University Research for Thread safety through typed annotations
      • Are they ready to contribute? - Probably yes, needs to be clarified; having better dev support for Thread Safety will be a huge help
      • Dani: Thinks that going to Java8 feels a bit early for SWT, which is at the bottom of the technology stack ... would prefer 1 year later
      • John: Lambda support doesn't necessarily require SWT to be Java 8 itself (it could just be more lambda friendly)
        • Won't help with base listeners, but probably with mouse events and related .. follow up in the bugreport
        • Labdas are more than syntactic sugar, it's more efficient ... still there is more value in Thread safety annotations
      • McQ: Assumes there would be an extensive discussion on cross-project anyways ... but there is evidence now we could get value from doing this.
  • Dani: Update on Move of platform.text
    • Approval from IP, will soon move to platform.ui - will keep platform.text bugzilla.
  • John: FEEP
  • McQ: Platform Support
    • Many Platforms are not really active - IBM keeps alive some of them, for example RHEL4
    • Recent mailinglist asking for Mac 32bit, have we done enough on announcements ?
    • Agreement there's no case for catering more to people who don't read announcements and follow the project. Having a mailinglist ask once in a while is OK.
    • Dani: Planning Update for Neon / M4 - please comment on the bug.
      • John: Plan document is not really exhaustive on the oldest working Platform - RHEL4 surely won't work in Neon.
    • Alex: Consider a "Build your Own" approach for the more obscure Platforms? - Frees us from keeping older binaries in sync
      • Did that for ARM32 and ARM64 in master - can build by just calling maven
      • McQ: Who would ever validate that scripts are still valid... (Linux community: provides no binaries at all, who validates?)
      • Alex: Providing scripts is a lot less work than providing stable and widely compatible binaries (about 1/3 of the work)

November 18, 2015 - Alex, John, Dani


November 11, 2015 - McQ, John, Dani

  • Discussed new meeting time that works for Martin
    • John to send a note that proposes Tuesday, 11:00 EST / 17:00 CET (starting in two weeks)
  • John: Alex mentioned at EclipseCon that there's no one in SWT team overlooking cross-platform, e.g. to craft new APIs
    • owning one platform is a full-time job
    • would need another person in SWT
    • for now one of the two co-leads needs to own that task - Dani to talk to Pradeep and the co-leads
  • John to Dani: how was EclipseCon
    • Dani: Great! Lots of talking to people; spent quite some time at the Hackathon; only saw 4 talks

October 28, 2015 - McQ, John, Alex, Dani

  • Dani: Discuss new meeting time that works for Martin
    • decided that John will send out a doodle poll
  • Dani: Discuss our position regarding the removal of committer emeritus (bug 480670)
    • everyone agreed that we would like to keep this for the following reasons:
      • it is a good way reward those committers who invested lots of their time and made significant contributions to a project
      • it makes no sense to remove something that currently works and ask projects to maintain this on their website
    • we have to make sure that the emeritus list doesn't get stale

October 21, 2015 - McQ, Alex, Dani

  • Dani: so far no negative vote in the vote to move platform.text into platform.ui
  • McQ: Martin can no longer join, McQ would like to move the meeting
    • detailed several alternatives but no fit yet
    • decided to continue the discussion in our next meeting

October 14, 2015 - McQ, John, Alex, Dani

  • Dani: Community asked to move platform.text into platform.ui (see https://dev.eclipse.org/mhonarc/lists/platform-text-dev/msg00484.html)
    • 3 solutions:
      • make the move
      • make a more radical move to merge everything into 'Platform'
      • leave things as is and let new people join platform.text
    • McQ: merging everything together is not an option. Skills are too different. Resources, Debug and SWT need to be kept separate.
    • Dani: fine with the move as long as it does not serve as argument to merge everything into one pot
    • Alex: committers need to accept the move
    • PMC decision: OK with the move but Dani to ask the platform.text and platform.ui committers whether they are both OK with it. Dani to become co-lead of Platform UI
  • John from Board Meeting: Eclipse Foundation wants to change perception that Eclipse is just an IDE. Therefore they would like to change the name of our project ("Eclipse").
    • McQ:
      • this will not be for free. The name is used at many places (code, webpage, Help) and also by companies in their marketing
      • maybe we just have to accept we made a mistake in the beginning and now live with it
      • can't think of a good name - which indicates we shouldn't change it ("Platform" is not good and "Eclipse SDK" or "Eclipse IDE" hide that it is the base for "RCP" apps)
    • decided to talk about this again in the next call

October 7, 2015 - McQ, John, Alex, Dani, Martin

  • Dani: bug 108668 Default Text Encoding UTF-8 ?
    • On Linux and Mac, the Platform encoding is UTF-8 ; on Windows it's Cp1252 in most countries around the globe, even with Windows 10
    • Using the Platform encoding ensures interoperability with all local tools (editors, compilers, ...)
      • Desire for UTF-8 only for Windows exchanging files with users on other systems
      • Changing the encoding of an existing workspace after the fact is a no go (risk of data corruption when loading/saving a file, some encodings are lossy)
      • Using an encoding different than the OS encoding is problematic too (risk of data corruption when importing or D&D files from the OS)
    • Proposal 1: UTF-8 on new empty workspaces on Windows ? --> Might mean that external tools don't work as expected
    • Proposal 2: Make users aware (Restore Oomph Welcome, which was disabled via bug 459486) ? --> But many users don't understand implications, other tools also don't do this
    • Proposal 3: Ask for encoding when team-sharing since only team-shared projects cause issues (eg EGit hook) ? --> But on "push" it may be too late
    • Martin: Encoding describes content, so should be managed with the content (as a project setting)
      • --> Proposal 4: Move to a model where we encourage setting the project-level encoding preference
        • When creating a project, set the workspace default on project level automatically --> ensures that projects remain sane over their lifetime
        • For projects lacking the project-level preference, introduce a Problem Marker (Warning) with quick fix to either UTF-8 or workspace default
    • Decision:
      • We won't change the workspace default -- no use breaking existing users
      • We'll set the project encoding pro-actively
    • Open questions:
      • Do we need tooling to convert project from encoding A to encoding B (if project preference was set incorrectly initially) ?
      • Shall we try setting source encoding on drag-and-drop, or shall the project dictate the policy ?

September 30, 2015 - McQ, John, Alex, Dani

  • Dani: will send a note to PMC list asking to approve new Debug leadership (Sarika)
  • Dani: we should finalize our API removal discussion from last week
    • agreed that APIs marked for removal have to be annotated with @noreference, @noextend and @noimplement
    • agreed that components should be allowed to remove API but they have to provide good reasons
    • agreed that we won't allow to delete APIs simply because they are deprecated
    • agreed that the PMC will decide case by case i.e. there will be no general rule
    • regarding version numbering we decided to also decide this case by case
    • Dani to update the removal document and have it reviewed by the PMC

September 23, 2015 - Dani, John, Alex, Martin

  • Dani: JDT Core - Co-lead going to step up
  • Dani: API Removal Discussion
    • Q1: When do we actually delete API? What's the benefit compared to the pain that we cause ?
      • Example of methods that don't do anything any more or do wrong things -- those should be removed
      • Example TableTreeViewer : Continue having the API doesn't hurt, there's no significant benefit removing it
        • Alex: TableTree was completely broken on GTK for 2-3 years ... keeping such components that don't work properly lowers the quality
        • Dani: Is there actual proof of bugs ? Or could it be working fine on Windows RCP ? If it's deprecated, people use it at own risk; do we really need to break them, if it provides value to some people on some Platforms ?
        • John: In TableTreeViewer case, EMF had some generic code (was unclear if the path was ever taken) and CDT could update easily
      • Summary: scheduling for removal is OK with good arguments. Give Adopters a chance to respond before removal takes place.
    • Q2: How to deal with the versions?
      • Dani: Updating the major causes major pain on everyone (adoption work), so this should be avoided
        • Actively developed plugins will notice source breakage when recompiling anyways -- no need to update the major for them.
        • For dormant plugins (not recompiled), everyone will break when updating the major although only few may be affected - is it worth notifying those small percentage that might break ?
        • Plugins who don't care recompiling may have to live with ClassNotFoundException
        • Tooling exists: API Use Scan Tools can discover incorrect API references that are not announced by the versions
      • Summary: Handle the Major with care -- in most cases, the cost of updating the major is not justified by the benefit.
    • John: Announcement When thinking about removing something, we should announce that far and wide and ask for feedback
      • Martin: But which channel is as effective as actually removing it ? There's always who don't actually listen...
      • John: Still, giving a possibility to listen is important. Agree that mentioning in the release docs is not enough.
      • Dani: When making a release, also send message with a link to the removals page (for all removals that are planned)
    • John: Mechanisms for maintaining binary compatibility while only breaking source compatibility (but it's a lot of work!)
      • Dani: Agree, in this case better just leave it in there
    • Alex: What to do next time, can we remove more stuff ?
      • Martin: Should be at the discretion of the committers. They do the work. If they see the need for removal, they should be allowed to do so (as long as they play by the rules, like early announcement). Need to define what the rules are.
    • John: There was an interesting discussion on cross-project, asking for well-known points in time where major breakage can occur
      • Eg release but without all the deprecated at certain well-known point in time eg every 3-5 years
      • AI continue that discussion on the Architecture Council
    • Summary: Essentially do what we did, plus more communication upfront, allow people to respond before deletion happens (to avoid churn)
      • Committers still need to be able to delete stuff when they find it necessary.
      • Updating the major (or not) to be decided case by case, but in many cases "breaking everyone" is not justified against "notifying few dormant plugins".
  • Alex: Bumping the minimum GTK version again (may cause issues on Platforms like AIX -- to be discussed when it's time)



September 16, 2015 - John, Martin

  • John: API Removal Discussion
    • No urgency now -- changes have been reverted for now, and scheduled for 2017
    • Updating the major of a bundle knowingly breaks everyone/most adopters
      • In the past, breaking changes have often been small enough to work without increasing the major
      • One can argue that removing TableTreeViewer is big enough to warrant updating the major
    • Versioning packages has not been done in the past due to the huge upcoming maintenance effort when starting to do so
    • "Release Version" is decoupled from "bundle versions" already (and may move to date-based versions eg "2016.1" with rolling updates moving forward
    • --> will have more discussion next week

September 9, 2015 - Dani, Alex, Martin, John, McQ

  • John: Planning Council Updates
    • 4 planned releases (March, June, September, December -- essentially end of each quarter) with flexible contents
    • Mid December rather than end to avoid churn, so this one is a little shorter
    • Only June is "major" - allowing to drop off, or breaking changes; others are "minor"
    • McQ want to reduce the number of simultaneous streams -- if "master" is more stable more often that's OK, but avoid too many "live" streams
  • Software is getting more important - would be good to better support multicore
  • John: IntelliJ change in licensing / sales model
    • Many eclipse-positive comments on the announcement blog
    • Possibility putting Money on Eclipse Development may become interesting for companies in this context

September 2, 2015 - Dani, Alex, Martin, John

  • Dani: EclipseDay India on Saturday, 200 attendees wanted to join, hat to cut to 150
    • Keynote by Mike Milinkovich - large Community
  • Dani: Policy for and Mars.2
    • Do we want to stick to the "Service" model or allow feature updates ?
    • Mars.1 winding down -- sticking to "Critical Fixes Only" for that
    • Too much in the maintenance stream causes risk of defocus ... are there relevant features that are worth the extra effort ?
    • Dani: Suggests to require PMC Approval for adding a feature in - example candidate: Improvements for HiDPI
      • Also: What about version number (2nd digit version update), IP disclosures, Translations ... ?
      • Dani would suggest sticking to 3rd digit update only in the marketing release number; but a Release Review would be needed

August 26, 2015 -

  • Dani/Alex/Martin can't join (traveling)

August 19, 2015 - Alex, Dani

  • nothing to discuss

August 12, 2015 - John, Dani

  • John asked whether we run on Windows 10
    • Dani: yes, the team already tested on it a few weeks ago. Runs smoothly one bug so far. Browser widget works despite new browser (Edge)
    • Martin (added after the meeting): A CDT update is needed to keep the Terminal from hanging (see bug 474327, will release with Mars.1). Got some duplicates already. Workaround is switch the Win10 Console to "Legacy Mode".
  • Dani would like to get plan feedback by Friday EOD

August 5, 2015 - McQ, John, Dani, Alex, Martin

  • PC meeting later today (planning calendar, calling SR1/2 "Update 1/2" instead
    • adding another release before Christmas might be a next step - even if Platform contributes identical bits
  • Dani: Eclipse/Mars Retrospective
    • Move more components to Tycho build? (Would still need Ant to test against final build/bits)
    • Contribution Review Dates: joined by some components but not all
    • Error Reporter: Interesting to look at top ten but the sheer number is too big
      • John - based on Orion experience with similar error reporting :
        • Looking at changes in reported issues is more interesting than looking at reports themselves
        • Reports help getting contributions (But, Dani finds that "just adding a null check" is often not what's desired for Java .. though helpful for Javascript)
  • Dani: Foundation IP team doesn't require updating copyright notices per contribution any more (since that information is in git anyways)
    • The Project has to agree
    • Some contributors like to have their name in the source -- that's OK, no requirement to remove author information, but no requirement to add either
    • Won't remove existing lists (they never claimed to be complete, since there always was the "...and others" copyright notice
    • Dani to sent request for voting
  • Dani: Switching to Jetty 9.3.x (which requires JRE 8)
    • JRE 8 from Oracle (and also from IBM) exists for all Reference Platforms
    • Except Solaris, because we only support Solaris 32-bit and the JRE only exists as 64-bit
    • But the Plan for Neon is to have 64-bit Solaris support
    • New Language features in Java 8 are adopted, contributors would like to start using Java 8
    • McQ: In the past, staying on older Java was desired to enable more widespread use ... today, this argument does not seem valid any more, in fact likely more contributions / community is enabled by moving to Java 8
    • Dani: Only concern is some "non reference" Platforms like HP-UX might not have JREs initially; but that's OK as long as the reference platforms are good
    • AGREEMENT to move to JRE 8 and allow projects to use Java 8 in their code.
  • Dani: Looking for a contributor for SWT improvements for GTK3
  • Martin: libwebkitgtk-3 on Ubuntu 14 forcing GTK 2 not working ?
    • Alex: Using libwebkitgtk-4 which is much more stable, but not implementing the full SWT API
    • Most distros don't ship libwebkit for gtk-2 any more since it's not supported upstream any more and has many security issues
  • Alex: Build SWT at the Foundation
    • Work with the Foundation going well, expect to have RHEL machines deployed at the foundation next month



July 15, 22 and 29, 2015 -- no meeting


July 8, 2015 - McQ, Dani, John, Martin, Alex

  • John: Cross-Language Tooling Discussion on the eclipse.org-architecture-council and ide-dev mailing lists
  • decided to cancel the upcoming July meetings

July 1, 2015 -- no meeting


June 24, 2015 - McQ, Dani, Martin, Alex

  • Dani: Java 9 - <a href="http://marketplace.eclipse.org/content/eclipse-java%E2%84%A2-9-support-beta-mars">EAR Feature Patch</a> on the Marketplace NOW
    • No JARs any more - JRE is doing things internally using "jimage" format; updated search etc to create projects and work against them
    • If the Jimage filesystem provider isn't backported, one has to run the IDE on Java9 in order to code Java9
    • Modules are just a list of packages (and can refer to other modules) - no real JSR describing the plan yet - seems like just a replacement of "Profiles" (and JARs)

June 17, 2015 - Dani, John, Martin, Alex


June 10, 2015 - Dani, Alex, Martin

  • Dani: 4.5RC4 looking good, no more fixes planned
  • Dani: Working on Java 9 feature patch
  • Alex: PC discussing a change in the release train
    • Current common ground seems to be a request for more release points, and projects could decide whether they do features or maintenance
    • From Platform point of view, stability is key. Some key contributors not interested doing
    • Martin: How to also cater to contributors who want their contributions released soon ?
      • Martin Idea: With Tycho, building the Platform is easier so ask contributors build themselves
      • Or, open up a new "experimental" stream ?
      • Dani Idea: Market milestone builds differently, as "fully consumable" would serve the same purpose
  • Martin: Tested eclipse-installer (Oomph), looking really really good now

June 3, 2015 - Alex, Dani, Martin, McQ, John

  • Dani: Mars Endgame
  • Dani: Please vote for release review

May 20, 2015 - Dani, Alex, Martin, McQ

  • Dani: Security Update - Platform work done, Orbit updated, reached out to Wayne and other affected projects.
  • Dani: RC2 Build - too many bugs assigned, Lars on Vacation, Dani will fill in
  • McQ: Too Many Platforms Built? - Who's really hurt by "too many builds" ?
    • Will meet with Mike & Foundation tomorrow, Alex is also interested (Dani to check).

May 13, 2015 - McQ, John, Alex, Martin

  • John, Dani - Mars Endgame looking good
  • Alex - bug 465874 Lucene 5 looking good, almost done - Ready to commit as soon as CQs are in and Mars+1 is open
  • JDT for Java 9 - will need a wider discussion with EMO on make it easier to publish the work, e.g. in normal builds

May 6, 2015 - McQ, Dani, Martin, John

  • Dani: Java 9 timing - slight delay
  • Dani: RC1 preps
    • 2-day test pass went fine - 2 severe issues found, will be addressed
    • Request to watch PMC mailing list for API exceptions and defect approvals
  • John: PC Discussion on Release Cycles
    • Multiple releases per year PLUS maintenance streams seems like overkill
    • Consider an approach like Orion that just moves constantly forward
    • Especially for the Platform, being rock solid is most important. Still to attract new contributors we need to allow more frequent "feature updates".
      • A model where both "stable/maintenance" _and_ "features" are contributed to the train might be too much work/overhead.
      • Consider a model like Ubuntu, ... with some release numbers being "stable/LTS base" and others being "in-between feature releases" ?
      • Consider a model like LTS for maintenance fixes / aside mainstream just moving forward ?


April 15, 2015 - Dani, John, McQ, Alex, Martin

  • Dani: Java 1.7 Changes
    • Some bundles have been moved to a 1.7 BREE by new committers, even after API freeze
    • Rule has always been "we move up when there's a reason to move up". We won't move up without reason.
      • Dani: Moving the BREE may even cause API changes, so should only be done when incrementing the minor version (5% risk)
      • Alex: Such updates allow staying current and not get to "rewrite is needed" state (thus needed) but has to happen before M6 (API freeze)
    • Alex suggest not accepting additional changes, but not reverting either (to avoid churn)
  • Dani: Batik 1.6 update

April 8, 2015 - Dani, Martin, Alex, John, McQ

  • Dani: Batik - Platform is good, Train may need to update, perhaps updating one bundle only would suffice. John will follow up.
  • Alex: SWT for GTK 3 News
    • GTK port finally decoupled from X11 - it renders on Wayland now, can switch the renderer to a pure HTML one
    • This opens up opportunities (but depends on hosts that have GTK).



April 1, 2015 - McQ, Alex, Martin, Dani (Regrets: John travelling)

  • Alex: GTK 3.16 seeing issues again - fixed some crashes, but scrolling is still entirely broken
    • SWT uses a number of things that GTK declares as "implementation detail"
  • PMC approval on piggyback CQ's (AC question forwarded by John)

March 18, 2015 - Dani, Alex, Martin, McQ, John

  • John: EclipseCon - Bigger this year due to LocationTech (750 attendees)
    • Mark Reinhold keynote and "after-session" on Java 9
    • Much interest in Orion JS tooling / editor, also on desktop
    • Public face of Eclipse Platform at the conference was much more diverse than in the past (Lars Vogel, Max Anderson, Google ...)
  • Dani: bug 458730 Mars Plan Update
  • Dani: e4 project leadership approved by EMO
  • Dani: Szymon Brandys resigned as Platform/Resources co-lead. Need to +1 on the mailing list

March 11, 2015 - no meeting (EclipseCon)


March 4, 2015 - Dani, McQ, Martin, John

  • Dani: e4 leadership - Dani will volunteer to co-lead
  • Dani: BREEs - documentation about how to pick the EE
    • Recommending the "earliest generally supported JRE that provides the capabilities you need"
    • Would like an URL on the page pointing to the most recent plan (talking to Wayne)
  • John: greatfix contest
    • Dani: Working well - some very small contributions but some also very large (eg Customize Perspective fixes)
  • John: EclipseCon - numbers looking good; join Planning Council Breakfast as delegate for Dani

February 25, 2015 - Dani, Martin McQ

  • No topics

February 18, 2015 - Dani, Alex, Martin

  • Alex: Building Native Launchers
    • Current way of building is kinda unpredictable - even if getting some agreement on versions to use, results are kinda unpredictable
    • Pushing towards Hudson RHEL builders at least at the EF to get more transparency and automation - attempt to mimic the infrastructure at IBM
    • Looking at 3 primary architectures (at the EF) for Linux vs. secondary architectures (non-public builders potentially)
  • Dani: Great initiative, but other (non-EF) builders must not be broken
    • EF doesn't allow any commercial tools (but currently, e.g. Windows launchers are built with MSVS)
  • Alex is willing to spend time to get Linux builds running; but can't help with other architectures
    • Martin: great approach - for Windows, using a cross-compiler on Linux might be interesting (after Linux native works)
  • Alex: This is just phase one - getting rid of the binaries in git repos might be phase 2 (since the checked-in binaries easily cause inconsistencies between Java and Native side)
    • Martin: Checked-in binaries help consumers and contributors who just want to make a Java change
    • Dani: Checked-in binaries are also used for comparing build results for expected vs accidental changes
  • Alex: bug 459399 - Policy for recommended minimum execution environments for bundles
    • Dani: It works today
      • To run Eclipse, Java 8 or Java 9 can be used (minimum BREE has no impact)
      • To modify the source, a new JRE can be used but then the Execution Environment Descriptions need to be installed
    • Policy as discussed in the past: Each project can increase the BREE if there is a real need (such as generifying) and no upstream clients are broken
      • But don't change the BREE without justification -- changing the BREE always has some effect, such as new warnings that would need to be addressed
      • Suggested BREE for new bundles has already been changed by Lars
  • Alex: Even for bundles in "maintenance mode", old BREE causes issues for people who build from source (who have to change compilers etc)
  • No conclusion so far (Alex and Dani disagree)
  • Dani: e4 leadership
    • Mature bits being moved to Eclipse - e4 remaining as an incubator to keep alive for experiments with low entry barrier

February 11, 2015 - Dani, Alex

  • no topics

February 4, 2015 - Dani, Alex, Martin


January 28, 2015 - Dani, Alex, John

  • Dani: Switch Mac OS X 10.9 with 10.10 in Mars target environments
    • No objections
  • Alex: Looking for any Eclipse related activity @Fosdem

January 21, 2015 - Dani, Alex, Martin, McQ

  • Alex: Process for allowing non-committers extended bugzilla privileges (for bug triage)?
    • Dani: Yes a process exists. Send bugzilla username to Dani.
  • Alex: New resource for helping with SWT
  • Dani: Platform/UI co-lead
  • Dani: Solaris: Java 8 will only support 64 bits on both Intel and SPARC --> IBM SWT Team considering to invest in getting patches in for 64-bit Solaris

January 14, 2015 - Dani, Alex, Martin, McQ, John

  • Dani: Update on Platform/UI Leadership: Daniel Rolka left IBM and for now has no time to contribute. He stepped down as co-lead and nominated Lars Vogel
  • Dani: Solaris x86 64-bit support - patches exist, but no machine available. No luck to get one from Oracle or via Eclipse Foundation. We will not support Solaris x86 64-bit unless someone makes a machine available

January 7, 2015 - Dani, Alex, Martin, McQ, John

  • Dani: Platform/UI Leadership
  • John: Git security issue - pick up a patch for Jgit in the packages before SR2? - Mostly an EPP

Archive

Back to the top