<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 04/08/2013 07:47 AM, Mickael Istria
wrote:<br>
</div>
<blockquote cite="mid:516259EA.1040302@redhat.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<div class="moz-cite-prefix">On 04/07/2013 06:58 PM, Nick Boldt
wrote:<br>
</div>
<blockquote cite="mid:5161A5BB.6000704@redhat.com" type="cite">
<pre wrap="">(Mickael, Max: this step MUST be part of the target
platform release document to avoid unnecessarily broken builds.)
</pre>
</blockquote>
It's already step #1 in the "after the release" part.<br>
</blockquote>
<br>
Also, ideally, we'll release target-platforms a few days before we
branch components/jobs, and update Jenkins job and parent pom as
part of their "SNAPSHOT" cycle to reduce the amount of things to
change after branch is done.<br>
<div class="moz-signature">-- <br>
Mickael Istria<br>
Eclipse developer at <a href="http://www.jboss.org/tools">JBoss,
by Red Hat</a><br>
<a href="http://mickaelistria.wordpress.com">My blog</a> - <a
href="http://twitter.com/mickaelistria">My Tweets</a></div>
</body>
</html>