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"

m (→‎Meeting Minutes)
(238 intermediate revisions by 8 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 =
−
'''July 25, 2012:'''
+
 
−
* '''CBI Build'''
+
'''February 2, 2016''' - Dani, Alex, Martin, McQ
−
** For SR1, the build can produce what the Release Train needs ... but not all the extra validation
+
* Dani: '''Foundation Hires''' - Dani hopes they'll find someone in Europe to deal with Releng issues
−
** Need to run both builds for now ... until the CBI team's bytecode verifier produces the same output
+
* Dani: '''Neon M5''' went smoothly - M6 will be the API freeze; tomorrow is the last planned RC for Mars.2
−
** CBI team continues to look at the list of diffs and improve their builder
+
* Dani: '''CQ Deadline''' on Feb.12 for Neon
−
** Platform team would be OK dropping the legacy build once the bytecode validator has no diffs
+
* Dani: {{bug|486647}} for changing the strategy when opening files not associated with Eclipse
−
** Platform team can't commit more resources to CBI now (Paul Webster already heavily involved)
+
** With M5, can now use the System Editor (default) or Text Editor - there's a request to always use the text editor
−
* '''Losing Commits on the Orion git repo'''
+
** Dani thinks that for JPG one wants to use the OS
−
** Dozen commits or so  
+
*** Martin agrees, OpenWith and choosing an editor remembers the choice, and one can also remember;
−
** Might be a defect in the Orion git tools, but the server side should prevent that !!!
+
*** We also show the System Icon in Project Explorer, so using the System Editor by default is natural
−
** DenyNonFastForward should have protected ... need an extra layer of protection ?
+
*** Alex set it to "ask via popup" - can be quite noisy, but avoids trouble when KDevelop or something associated itself with Makefiles or so
 +
** Agreement that flexibility is fine - see no case for changing the default
  
 
<hr/>
 
<hr/>
−
'''June 27, 2012:''' - McQ, Dani, Martin, John
+
'''January 26, 2016''' - Dani, McQ, Alex, Martin, Lars
−
* Eclipse Demo Camps - none in Ottawa
+
* Official PMC representation on AC calls - keep McQ listed since he is interested but nominate Dani instead of John
−
* Going to skip the arch calls for all of July - leave the PMC slot in place.
+
* Next round of FEEP coming up - discussed pro and cons
−
* Should keep an eye on the Community feedback for Eclipse 4
+
* Dani: busy week for the team: Mars.2 (4.5.2) RC2 and Neon (4.6) M5 due this Friday - on track
  
 
<hr/>
 
<hr/>
−
'''June 13, 2012:''' - McQ, Dani, Martin, John
+
'''January 19, 2016''' - Dani, Alex, Martin
 +
* Upstaffing PMC - meet next week
 +
* Update Eclipse PMC representation on the AC
 +
** Since only Alex will represent the Eclipse PMC at EclipseCon, should push for not making formal decisions unless there is remote attendance support
 +
* Dani: {{bug|485429}} '''PDE Build''' - looks like a lot of people still use it; OK if moving to a different component, but there's still a dependency:
 +
** Plugin or feature export still needs PDE Build -- Whoever wants to remove it, will need to implement a replacement '''in the Platform'''
 +
** Alex: Platform build currently does double bootstrapping Tycho already ... making this more complex would be a problem
 +
** Introducing other build system into the Platform would be a wrong approach
 +
** Will go ahead with what we have for 4.6
 +
* Alex: As of today's GTK3 build, Eclipse is working fine on Wayland :) thanks to a number of fixes in GTK
 +
** Some GTK developers are now considering Eclipse as part of their regression suite :)
 +
* SWT move to Java 7 was much appreciated; moving forward, how to deal with functional interfaces ?
 +
* Alex would be interested in some styling support in SWT - would simplify some things, at least on GTK
 +
** Could be a very simple API like setStyle(String) - win32 also seems to have some styling support
 +
* Martin: '''Stability of GTK3 on Mars.2 ?'''
 +
** Alex: Many distros do their own hacks, so hard to tell... Mars.2 should be stable on every distro that has a stable GTK3 distro without too many patches
 +
** Can't recommend GTK3 on Ubuntu yet; few things improved lately, but still causes troubles whenever Ubuntu updates their GTK, requires more fixes in SWT; Kubunutu and derivatives might be even worse
 +
*** Good news is that GTK3.16 dropped support for custom theming engines - causes some ugliness but at least it's stable
 +
