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/Status meetings/Minutes"

(Discussion)
Line 1: Line 1:
 
__notoc__
 
__notoc__
 +
<!-- Hints:
 +
* Copy the empty template for the next week from the very end of this edit box.
 +
* Use templates to refer to {{bug|455135}} or {{bug|455135|5}} (2nd argument is the comment #)
 +
-->
  
== August 15, 2012 ==  
+
== January 18, 2017 ==
  
=== Discussion ===
+
=== Discussion/Reminders ===
 +
* M5 is next week. Please clean up your bugzilla backlog.
 +
* We will have a '''call on Wednesday, January 25'''.
  
* (Markus) Auto-tagging from master is problematic in the milestone week
+
== January 4, 2017 ==
** No possibility for a controlled rebuild
+
** Not all committers seem to follow (or know about) the Eclipse process (lockdown rules; changes on or after test day need to be reviewed)
+
** Team leads should decide and stick to one of two working modes:
+
*** Either work with integration and master branches, and only push integration in a controlled fashion
+
*** Or work with master only, but make sure all committers follow the rules and do not commit ongoing work to master in milestone weeks after the last scheduled test build and until the milestone is released<br>
+
  
=== Status ===
+
As decided last year, we will only have an Eclipse Project status call on demand, e.g. before and during a milestone week. The request for a call must be placed on this wiki page before Wednesday, and if so, a reminder will be sent to eclipse-dev.
  
  
== August 08, 2012 ==
 
  
=== Discussion ===
+
== Archived Minutes ==  
  
* Should we collect status notes on a wiki?
+
* [[Eclipse/Status_meetings/Minutes_2016|2016]]
: http://wiki.eclipse.org/Eclipse/Status_meetings
+
* [[Eclipse/Status_meetings/Minutes_2015|2015]]
: ''answer was "yes" but suggested a "one page" format so always same page, easier to "watch" for changes.''
+
* [[Eclipse/Status_meetings/Minutes_2014|2014]]
 +
* [[Eclipse/Status_meetings/Minutes_2013|2013]]
 +
* [[Eclipse/Status_meetings/Minutes_2012|2012]]
  
* 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).
+
[[Category:Eclipse_Platform_Status_Meetings| ]][[Category:Eclipse]]
: 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 [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. ]
 
  
=== Status ===
+
<!-- Template for next week's status (add 7 days, then copy):
 +
== January 4, 2017 ==
  
<!-- ==== Platform Workspace ==== -->
+
=== Discussion/Reminders ===
  
<!-- ==== Platform User Assistance ==== -->
+
=== Status ===
 
+
==== Platform Resources (Sergey) ====
<!-- ==== Platform UI ==== -->             
+
==== Platform UI (Lars or Dani) ====
 
+
==== Platform Debug (Sarika) ====
==== Platform Text (Dani) ====            
+
==== Platform Ant (Sarika) ====
: working towards Kepler M1 (one day test pass, bug fixing, N&N)
+
==== Platform SWT (Arun) ====
: Juno SR1 status: no bug fixes planned so far
+
==== Platform Releng (Sravan) ====
<!-- ==== Platform Search ==== -->
+
==== JDT Core (Jay) ====
 
+
==== JDT Debug (Sarika) ====
==== Platform Debug (Michael Rennie) ====
+
==== JDT UI (Noopur or Markus) ====
: Holidays
+
==== PDE (Vikas) ====
: Testing 4.3 M1
+
==== Equinox (Tom Watson) ====
: 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
+
 
+
<!-- ==== Equinox (Tom Watson) ==== -->   
+
<!-- ==== Equinox p2 (Ian Bull) ==== -->
+
 
+
 
+
 
+
 
+
 
+
[[Category:Eclipse_Platform_Status_Meetings| ]]
+

Revision as of 05:21, 19 January 2017


January 18, 2017

Discussion/Reminders

  • M5 is next week. Please clean up your bugzilla backlog.
  • We will have a call on Wednesday, January 25.

January 4, 2017

As decided last year, we will only have an Eclipse Project status call on demand, e.g. before and during a milestone week. The request for a call must be placed on this wiki page before Wednesday, and if so, a reminder will be sent to eclipse-dev.


Archived Minutes

Back to the top