Jump to: navigation, search

Difference between revisions of "Eclipse/Status meetings/Minutes"

(August 08, 2012)
(Discussion)
Line 14: Line 14:
 
: How to fit these two "M-builds" in with other I-builds, N-builds?  
 
: How to fit these two "M-builds" in with other I-builds, N-builds?  
 
:: M builds scheduled for Mondays? 10 AM, 12 AM Eastern, with rebuilds upon request?
 
:: M builds scheduled for Mondays? 10 AM, 12 AM Eastern, with rebuilds upon request?
:: ''Decision was to move to Wednesday's 10, 12; always, instead of Thursday, and then schedule nothing special for RC weeks.''
+
:: ''Decision was to move to Wednesday's 10, 12:00; always, instead of Thursday, and then schedule nothing special for RC weeks. This aligns with the [http://www.eclipse.org/eclipse/development/plans/freeze_plan_4_2_1.php 4.2.1 SR 1 Endgame Plan].''
  
 
* Question was asked about how to "change history" to correct authorship of a commit. Basic answer was that changing history risks messing up others who have that branch checked out, so best to add a new commit explaining the connection to a bug, the other commit hash, and ?fixing? authorship if possible ... but, not sure any of us on call knew all details of how that all works with auto IP log (especially, if desire was to remove an author? ... though, not sure that's legitimate ... maybe if someone just added whitespace formatting or something?). [Its not clear, to me, how "authorship" could ever be "wrong"? Interesting case. ]
 
* Question was asked about how to "change history" to correct authorship of a commit. Basic answer was that changing history risks messing up others who have that branch checked out, so best to add a new commit explaining the connection to a bug, the other commit hash, and ?fixing? authorship if possible ... but, not sure any of us on call knew all details of how that all works with auto IP log (especially, if desire was to remove an author? ... though, not sure that's legitimate ... maybe if someone just added whitespace formatting or something?). [Its not clear, to me, how "authorship" could ever be "wrong"? Interesting case. ]

Revision as of 02:23, 9 August 2012


August 08, 2012

Discussion

  • Should we collect status notes on a wiki?
http://wiki.eclipse.org/Eclipse/Status_meetings
answer was "yes" but suggested a "one page" format so always same page, easier to "watch" for changes.
  • What build schedule would we like for Juno SR1 RC1? Our +0 day is 8/17 (then a week off, then RCs three Friday's in a row).
Assume we'll be doing both 3.8.1 and 4.2.1 "in sync" (Though 4.2.1 is the official Juno SR1 deliverable).
How to fit these two "M-builds" in with other I-builds, N-builds?
M builds scheduled for Mondays? 10 AM, 12 AM Eastern, with rebuilds upon request?
Decision was to move to Wednesday's 10, 12:00; always, instead of Thursday, and then schedule nothing special for RC weeks. This aligns with the 4.2.1 SR 1 Endgame Plan.
  • Question was asked about how to "change history" to correct authorship of a commit. Basic answer was that changing history risks messing up others who have that branch checked out, so best to add a new commit explaining the connection to a bug, the other commit hash, and ?fixing? authorship if possible ... but, not sure any of us on call knew all details of how that all works with auto IP log (especially, if desire was to remove an author? ... though, not sure that's legitimate ... maybe if someone just added whitespace formatting or something?). [Its not clear, to me, how "authorship" could ever be "wrong"? Interesting case. ]

Status

Platform Text (Dani)

working towards Kepler M1 (one day test pass, bug fixing, N&N)
Juno SR1 status: no bug fixes planned so far

Platform Debug (Michael Rennie)

Holidays
Testing 4.3 M1
SR1 - fixed two bugs, no additional fixes planned

Platform Ant (Michael Rennie)

Holidays
Testing 4.3 M1
No fixes planned for SR1

Platform SWT (Silenio)

Holidays
SR1 fixes
Reviewing GTK 3 patches

Platform Releng (davidw)

Sim Release:
Completed migration of repository to git.
Converted and setup aggregation build for Kepler and Juno SR1

JDT Core (Srikanth)

Working towards Kepler M1 (one day test pass, bug fixing, N&N)
Nothing more planned for M1.
Juno SR1 status: Still a few bugs being worked on.

JDT Debug

Holidays
Testing 4.3 M1
SR1 - fixed two bugs, no additional fixes planned

JDT UI & Text (Dani)

working towards Kepler M1 (one day test pass, bug fixing, N&N)
Juno SR1 status: fixed 2 bugs - no further bug fixes planned to fix so far

PDE (Curtis Windatt)

testing for M1
no more fixes planned for SR1