** Debian or SuSE should be OK;
 +
** Expect Neon GTK3 to be more stable everywhere than GTK2
  
−
* Discussed the ECF rebuild request ({{bug|382206}}). Arguments in favor: it is a safe change, it reverts the situation to where it was in RC3 and earlier. Arguments against summarized in https://bugs.eclipse.org/bugs/show_bug.cgi?id=382206#c20.
+
<hr/>
−
* We will need to tag the release but we can wait until we are officially done (week of June 25th).
+
'''January 12, 2016''' - McQ, Dani, Alex, Martin
 +
* Dani: '''Upstaffing the PMC'''
 +
** Considering "one-time invitation" to get to know candidates better; not so comfortable with a "trial period"
 +
* Dani: '''Remove Kim Moir from Platform Releng''' - ideally talk to Kim before moving forward
 +
* Dani: {{bug|485429}} '''Remove PDE Build from our drops?'''
 +
** Removing PDE Build is one thing - adding a different technology would be wrong, as wrong as adding EGit
 +
** McQ and Dani will reach out inside IBM;
 +
** Patches are still being submitted; middle ground would be remove from the delivery but keep in repo (and deprecate since not adding features)
 +
* Dani: {{bug|485257}} '''Copyright Policy Change''' - waiting on EMO/Legal input
 +
* Alex: '''Updating SWT to Java7'''
 +
* McQ: '''Travel for EclipseCon'''
  
 
<hr/>
 
<hr/>
−
'''June 6, 2012:''' - McQ, Dani, Martin, John, Andrew
+
'''January 5, 2016''' - McQ, Dani
 +
* Dani: '''PMC Membership'''
  
−
* Discussion of how to handle test failures for final build. Most of the remaining failures are infrastructure issues related to our move to Hudson for tests. We will document the failures through bugs, and include a note on the build results page for the final build explaining the failures
+
<hr/>
−
* Discussion of whether we need a 3.9 release. Unanimous conclusion was that we do not see a need for it. Reducing to one stream will greatly reduce our development overhead and encourage consolidation around the single stream.
+
'''December 15, 2015''' - McQ, Dani, Martin, Alex
−
* Discussion of how to handle the disappearance of org.eclipse.equinox.concurrent from our RC3 builds. This was never deliberately included in the platform, but was present due to a greedy optional dependency from ECF. By very close 3/2 decision PMC decided to leave it alone and document the disappearance in porting guide, readme file, release review material, and cross-project list.
+
* No calls until Jan.5
 +
* Looking for a new PMC member
  
 
<hr/>
 
<hr/>
 +
'''December 8, 2015''' - McQ, Alex, John, Dani
 +
* Discussed {{bug|483803}} regarding the BREE for org.eclipse.core.jobs.
 +
** PMC decided to move it back to JavaSE-1.7 but keep databinding on JavaSE-1.8
 +
* Dani: Reminder: {{bug|475185}} Plan Update 1 - Due with Neon M4 next week
  
−
'''May 23, 2012:''' - McQ, Dani, Martin
+
<hr/>
−
* McQ: '''CBI / Tycho builder''': Paul Webster driving Platform efforts (AI Martin notify about {{bug|359719}})
+
'''December 1, 2015''' - McQ, Alex, Martin, Dani
−
* Martin: {{bug|380984}} ant / Orbit respin? - Unclear for now
+
* McQ: The new 5-Dollar Raspberry Pi and Orion (Java server works just fine on the Pi2).
−
* McQ: Finally figured out some long-standing bug eg "Variables view sometimes empty"
+
** Node server is a bit smaller but single-user and no git - nice for developing node apps though
−
** Dani: It's 2 issues: First-time switch to Perspective deferred to 4.2.1, but {{bug|379818}} is finally fixed
+
* Dani: '''Mars.2 Endgame Plan sent'''
−
** The actual underlying defect had been in there for years
+
* Dani: {{bug|475185}} Plan Update 1 - Due with Neon M4 next week
  
 
<hr/>
 
