development/pmc_call_notes/2011-09-27.html - www.eclipse.org/webtools - Git at Google

 <?xml version="1.0" encoding="ISO-8859-1" ?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
 <html xmlns="http://www.w3.org/1999/xhtml">
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
 <title>WTP PMC Agenda/Minutes for September 27, 2011 Conference
 	Call</title>
 </head>


 <body>
 	<h1>WTP PMC Agenda/Minutes for September 27, 2011 Conference Call</h1>
 	<h2>Call Info </h2>
 	<p>
 		Toll free (in US and Canada): 888-426-6840 <br /> Access code:
 		5019600# <br /> Caller pay alternative number: 215-861-6239<br /> <a
 			href="https://www.teleconference.att.com/servlet/glbAccess?process=1&accessCode=6460142&accessNumber=2158616239">Full
 			list of global access numbers</a><br /> <br /> <a
 			href="http://www.timeanddate.com/worldclock/custom.html?cities=224,207,1440,107
 &amp;month=08
 &amp;day=25
 &amp;year=2011
 &amp;hour=11
 &amp;min=0&amp;sec=0&amp;p1=207">Call
 			Time: 11:00 AM Eastern</a>
 	</p>

 <!--
 	<h2>Attendees</h2>
 	<h3>PMC Members</h3>
 	<ul>
 		<li style="margin: 0em 0.2em 0em 0em; padding: 0.0em;">Chuck
 			Bridgham: Y</li>
 		<li style="margin: 0em 0.2em 0em 0em; padding: 0.0em;">Naci Dai:
 			N</li>
 		<li style="margin: 0em 0.2em 0em 0em; padding: 0.0em;">Raghunathan
 			Srinivasan: Y</li>
 		<li style="margin: 0em 0.2em 0em 0em; padding: 0.0em;">Neil
 			Hauge: Y</li>
 		<li style="margin: 0em 0.2em 0em 0em; padding: 0.0em;">Tim
 			deBoer: N</li>
 		<li style="margin: 0em 0.2em 0em 0em; padding: 0.0em;">Kaloyan
 			Raev: Y</li>
 		<li style="margin: 0em 0.2em 0em 0em; padding: 0.0em;">David
 			Williams: Y</li>
 	</ul>
 -->

 	<h2>Announcements and General Business</h2>

 	<h3>Congrats Kaloyan! </h3>
 	<p>
 		<a href="http://dev.eclipse.org/mhonarc/lists/wtp-dev/msg08232.html">Now get some sleep...</a>
 	</p>

 	<h3>Indigo SR1 delivered - Thanks</h3>

 	<p>
 		<a href="http://www.eclipse.org/downloads/">EPP Downloads for 3.7.1</a>.
 	</p>


 	<h3>3.4 Release planning</h3>

 	<p>
 		<a href="http://www.eclipse.org/projects/project-plan.php?projectid=webtools">Top-level plan</a>
 	</p>
 	<ul>
 		<li>M2: Initial Planning document.</li>
 		<li>M3: Iterate/Review plans</li>
 		<li>M4: Final Plans due</li>
 	</ul>

 	<h3>Discuss API policy and bug 353775</h3>
 	<p>Do we need to define facets as API - what attributes, behavior should be considered API?
 	Possibly similar to plugin extension points where everything considered API.
 	Let's discuss possible changes we can make to our policy documents for clarification</p>

 	<ul>
 		<li><a href="http://wiki.eclipse.org/WTP_API_Policy">WTP API Policy</a></li>
 		<li><a href="http://wiki.eclipse.org/OSGi_API_Guidelines">Eclipse OSGI API Policy</a></li>
 	</ul>

 	<p>We may need to define our policy on API deprecation or altering API behavior in both the current and maintenance releases.

 	<a href="http://wiki.eclipse.org/Eclipse/API_Central/Deprecation_Policy">Eclipse API Deprecation Policy</a></p>
 	<p>After some good discussion, we decided some clarification is needed for WTP's API policy, and Chuck will send an initial draft to
 	the PMC list for further discussion.  Neil pointed out a good statement(describing the "entire" API) from the platform is located
 	<a href="http://wiki.eclipse.org/Eclipse/API_Central/Deprecation_Policy">here</a> summary below:
 	"Note that the API (Application Programming Interface) is the entire public programming surface of the framework,
 	thus it includes not only Java classes, packages, and interfaces, but also extension points, file formats, generated meta-data, and even objects that are passed through to internal packages."</p>

 	<h3>Discussion on Git adoption</h3>
 	<p>Continue polling - re-evaluate by M4
 	- Should we put a stake in the ground mandating when we need to see some progress in educating our committers?
 	- investigate a subproject that could "pilot" a git repo feeding into our overall PDE build
 	- More discussion on CVS - GIT transition - should replace CVS feature for feature
 	- Platform HAS put a stake in the ground....
 	<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=358980"> CVS Retirement bug (Target: December 21, 2012)</a>
 	</p>

 	<h3>Discussion on 4.2 adoption</h3>
 	<p>Many small problems found
 	- subtle changes in behavior - tracking with "wtp4x" in whiteboard.

 	<a href="https://bugs.eclipse.org/bugs/buglist.cgi?status_whiteboard_type=allwordssubstr;query_format=advanced;field0-0-0=assigned_to;status_whiteboard=wtp4x;bug_status=NEW;bug_status=ASSIGNED;bug_status=REOPENED;type0-0-0=nowords;value0-0-0=gercan%40acm.org%2C%20deboer%40ca.ibm.com%2C%20kosta%40bea.com%2C%20rfrost%40bea.com%2C%20lmandel%40ca.ibm.com%2C%20mdelder%40us.ibm.com%2C%20agarwasa%40us.ibm.com%2C%20ryman%40ca.ibm.com%2C%20tbashor%40bea.com%2C%20csalter%40ca.ibm.com%2C%20nitind%40us.ibm.com%2C%20rmah%40ca.ibm.com%2C%20naci.dai%40eteration.com">Tracking query</a>
 	</p>

 	<h3>Dali - Possible mid-stream release</h3>
 	<p>More details to come...
 	</p>

 	<h3>Other Business ... ?</h3>

 	<p>
 		webtool.website Progress from <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=356874">tracking bug</a>
 	</p>

 	<p style="font-style: italic;">Progress moving WTP 3.4 builds "officially" to 4.2 platform as the default.
 		Carl is finished promoting our <a href="http://build.eclipse.org/webtools/committers/wtp4x-R3.4.0-I/20110922230524/S-3.4.0M2-20110922230524/">Juno M2 build</a>, and is 4.2 based.
 		He has also changed the order and frequency of both 3.8 and 4.2 builds.  EMF is fixing the problem with 3.8 based builds shortly after M2 is declared.</p>


 	<h2>Future Agenda items</h2>
 	<!--  <ul style="text-indent: 5em; font-style: italic;"> -->
 	<ul style="font-style: italic;">


 		<li>Discuss our model and assignments of "PMC Roles". Do they
 			still make sense?</li>


 	</ul>
 	<h2>References</h2>
 	<ul>
 		<li><a
 			href="http://wiki.eclipse.org/Team_thoughts_on_continuous_improvement_32">Continuous
 				Improvement Notes</a></li>
 	</ul>


 	<hr />
 	<p>
 		Back to <a href="../index_pmc_call_notes.php">meeting list</a>.
 	</p>
 	<p>Please send any additions or corrections to Chuck Bridgham.</p>
 </body>
 </html>
	<?xml version="1.0" encoding="ISO-8859-1" ?>
	<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
	<html xmlns="http://www.w3.org/1999/xhtml">
	<head>
	<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
	<title>WTP PMC Agenda/Minutes for September 27, 2011 Conference
	Call</title>
	</head>


	<body>
	<h1>WTP PMC Agenda/Minutes for September 27, 2011 Conference Call</h1>
	<h2>Call Info </h2>
	<p>
	Toll free (in US and Canada): 888-426-6840 <br /> Access code:
	5019600# <br /> Caller pay alternative number: 215-861-6239<br /> <a
	href="https://www.teleconference.att.com/servlet/glbAccess?process=1&accessCode=6460142&accessNumber=2158616239">Full
	list of global access numbers</a><br /> <br /> <a
	href="http://www.timeanddate.com/worldclock/custom.html?cities=224,207,1440,107
	&month=08
	&day=25
	&year=2011
	&hour=11
	&min=0&sec=0&p1=207">Call
	Time: 11:00 AM Eastern</a>
	</p>

	<!--
	<h2>Attendees</h2>
	<h3>PMC Members</h3>
	<ul>
	<li style="margin: 0em 0.2em 0em 0em; padding: 0.0em;">Chuck
	Bridgham: Y</li>
	<li style="margin: 0em 0.2em 0em 0em; padding: 0.0em;">Naci Dai:
	N</li>
	<li style="margin: 0em 0.2em 0em 0em; padding: 0.0em;">Raghunathan
	Srinivasan: Y</li>
	<li style="margin: 0em 0.2em 0em 0em; padding: 0.0em;">Neil
	Hauge: Y</li>
	<li style="margin: 0em 0.2em 0em 0em; padding: 0.0em;">Tim
	deBoer: N</li>
	<li style="margin: 0em 0.2em 0em 0em; padding: 0.0em;">Kaloyan
	Raev: Y</li>
	<li style="margin: 0em 0.2em 0em 0em; padding: 0.0em;">David
	Williams: Y</li>
	</ul>
	-->

	<h2>Announcements and General Business</h2>

	<h3>Congrats Kaloyan! </h3>
	<p>
	<a href="http://dev.eclipse.org/mhonarc/lists/wtp-dev/msg08232.html">Now get some sleep...</a>
	</p>

	<h3>Indigo SR1 delivered - Thanks</h3>

	<p>
	<a href="http://www.eclipse.org/downloads/">EPP Downloads for 3.7.1</a>.
	</p>



	<h3>3.4 Release planning</h3>

	<p>
	<a href="http://www.eclipse.org/projects/project-plan.php?projectid=webtools">Top-level plan</a>
	</p>
	<ul>
	<li>M2: Initial Planning document.</li>
	<li>M3: Iterate/Review plans</li>
	<li>M4: Final Plans due</li>
	</ul>

	<h3>Discuss API policy and bug 353775</h3>
	<p>Do we need to define facets as API - what attributes, behavior should be considered API?
	Possibly similar to plugin extension points where everything considered API.
	Let's discuss possible changes we can make to our policy documents for clarification</p>

	<ul>
	<li><a href="http://wiki.eclipse.org/WTP_API_Policy">WTP API Policy</a></li>
	<li><a href="http://wiki.eclipse.org/OSGi_API_Guidelines">Eclipse OSGI API Policy</a></li>
	</ul>

	<p>We may need to define our policy on API deprecation or altering API behavior in both the current and maintenance releases.

	<a href="http://wiki.eclipse.org/Eclipse/API_Central/Deprecation_Policy">Eclipse API Deprecation Policy</a></p>
	<p>After some good discussion, we decided some clarification is needed for WTP's API policy, and Chuck will send an initial draft to
	the PMC list for further discussion. Neil pointed out a good statement(describing the "entire" API) from the platform is located
	<a href="http://wiki.eclipse.org/Eclipse/API_Central/Deprecation_Policy">here</a> summary below:
	"Note that the API (Application Programming Interface) is the entire public programming surface of the framework,
	thus it includes not only Java classes, packages, and interfaces, but also extension points, file formats, generated meta-data, and even objects that are passed through to internal packages."</p>

	<h3>Discussion on Git adoption</h3>
	<p>Continue polling - re-evaluate by M4
	- Should we put a stake in the ground mandating when we need to see some progress in educating our committers?
	- investigate a subproject that could "pilot" a git repo feeding into our overall PDE build
	- More discussion on CVS - GIT transition - should replace CVS feature for feature
	- Platform HAS put a stake in the ground....
	<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=358980"> CVS Retirement bug (Target: December 21, 2012)</a>
	</p>

	<h3>Discussion on 4.2 adoption</h3>
	<p>Many small problems found
	- subtle changes in behavior - tracking with "wtp4x" in whiteboard.

	<a href="https://bugs.eclipse.org/bugs/buglist.cgi?status_whiteboard_type=allwordssubstr;query_format=advanced;field0-0-0=assigned_to;status_whiteboard=wtp4x;bug_status=NEW;bug_status=ASSIGNED;bug_status=REOPENED;type0-0-0=nowords;value0-0-0=gercan%40acm.org%2C%20deboer%40ca.ibm.com%2C%20kosta%40bea.com%2C%20rfrost%40bea.com%2C%20lmandel%40ca.ibm.com%2C%20mdelder%40us.ibm.com%2C%20agarwasa%40us.ibm.com%2C%20ryman%40ca.ibm.com%2C%20tbashor%40bea.com%2C%20csalter%40ca.ibm.com%2C%20nitind%40us.ibm.com%2C%20rmah%40ca.ibm.com%2C%20naci.dai%40eteration.com">Tracking query</a>
	</p>

	<h3>Dali - Possible mid-stream release</h3>
	<p>More details to come...
	</p>

	<h3>Other Business ... ?</h3>

	<p>
	webtool.website Progress from <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=356874">tracking bug</a>
	</p>

	<p style="font-style: italic;">Progress moving WTP 3.4 builds "officially" to 4.2 platform as the default.
	Carl is finished promoting our <a href="http://build.eclipse.org/webtools/committers/wtp4x-R3.4.0-I/20110922230524/S-3.4.0M2-20110922230524/">Juno M2 build</a>, and is 4.2 based.
	He has also changed the order and frequency of both 3.8 and 4.2 builds. EMF is fixing the problem with 3.8 based builds shortly after M2 is declared.</p>


	<h2>Future Agenda items</h2>
	<!-- <ul style="text-indent: 5em; font-style: italic;"> -->
	<ul style="font-style: italic;">


	<li>Discuss our model and assignments of "PMC Roles". Do they
	still make sense?</li>


	</ul>
	<h2>References</h2>
	<ul>
	<li><a
	href="http://wiki.eclipse.org/Team_thoughts_on_continuous_improvement_32">Continuous
	Improvement Notes</a></li>
	</ul>


	<hr />
	<p>
	Back to <a href="../index_pmc_call_notes.php">meeting list</a>.
	</p>
	<p>Please send any additions or corrections to Chuck Bridgham.</p>
	</body>
	</html>