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 "E4/Meeting Minutes/Status 20110623"

(Attendees)
 
(5 intermediate revisions by one other user not shown)
Line 7: Line 7:
 
* John
 
* John
 
* Paul
 
* Paul
 +
* McQ
  
 
= Minutes =
 
= Minutes =
Line 22: Line 23:
  
 
* Cyclic dependency on EMF - need to ensure we coordinate with EMF to make sure we align at milestone times.
 
* Cyclic dependency on EMF - need to ensure we coordinate with EMF to make sure we align at milestone times.
 +
 +
* Development cadence
 +
** 4_1_maintenance for bug fixes
 +
** 4.2 stream for major changes
 +
** May be some destabilizing changes in early 4.2 milestones
 +
** If necessary could contribute for 4.1 builds to Juno train at first
 +
 +
* Bug triage
 +
** Move e4 bugs to Platform as needed
 +
** All new bugs go in Platform rather than e4
 +
 +
* Big ticket items
 +
** Capabilities
 +
** Startup sequence
 +
** Reduce memory burn
 +
** Figure out if model delta file approach will work

Latest revision as of 09:35, 24 June 2011

Attendees

  • Eric
  • Andrew
  • Remy
  • Bogdan
  • John
  • Paul
  • McQ

Minutes

  • e4 conversion to git
    • Have to wait for Platform git conversion
    • Will then stitch the e4 bundles into the appropriate Platform git repository
    • Bundles remaining in e4 will move into a general e4
  • Building 4.x
    • Need to switch to long form "full" 3.x builder to build 4.x
    • Nightly builds of 4.x instead of 3.x
    • Need to branch tests that rely on internals
    • We will do this after Git migration - August
  • Cyclic dependency on EMF - need to ensure we coordinate with EMF to make sure we align at milestone times.
  • Development cadence
    • 4_1_maintenance for bug fixes
    • 4.2 stream for major changes
    • May be some destabilizing changes in early 4.2 milestones
    • If necessary could contribute for 4.1 builds to Juno train at first
  • Bug triage
    • Move e4 bugs to Platform as needed
    • All new bugs go in Platform rather than e4
  • Big ticket items
    • Capabilities
    • Startup sequence
    • Reduce memory burn
    • Figure out if model delta file approach will work

Back to the top