<hr/>
−
'''May 16, 2012:''' - McQ, John, Dani, Martin
+
'''November 25, 2015''' - McQ, Martin, Alex
−
* Dani: '''Version Number''' in branding features gets auto-generated and 3.8 version is now higher than 4.2 (since 3.8 build runs after 3.8)
+
* Alex: '''Bumping SWT to Java8'''
−
** John thinks it's not a big deal
+
** Lars wants to use Lambdas {{bug|481195}}; Markus keller wants static helper methods;
−
* John: '''CBI Patches''' - CBI has lots of patches downstream in their POM's ... RC2 is the last chance getting that in
+
** Stephan Herrmann - University Research for Thread safety through typed annotations
−
** Auto-generating the POM.XML would be nice but that's not how things work today
+
*** 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'''
 +
** 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/>
−
'''May 9, 2012:''' - McQ, John, Dani
+
'''November 18, 2015''' - Alex, John, Dani
−
* John: Classic update can still be enabled via capabilities - should we remove it?
+
* Dani: EclipseCon NA 2016 submission from our team:
−
** Dani: in general "yes", but too late now
+
** https://www.eclipsecon.org/na2016/session/scaling-eclipse-high-dpi-dots-inch-monitors-challenges-and-solutions
−
** McQ: too late, but make sure we do it for Kepler
+
** 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/>
−
'''May 2, 2012:''' - McQ, Dani, Martin, Andrew, John
+
 
−
* John: '''Forking of SWT''' 3.8 and 4.2 are now separate Streams with CTabFolder implementation being the only difference
+
'''November 11, 2015''' - McQ, John, Dani
−
* Dani: '''Icons''' (not discussed)
+
* 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/>
−
'''April 18, 2012:''' - McQ, Dani, Martin, Andrew, John
+
 
−
* Martin: [[E4/Scripting]] initiative
+
'''October 28, 2015''' - McQ, John, Alex, Dani
−
** McQ thinks the E4 Application Model should be exposed as a DOM to scripting .. anything other than utilizing the e4 DOM for hiding a view feels wrong
+
* Dani: Discuss new meeting time that works for Martin
−
*** Martin: Approach is very pragmatic - don't see anybody investing into new Frameworks at this point but converging on what already exists
+
** decided that John will send out a doodle poll
−
*** If this goes towards macro recording, the recorder should utilize the e4 app model
+
* Dani: Discuss our position regarding the removal of committer emeritus ({{bug|480670}})
−
** Signing up on the [https://dev.eclipse.org/mailman/listinfo/eclipse-scripting-dev eclipse-scripting-dev] mailing list will keep people in the loop (expect low volume)
+
** everyone agreed that we would like to keep this for the following reasons:
−
* Dani: '''API Approval Process''' Approval on Bug plus sent to eclipse-pmc list (like last year)
+
*** it is a good way reward those committers who invested lots of their time and made significant contributions to a project
−
* John: '''PDE Committers''' - perception of not being open
+
*** it makes no sense to remove something that currently works and ask projects to maintain this on their website
−
** McQ would like to see a plan item for next year "actively promote more committers from outside"
+
** we have to make sure that the emeritus list doesn't get stale
−
* Martin: [[Asterisk]] - will need a dialin for Dani in Switzerland; '''AI Dani''' forward his dialin to Martin for the time being
+
  
 
<hr/>
 
<hr/>
−
'''April 11, 2012:''' - McQ, Dani, Martin, Andrew, John
+
 
−
* Martin: '''LTS vs Quality/Fixes in Current Stream''' - Like John's reply making the link between the two
+
'''October 21, 2015''' - McQ, Alex, Dani
−
* McQ/John: '''Builds''' - Moving forward
+
* Dani: so far no negative vote in the vote to move platform.text into platform.ui
−
* McQ: '''CBI Builds''' - Platform not going to take any ownership but will be a consumer like others - still shooting for Juno SR1
+
* McQ: Martin can no longer join, McQ would like to move the meeting
−
* Andrew: '''4.2 Builds in Fedora 17''' - Testing now
+
** detailed several alternatives but no fit yet
−
* McQ: '''IBM Ottawa Team moving to new building''' - expect delays during next couple days
+
** decided to continue the discussion in our next meeting
  
 
<hr/>
 
<hr/>
−
'''April 4, 2012:''' - McQ, Dani, Martin, Andrew
+
 
−
* Dani: '''VM Requirements''' - Help no longer works on Java 5, this surprised some people... but Project Plan talks about a Java 6 req now
+
'''October 14, 2015''' - McQ, John, Alex, Dani
−
** Martin suggestion: on the "Required JVM" table in the Project Plan, add a 2nd column with closure of BREE including all pre-reqs (continue having 1st column the BREE of the bundle itself auto-generated)
+
* 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])
−
* Dani: '''Jeff still mentioned as PMC member'''
+
** 3 solutions:
−
** '''AI Dani''' send E-Mail
+
*** make the move
−
* Martin: '''Concern about Platform Quality''' - eg SWT Redraws on 3.7.x - Old-time committers moving away
+
*** make a more radical move to merge everything into 'Platform'
−
** McQ: Platform team's focus will continue being maintenance, and new Platform support ... team's capacity is going down, but SWT is not affected mosted
+
*** leave things as is and let new people join platform.text
−
** Martin: Code contributions are easy, hi-quality triage and review are harder
+
** McQ: merging everything together is not an option. Skills are too different. Resources, Debug and SWT need to be kept separate.
−
** Martin: Re-think the idea of having committers paid by the Foundation and Member Companies paying their share
+
** Dani: fine with the move as long as it does not serve as argument to merge everything into one pot
−
*** Example: Why would Pascal review p2 in his sparetime ... but if he gets paid per bug his experience can be extremely valuable
+
** Alex: committers need to accept the move
−
*** Be more creative on resourcing side
+
** 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
−
** McQ: In favor of putting more structure in place similar to LTS ("hire people for fixes") ... just continue with LTS ?
+
 
−
*** IBM will have a need for fixes for at least another 8 years .. but that's a very self-serving focus
+
* 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").
−
** [[Image:Ok_green.gif]] '''AI Martin''' send E-Mail to Mike to keep the ball rolling
+
** McQ:
−
* Dani: {{bug|375292}} '''Reference to Marketplace in the SDK'''
+
*** this will not be for free. The name is used at many places (code, webpage, Help) and also by companies in their marketing
−
** Martin: "Classic" is a Building Block but "Packages" are for end users
+
*** maybe we just have to accept we made a mistake in the beginning and now live with it
−
** McQ: The purity of the SDK in itself isn't relevant
+
*** 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)
−
*** Martin: Why not just create a new package "Classic" which is at +3 and pulls in egit + marketplace ... the process for building is all in place, may just need a package reviewer
+
** decided to talk about this again in the next call
−
*** [[Image:Ok_green.gif]] '''AI Martin''' mail Markus
+
  
 
<hr/>
 
<hr/>
−
'''March 21, 2012:''' - McQ, Dani, Andrew, Martin
+
 
−
* McQ '''Oracle Java on Mac'''
+
'''October 7, 2015''' - McQ, John, Alex, Dani, Martin
−
* Dani '''denyNonFastForward'''
+
* Dani: '''{{bug|108668}} Default Text Encoding UTF-8 ?'''
−
* McQ '''JDT Team might see some losses'''
+
** 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
−
* Andrew '''Running OpenJDK tests now on ARM''' :)
+
** 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 ? --&gt; Might mean that external tools don't work as expected
 +
** 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
 +
** Martin: Encoding describes content, so should be managed with the content (as a project setting)
 +
*** '''--&gt; 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 --&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/>
−
'''March 14, 2012:''' - McQ, Andrew, Dani, John
+
'''September 30, 2015''' - McQ, John, Alex, Dani
−
* Losing Eclipse project release engineer next week
+
* Dani: will send a note to PMC list asking to approve new Debug leadership (Sarika)
−
* David Williams is stepping in to help with our builds until Juno
+
* Dani: we should finalize our API removal discussion from last week
−
* Most immediate issue is that our build needs elevated privileges to tag, sign, and promote builds
+
** agreed that APIs marked for removal have to be annotated with @noreference, @noextend and @noimplement
−
** kmoir was the only committer with sufficient privileges
+
** agreed that components should be allowed to remove API but they have to provide good reasons
−
** We either need to give another committer sufficient rights, or give build user access it needs
+
** agreed that we won't allow to delete APIs simply because they are deprecated
−
** Could use hooks to ensure build user isn't doing anything other than tagging
+
** agreed that the PMC will decide case by case i.e. there will be no general rule
−
** All agreed the build user approach was the best option. John to open bug against foundation to carry it out
+
** 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/>
−
'''March 7, 2012:''' - McQ, Andrew, Martin, John
+
 
