Difference between revisions of "RT/meetings/PMC Minutes 121017"

Latest revision as of 10:58, 17 October 2012

Attendees

• Tom
• Mike
• Glyn
• Ian
• Christian
• Markus

Agenda

• LTS Readiness Criteria for RT ( Glyn's note, LTS Readiness)
  • IP Log requirement?
  • 1.3 you state that most, if not all seem necessary? Actually you call out many that do not apply to RT later
  • What about 1.4.9 APIs

RT Panel

• Who is the moderator?
  • Someone from the foundation (Ian? or Mike?)
  • Ian Bull will take a first crack at the abstract

LTS Readiness

• Virgo did a lot of work to get on Juno release
  • driver for it was to be eligible for LTS
  • it was a lot of effort, is it really necessary for LTS?
  • A large number of the requirements required to participate in the common yearly release do not seem applicable to RT. simultaneous release requirements
• Jesse and Glyn had a meeting with LTS
  • Got an action item to go back to RT-PMC for criteria that do not apply to RT for LTS support Initial note from Glyn to RT-PMC
• Discussed the individual items during the call. The discussion fell into two categories
  • Simultaneous Release Requirements that don't apply to RT
    • State intent early (M4)
    • Compatibility with Previous Releases
    • Support for Eclipse 3.8 workbench
    • Integrate Early and Often
    • Communication
    • Provide optimized p2 repository
    • Branding
    • Do No Harm
    • Support Primary Eclipse Platform
    • Engage Community
    • Usability
    • Performance
    • Capabilities
    • Ramp Down Plan
    • Accessibility
    • APIs
      • The PMC discussed this item a bit. We agree that it has value, but need clarification on some of the musts. For example, the must for having bugzilla entries for each deviation.
      • Ian to take action item to planning council to get some clarification.
    • Retention Policy
      • The PMC discussed this item a bit. If this only applies to policies for p2 repositories then it does not apply to RT for LTS. If it applies to source repositories or repositories of binaries (p2, maven etc) in a reproducible build then it seems like a good idea for RT.
    • Project Metrics
    • Excel in NLS
  • LTS requirements above the Simultaneous Release Requirements
    • What about common builds (CBI)?
      • It is unclear to us if the use of CBI is a requirement for LTS. If so many RT projects have a huge hurtle to jump over to participate in LTS.
    • What about versioning?
      • We have general concerns with establishing a versioning story for things built at LTS and making logical semantic sense out of them.