development/pmc_call_notes/2011-05-10.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 May 10, 2011 Conference Call</title>
 </head>
 <body>
 	<h1>WTP PMC Agenda/Minutes for May 10, 2011 Conference Call</h1>
 	<h2>Call Info</h2>
 	<p>
 		Toll free (in US and Canada): 888-426-6840 <br /> Access code:
 		6460142# <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=05
 &amp;day=10
 &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;">David
 			Williams: 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;">Chuck
 			Bridgham: Y</li>
 	</ul>

 	<h2>Announcements and General Business</h2>

 	<p>
 		Remember to monitor <a
 			href="http://www.eclipse.org/webtools/plans/3.3.0RC/pmc-bug-approval.php">PMC
 			review list for 3.3.0 end game.</a>.
 	</p>
 	<p>
 		Remember to monitor <a
 			href="http://www.eclipse.org/webtools/plans/3.2.4/pmc-bug-approval.php">PMC
 			review list for 3.2.4 end game</a>.
 	</p>

 	<p>
 		Discuss <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=257640">validation
 			bug</a>.
 	</p>
 	<p style="font-style: italic;">We decided to treat as "hotbug", to
 		review during status meetings. I also updated "hot bug description""
 		to make clearer that other Eclipse/WTP projects can, just for extra
 		review.</p>

 	<p>Are we ready to release 3.2.4 on Friday? Need respin? Delay? Not
 		ready to propose or conclude anything ... . but, as a heads-up ... ...</p>
 	<ul>
 		<li>Regression related to EJBs (see <a
 			href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=345006">bug
 				345006</a>).</li>
 		<li>Another bug is being investigated (no bug number yet) where
 			an OOME easily occurs with large JavaScript libraries. Not a
 			regression, exactly, but is a scalability issue that shows up in
 			enterprise contexts. Sill being investigated ... this is just an
 			early heads up.</li>
 	</ul>

 	<p style="font-style: italic;">We will respin for bug 345006. Since
 		this isn't a "simultaneious release", we will reset the "quiet week"
 		and not officially release until 5/20, just to give a chance to
 		confirm the rebuild went ok ... not to fix more bugs. Note: latest
 		info is that JSDT memory issue is not suitable for "quick fix", and
 		not that obvious in "plain" WTP so JSDT team will look at other
 		alternatives, and (probably) fix in the next maintenance release. dw
 		to send note to wtp-dev on Wednesday with (proposed) change to exact
 		maintenance release date and begin formal sign-off.</p>

 	<p>Can we accommodate a 3.2.5 proposed release? First of September?
 		Maybe November? Not ready for concrete proposal ... but should have
 		high level discussion. Can we handle three streams at once? Can we
 		"lighten" weekly testing load, somehow?</p>

 	<p style="font-style: italic;">There were no objections, and
 		general agreement it is better, in the sense of being more open (more
 		transparent) to fix things in a mini-release, rather than in a lot of
 		patch builds. Of course there is the concern about having "3 streams
 		at once" -- we could not do three smoke tests every week, for example.
 		Two alternatives were suggested: a) alternate maintenance testing ...
 		Helios every other week, Indigo maintenance every other week, Juno
 		every week, or b) perhaps agree to a policy that "any team that
 		contributes to a build should smoke test it", still have three
 		"declares" every week (as long as any contributions, any amount of
 		testing) and then have one focused testing period near "ramp down" of
 		any stream or milestone, where everyone tests, just to make sure no
 		inadvertent side effects (such as, just as an example, where a change
 		in XML DOM might effect JPA function). We'd also need to make clear, and agree to policy,
 		that the 3 streams are "cumlative" ... that is, fixes in Helios also
 		need to go in Indigo stream, and also need to go in Juno stream, to
 		maintain parity between streams. It was also mentioned we'd need to be
 		clear on the "message" we send ... that the extra maintenance releases
 		were simply to provide really good quality, on a long term basis to users and adopters that need it,
 		rather then simply expecting all adopters to move up to new release every
 		year. That is, we are not doing it because a stream has bad
 		quality, or anything.</p>
 	<h3>Other Business ... ?</h3>

 	<p style="font-style: italic;"></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 David Williams.</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 May 10, 2011 Conference Call</title>
	</head>
	<body>
	<h1>WTP PMC Agenda/Minutes for May 10, 2011 Conference Call</h1>
	<h2>Call Info</h2>
	<p>
	Toll free (in US and Canada): 888-426-6840 <br /> Access code:
	6460142# <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=05
	&day=10
	&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;">David
	Williams: 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;">Chuck
	Bridgham: Y</li>
	</ul>

	<h2>Announcements and General Business</h2>

	<p>
	Remember to monitor <a
	href="http://www.eclipse.org/webtools/plans/3.3.0RC/pmc-bug-approval.php">PMC
	review list for 3.3.0 end game.</a>.
	</p>
	<p>
	Remember to monitor <a
	href="http://www.eclipse.org/webtools/plans/3.2.4/pmc-bug-approval.php">PMC
	review list for 3.2.4 end game</a>.
	</p>

	<p>
	Discuss <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=257640">validation
	bug</a>.
	</p>
	<p style="font-style: italic;">We decided to treat as "hotbug", to
	review during status meetings. I also updated "hot bug description""
	to make clearer that other Eclipse/WTP projects can, just for extra
	review.</p>

	<p>Are we ready to release 3.2.4 on Friday? Need respin? Delay? Not
	ready to propose or conclude anything ... . but, as a heads-up ... ...</p>
	<ul>
	<li>Regression related to EJBs (see <a
	href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=345006">bug
	345006</a>).</li>
	<li>Another bug is being investigated (no bug number yet) where
	an OOME easily occurs with large JavaScript libraries. Not a
	regression, exactly, but is a scalability issue that shows up in
	enterprise contexts. Sill being investigated ... this is just an
	early heads up.</li>
	</ul>

	<p style="font-style: italic;">We will respin for bug 345006. Since
	this isn't a "simultaneious release", we will reset the "quiet week"
	and not officially release until 5/20, just to give a chance to
	confirm the rebuild went ok ... not to fix more bugs. Note: latest
	info is that JSDT memory issue is not suitable for "quick fix", and
	not that obvious in "plain" WTP so JSDT team will look at other
	alternatives, and (probably) fix in the next maintenance release. dw
	to send note to wtp-dev on Wednesday with (proposed) change to exact
	maintenance release date and begin formal sign-off.</p>

	<p>Can we accommodate a 3.2.5 proposed release? First of September?
	Maybe November? Not ready for concrete proposal ... but should have
	high level discussion. Can we handle three streams at once? Can we
	"lighten" weekly testing load, somehow?</p>

	<p style="font-style: italic;">There were no objections, and
	general agreement it is better, in the sense of being more open (more
	transparent) to fix things in a mini-release, rather than in a lot of
	patch builds. Of course there is the concern about having "3 streams
	at once" -- we could not do three smoke tests every week, for example.
	Two alternatives were suggested: a) alternate maintenance testing ...
	Helios every other week, Indigo maintenance every other week, Juno
	every week, or b) perhaps agree to a policy that "any team that
	contributes to a build should smoke test it", still have three
	"declares" every week (as long as any contributions, any amount of
	testing) and then have one focused testing period near "ramp down" of
	any stream or milestone, where everyone tests, just to make sure no
	inadvertent side effects (such as, just as an example, where a change
	in XML DOM might effect JPA function). We'd also need to make clear, and agree to policy,
	that the 3 streams are "cumlative" ... that is, fixes in Helios also
	need to go in Indigo stream, and also need to go in Juno stream, to
	maintain parity between streams. It was also mentioned we'd need to be
	clear on the "message" we send ... that the extra maintenance releases
	were simply to provide really good quality, on a long term basis to users and adopters that need it,
	rather then simply expecting all adopters to move up to new release every
	year. That is, we are not doing it because a stream has bad
	quality, or anything.</p>
	<h3>Other Business ... ?</h3>

	<p style="font-style: italic;"></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 David Williams.</p>
	</body>
	</html>