−
* John: '''API Deletions''' {{bug|370248}} - PMC agrees.
+
'''September 23, 2015''' - Dani, John, Alex, Martin
−
* McQ: '''Common Build Infrastructure at the Foundation'''
+
* Dani: '''JDT Core''' - Co-lead going to step up
−
** Shipping Platform Juno bits built by PDE ... but Foundation wants EPP packages built by Tycho; Platform can't support this
+
* Dani: '''API Removal Discussion'''
−
*** Reason might be that 4.2 is planned to be the start of LTS and VLTS .. ok for now if LTS bits are different since not publicly available
+
** Q1: When do we actually delete API? What's the benefit compared to the pain that we cause ?
−
*** Plus, LTS really starts after Juno SR2 ... Platform might be in a better position for Tycho by then
+
*** Example of methods that don't do anything any more or do wrong things -- those should be removed
−
*** In Linux, Fedora also builds by themselves ... but assumption is that people come to Fedora support first
+
*** Example TableTreeViewer : Continue having the API doesn't hurt, there's no significant benefit removing it
−
** Martin, Andrew really concerned about fragmentation and duplication of effort ... eg what if the qualifiers don't match
+
**** Alex: TableTree was completely broken on GTK for 2-3 years ... keeping such components that don't work properly lowers the quality
−
** Should be treated as proof of concept but not publicly available until Juno SR2, in order to avoid fragmentation !
+
**** 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/>
−
'''February 29, 2012:''' - Dani, McQ, John, Martin, Andrew
+
'''September 16, 2015''' - John, Martin
−
* John: Orion team received a box full of '''Black Ducks''' to honour their Black Duck Rookie of the Year award
+
* John: '''API Removal Discussion'''
−
* Dani: '''Gerrit Move'''
+
** No urgency now -- changes have been reverted for now, and scheduled for 2017
−
** John: Important information needs to stay in Bugzilla ... don't pull from outside git exclusively
+
** Updating the major of a bundle knowingly breaks everyone/most adopters
−
* Andrew: '''Platform Defect Contest'''
+
*** In the past, breaking changes have often been small enough to work without increasing the major
−
** McQ concern: Lots of duplicate bugs would take focus away from the team
+
*** One can argue that removing TableTreeViewer is big enough to warrant updating the major
−
** Martin: Could encourage triage as part of the contest, and only count good/new bugs
+
** Versioning packages has not been done in the past due to the huge upcoming maintenance effort when starting to do so
−
** John: Some low-hanging fruit bugs in Platform UI but not necessarily in 4.x ("helpwanted")
+
** "Release Version" is decoupled from "bundle versions" already (and may move to date-based versions eg "2016.1" with rolling updates moving forward
−
** John: Re-introduce the "greatbug" keyword ?
+
** --&gt; will have more discussion next week
−
*** A greatbug is relevant, new, good description that helps understanding/finding the issue; ideally with a patch.
+
−
*** Resolution: '''AI John''' send note to Mike
+
−
* John: '''PDE API Moved'''
+
−
** Some internal, provisional API was migrated to full API in this release
+
−
** Someone from SAP (Dimitar Giormov) Asked adding back the provisional API such that they could support 2 versions of Eclipse with one codebase
+
−
** McQ: Would have helped them 4 years ago .. but at the moment don't have enough people
+
−
*** McQ: Question how pervasive their use of the old API is ... how much Reflection would they need to put int
+
−
*** One resolution could be OK but only if they provide all the patches
+
−
** This kind of duplication is error prone and adds a maintenance burden on the project
+
  
 
<hr/>
 
<hr/>
−
'''February 22, 2012:''' - Dani, McQ, John, Andrew
+
'''September 9, 2015''' - Dani, Alex, Martin, John, McQ
−
* Repeat of PDE build discussion from last week. We decided to nominate John Arthorne as a committer so we at least have someone to accept community patches. We will revisit after Juno and perhaps do a larger restructuring
+
* John: '''Planning Council Updates'''
−
* Communication with eGit: We have written some patches for eGit that have been growing stale. Dani will review the patches, and then send an email to eGit lead asking if there is a particular reason for not accepting them. If there is no problem with the patches we will track down an eGit committer to release them.
+
** 4 planned releases (March, June, September, December -- essentially end of each quarter) with flexible contents
−
* Andrew asked about process for approving CQs:
+
** Mid December rather than end to avoid churn, so this one is a little shorter
−
** Any PMC member can feel free to approve CQs
+
** Only June is "major" - allowing to drop off, or breaking changes; others are "minor"
−
** New versions of existing third party libraries are a no-brainer, typically just +1 right away
+
** 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
−
** For new third party libraries we may need a PMC discussion about why the library is needed, what feature it will live in, etc
+
 
−
** For code contributions just make sure the legal process has been followed and then +1. We generally trust the judgement of the committer who will process the contribution.
+
* 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/>
−
'''February 15, 2012:''' - Dani, McQ, John
+
'''September 2, 2015''' - Dani, Alex, Martin, John
−
* Some discussion of what to do with PDE Build, which lacks committers. PDE as a whole has barely enough committers to be a functioning project, so maybe we should be looking at a larger restructuring after
+
* Dani: '''EclipseDay India''' on Saturday, 200 attendees wanted to join, hat to cut to 150
−
Juno rather than one piece at a time. We lacked quorum to make a decision so we will defer discussion to another week.
+
** 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)
  
 
<hr/>
 
<hr/>
−
'''February 8, 2012:''' - Dani, Martin, Andrew, McQ
+
'''August 19, 2015''' - Alex, Dani
−
* Andrew: Eclipse stand at '''FOSDEM in Brussles'''
+
* nothing to discuss
−
** Lots of people just dropped by to say hi and thanks
+
−
** Mike Milinkovich was showing off Orion; Gunnar and Andrew did others (Web, EclipseRT, C/C++)
+
−
* McQ: '''4.2 Quality''' ... current list of defects looks manageable to tick all off .. any messaging we want to do ?
+
  
 
<hr/>
 
<hr/>
−
'''February 1, 2012:''' - Dani, Martin, John
+
'''August 12, 2015''' - John, Dani
−
* Dani: '''No UA Committers any more''' - move UA under Platform UI such that at least somebody can apply patches
+
* John asked whether we run on Windows 10
−
** AI John check with Wayne ... UA is a subcomponent now, may not even need a move review.
+
** 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: {{bug|343150}} git '''DenyNonFastForward'''
+
** ''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".''
−
** Orion could eventually add tooling to support easy workflows in spite of deny on the repo ... but not in this release
+
* Dani would like to get plan feedback by Friday EOD
−
** Ping on the bug again and proceed
+
−
* John: Decide when to switch 4.2 builds from re-using 3.x binary bundles vs full 4.x builds
+
−
** Today, the 4.x testsuite just tests 4.x specific stuff; things like JDT tests just run against 3.8 today
+
−
** Today, cannot generate Javadocs in 4.x today sine it needs the full source
+
−
** Today, nightlies are running 3.x only (could change to running 4.x nightlies only)
+
−
** Today, 3.x builds run at IBM and 4.x builds run at Eclipse.org
+
−
** Only few test failures left in the 4.x builds --&gt; ready to switch
+
−
** AI: '''Kim''' to send 4.x test results to the mailing list, consider switching right after M5
+
−
** '''Performance Tests:''' Not yet run on 4.x yet - should be able to run on Denis' vserver
+
−
*** IBM is going to lose the physical machines for performance tests in 2 weeks ! (Going to migrate to vserver too!)
+
−
*** Need a new baseline
+
−
** Andrew: at '''FOSSLC''' in Brussels this week, going to represent Eclipse with Mike Milinkovich, Gunnar Wagenknecht and others
+
−
* '''Gerrit''': Platform won't jump in as an early adopter this time, wait for other projects first
+
−
** Not all Platform Unittests can run on Hudson today (need at least some fingerprint tests to get value from Gerrit)
+
  
 
<hr/>
 
<hr/>
−
'''January 25, 2012:''' - McQ, John, Martin, Andrew, Dani
+
'''August 5, 2015''' - McQ, John, Dani, Alex, Martin
−
* McQ: '''Note about 4.2 on Release Train'''
+
* PC meeting later today (planning calendar, calling SR1/2 "Update 1/2" instead
−
* Andrew: '''Eclipse 4.2 for Fedora''' - Feature note written for Eclipse Juno led to some discussion at Eng.Steering Committee, but finally approved
+
** adding another release before Christmas might be a next step - even if Platform contributes identical bits
−
* Dani: Team down by 1 but no impact (Dani is going to take over responsibilities)
+
 
−
* John: '''Build Failures in UA, Update, PDE, p2 yesterday''' after the move to Java 7... nobody watching these, need to find caretakers
+
* Dani: '''[[Eclipse/Mars Retrospective]]'''
−
** UA tests often fail due to a link validity checker, these can be caused by anyone
+
** Move more components to Tycho build? (Would still need Ant to test against final build/bits)
−
** Certificate Validity issue (Jar signing)
+
** 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/>
−
'''January 18, 2012:''' - McQ, John, Martin, Andrew, Dani
+
'''July 15, 22 and 29, 2015''' -- no meeting
−
* McQ: '''4.2 quality''' and next steps
+
−
** More resources found to enable 4.2 as the LTS base - encouraging, although some items still missing
+
−
** Fedora 17 think about shipping 4.2m6 (work ongoing) - that would be a large stack on top of 4.2
+
−
** John: '''Oracle Java 7 as Reference Platform''' now that the most severe issues are fixed (Java 6 EOL is June 2012 !) - that is Oracle, not OpenJDK
+
−
*** Not remove Java 6 for now
+
−
*** Fedora also does all tests on 7
+
  
 
<hr/>
 
<hr/>
−
'''January 11, 2012:''' - McQ, John, Dani, Martin, Andrew
+
'''July 8, 2015''' - McQ, Dani, John, Martin, Alex
−
* McQ: '''State of Presentation API's'''
+
* John: '''Cross-Language Tooling Discussion''' on the eclipse.org-architecture-council and ide-dev mailing lists
−
** Different API's in 4.2 and 3.x -- will need to deprecate API in 3.x
+
* decided to cancel the upcoming July meetings
−
** Christian suggested deleting API that's not implemented in 4.x to get compile errors ... John thinks that binary compatibility is more important
+
−
*** Plugins will be "mostly OK", presentation API is cosmetic anyways
+
−
** McQ: get in touch with clients who use presentation API, telling them what's best to do ... often newer 4.x infrastructure is much better than trying to keep 3.x around forever
+
−
* Andrew: '''Cairo and GTK3'''
+
−
* John: '''4.2 compiling now'''
+
−
* Martin: '''Updated JSch-0.1.44 version''' - how to announce properly
+
−
** AI Martin Announce on eclipse-dev and cross-project
+
−
** Should also put into migrtion notes and README
+
  
 
<hr/>
 
<hr/>
−
'''January 4, 2012:''' - McQ, Dani, Martin, Andrew
+
'''July 1, 2015''' -- no meeting
−
* McQ: Pascal's note about p2 leadership .. not sure who could step in and make a commitment (may see the same fate as UA)
+
 
−
** Tom Watson looking for candidates, but looks like none in McQ's team
+
<hr/>
 +
'''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)
 +
 
 +
<hr/>
 +
'''June 17, 2015''' - Dani, John, Martin, Alex
 +
* John: '''Mars''' Platform in good shape for Mars - EPP respin for Error Reporting
 +
* Dani: '''Crashes with Java 8''' - Potentially will add to the online README
 +
** Happens in the JIT, with latest Oracle Java 8 (with 8 Cores and very specific circumstances)
 +
** 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/>
 +
 
 +
'''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/>
 +
'''June 3, 2015''' - Alex, Dani, Martin, McQ, John
 +
* Dani: '''Mars Endgame'''
 +
* Dani: Please vote for release review
 +
 
 +
<hr/>
 +
'''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).
 +
 
 +
<hr/>
 +
'''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
 +
 
 +
<hr/>
 +
'''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'''
 +
 
 +
<hr/>
 +
'''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).
 +
 
 +
 
 +
<hr/>
 +
'''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)
 +
** Dani sent [https://dev.eclipse.org/mhonarc/lists/eclipse-pmc/msg02332.html our position] to John in order to update the AC
 +
 
 +
<hr/>
 +
'''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
 +
 
 +
<hr/>
 +
 
 +
'''March 11, 2015 - no meeting (EclipseCon)'''
 +
 
 +
<hr/>
 +
 
 +
'''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
 +
 
 +
<hr/>
 +
'''February 25, 2015''' - Dani, Martin McQ
 +
* No topics
 +
 
 +
<hr/>
 +
'''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
 +
 
 +
<hr/>
 +
'''February 11, 2015''' - Dani, Alex
 +
* no topics
 +
 
 +
<hr/>
 +
 
 +
'''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 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:23, 2 February 2016

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

February 2, 2016 - Dani, Alex, Martin, McQ

  • Dani: Foundation Hires - Dani hopes they'll find someone in Europe to deal with Releng issues
  • Dani: Neon M5 went smoothly - M6 will be the API freeze; tomorrow is the last planned RC for Mars.2
  • Dani: CQ Deadline on Feb.12 for Neon
  • Dani: bug 486647 for changing the strategy when opening files not associated with Eclipse
    • With M5, can now use the System Editor (default) or Text Editor - there's a request to always use the text editor
    • Dani thinks that for JPG one wants to use the OS
      • Martin agrees, OpenWith and choosing an editor remembers the choice, and one can also remember;
      • We also show the System Icon in Project Explorer, so using the System Editor by default is natural
      • Alex set it to "ask via popup" - can be quite noisy, but avoids trouble when KDevelop or something associated itself with Makefiles or so
    • Agreement that flexibility is fine - see no case for changing the default

January 26, 2016 - Dani, McQ, Alex, Martin, Lars

  • Official PMC representation on AC calls - keep McQ listed since he is interested but nominate Dani instead of John
  • Next round of FEEP coming up - discussed pro and cons
  • Dani: busy week for the team: Mars.2 (4.5.2) RC2 and Neon (4.6) M5 due this Friday - on track

January 19, 2016 - Dani, Alex, Martin

  • Upstaffing PMC - meet next week
  • Update Eclipse PMC representation on the AC
    • Since only Alex will represent the Eclipse PMC at EclipseCon, should push for not making formal decisions unless there is remote attendance support
  • Dani: bug 485429 PDE Build - looks like a lot of people still use it; OK if moving to a different component, but there's still a dependency:
    • Plugin or feature export still needs PDE Build -- Whoever wants to remove it, will need to implement a replacement in the Platform
    • Alex: Platform build currently does double bootstrapping Tycho already ... making this more complex would be a problem
    • Introducing other build system into the Platform would be a wrong approach
    • Will go ahead with what we have for 4.6
  • Alex: As of today's GTK3 build, Eclipse is working fine on Wayland :) thanks to a number of fixes in GTK
    • Some GTK developers are now considering Eclipse as part of their regression suite :)
  • SWT move to Java 7 was much appreciated; moving forward, how to deal with functional interfaces ?
  • Alex would be interested in some styling support in SWT - would simplify some things, at least on GTK
    • Could be a very simple API like setStyle(String) - win32 also seems to have some styling support
  • Martin: Stability of GTK3 on Mars.2 ?
    • Alex: Many distros do their own hacks, so hard to tell... Mars.2 should be stable on every distro that has a stable GTK3 distro without too many patches
    • Can't recommend GTK3 on Ubuntu yet; few things improved lately, but still causes troubles whenever Ubuntu updates their GTK, requires more fixes in SWT; Kubunutu and derivatives might be even worse
      • Good news is that GTK3.16 dropped support for custom theming engines - causes some ugliness but at least it's stable
    • Debian or SuSE should be OK;
    • Expect Neon GTK3 to be more stable everywhere than GTK2

January 12, 2016 - McQ, Dani, Alex, Martin

  • Dani: Upstaffing the PMC
    • Considering "one-time invitation" to get to know candidates better; not so comfortable with a "trial period"
  • Dani: Remove Kim Moir from Platform Releng - ideally talk to Kim before moving forward
  • Dani: bug 485429 Remove PDE Build from our drops?
    • Removing PDE Build is one thing - adding a different technology would be wrong, as wrong as adding EGit
    • McQ and Dani will reach out inside IBM;
    • Patches are still being submitted; middle ground would be remove from the delivery but keep in repo (and deprecate since not adding features)
  • Dani: bug 485257 Copyright Policy Change - waiting on EMO/Legal input
  • Alex: Updating SWT to Java7
  • McQ: Travel for EclipseCon

January 5, 2016 - McQ, Dani

  • Dani: PMC Membership

December 15, 2015 - McQ, Dani, Martin, Alex

  • No calls until Jan.5
  • Looking for a new PMC member

December 8, 2015 - McQ, Alex, John, Dani

  • Discussed bug 483803 regarding the BREE for org.eclipse.core.jobs.
    • PMC decided to move it back to JavaSE-1.7 but keep databinding on JavaSE-1.8
  • Dani: Reminder: bug 475185 Plan Update 1 - Due with Neon M4 next week

December 1, 2015 - McQ, Alex, Martin, Dani

  • McQ: The new 5-Dollar Raspberry Pi and Orion (Java server works just fine on the Pi2).
    • Node server is a bit smaller but single-user and no git - nice for developing node apps though
  • Dani: Mars.2 Endgame Plan sent
  • Dani: bug 475185 Plan Update 1 - Due with Neon M4 next week

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

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

Back to the top