<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
On 02/22/2012 01:48 PM, Len DiMaggio wrote:
<blockquote
cite="mid:f03d50e2-afed-4040-808d-76c1dcf55568@zmail14.collab.prod.int.phx2.redhat.com"
type="cite">
<style type="text/css">p { margin: 0; }</style>
<div style="font-family: Times New Roman; font-size: 12pt; color:
rgb(0, 0, 0);">(Added Ken and Anne-Louise to the cc list)<br>
<br>
The current released version of SOA-P is 5.2 - this release is
only supported with JBDS 4.1.1 (4.1.2, I guess actually).<br>
<br>
The first version of SOA-P that will support JBDS 5 is SOA-P 5.3
- and we are several weeks away from a beta-ready build of SOA-P
5.3.<br>
<br>
So - I think that the ~2 week delay for SOA tooling with JBDS
5.0.beta1 is not an issue. <br>
</div>
</blockquote>
<br>
IIUC, this should be fine.<br>
<br>
<blockquote
cite="mid:f03d50e2-afed-4040-808d-76c1dcf55568@zmail14.collab.prod.int.phx2.redhat.com"
type="cite">
<div style="font-family: Times New Roman; font-size: 12pt; color:
rgb(0, 0, 0);"><br>
Ken - would you agree?<br>
<br>
<br>
<br>
-- Len<br>
<br>
<br>
<br>
<br>
<hr id="zwchr">
<blockquote style="border-left: 2px solid rgb(16, 16, 255);
margin-left: 5px; padding-left: 5px; color: rgb(0, 0, 0);
font-weight: normal; font-style: normal; text-decoration:
none; font-family: Helvetica,Arial,sans-serif; font-size:
12pt;"><b>From: </b>"Nick Boldt" <a class="moz-txt-link-rfc2396E" href="mailto:nboldt@redhat.com"><nboldt@redhat.com></a><br>
<b>To: </b>"Rob Cernich" <a class="moz-txt-link-rfc2396E" href="mailto:rcernich@redhat.com"><rcernich@redhat.com></a><br>
<b>Cc: </b>"Max Rydahl Andersen" <a class="moz-txt-link-rfc2396E" href="mailto:manderse@redhat.com"><manderse@redhat.com></a>,
"jbosstools-dev jbosstools-dev"
<a class="moz-txt-link-rfc2396E" href="mailto:jbosstools-dev@lists.jboss.org"><jbosstools-dev@lists.jboss.org></a>, "Len DiMaggio"
<a class="moz-txt-link-rfc2396E" href="mailto:ldimaggi@redhat.com"><ldimaggi@redhat.com></a>, "Mark Yarborough"
<a class="moz-txt-link-rfc2396E" href="mailto:myarboro@redhat.com"><myarboro@redhat.com></a>, "John Graham"
<a class="moz-txt-link-rfc2396E" href="mailto:jgraham@redhat.com"><jgraham@redhat.com></a>, "Burr Sutter"
<a class="moz-txt-link-rfc2396E" href="mailto:bsutter@redhat.com"><bsutter@redhat.com></a><br>
<b>Sent: </b>Wednesday, February 22, 2012 1:27:12 PM<br>
<b>Subject: </b>Slip the release of JBT/JBDS SOA Tooling to a
couple weeks after JBT/JBDS Core? (was Re: [jbosstools-dev]
Adding Plugins to m2e Discovery Mechanism)<br>
<br>
Well, then, if we target the QE cycle for the SOA Tooling site
to start <br>
"in a week or two", you could have your Beta1 site (including
<br>
0.4.0.Final) out by the end of March.<br>
<br>
Does that work? It'd be very much like the Eclipse release
train model <br>
with +0, +1, +2, +3 tier projects [1], and the accompanying
date offsets <br>
needed to have everyone align with their upstream bits.<br>
<br>
(Teiid is also a bit behind -- I'd expected that they'd
already be <br>
testing w/ the SR1-M target platform so when I flipped the
switch on <br>
them to start building against that, they'd build fine, but
they're <br>
broken right now. They too are a +3 project to JBT Core's +0.)<br>
<br>
[1] <a class="moz-txt-link-freetext" href="http://wiki.eclipse.org/Indigo/Simultaneous_Release_Plan">http://wiki.eclipse.org/Indigo/Simultaneous_Release_Plan</a><br>
<br>
Adding John, Mark, Burr, and Len so they're in the loop on
this <br>
"staggered release" idea and suggested 2 week offset. I have
no idea if <br>
that works from their point of view.<br>
<br>
On 02/22/2012 01:19 PM, Rob Cernich wrote:<br>
> I think I'd want one of our "Final" releases to show up
there. That said, 0.4 won't be complete for another week or
two and I don't remember whether or not the m2e extension was
in 0.3.<br>
><br>
> I'm happy to wait.<br>
><br>
> ----- Original Message -----<br>
>> guys we are working on beta1 - that seem to be a fine
place and time<br>
>> to push such a thing aint it ?<br>
>><br>
>> /max<br>
>><br>
>> On Feb 22, 2012, at 6:40 PM, Nick Boldt wrote:<br>
>><br>
>>> So then we take the nightly site, move it a
temporary location that<br>
>>> won't be overwritten by subsequent nightly spins,
and tell QE to go<br>
>>> wail<br>
>>> on it (Feb 23).<br>
>>><br>
>>> Then, after QE vets it as being stable enough and
safe enough to<br>
>>> release<br>
>>> (Mar 12), it gets moved to here:<br>
>>><br>
>>>
<a class="moz-txt-link-freetext" href="http://download.jboss.org/jbosstools/updates/development/indigo/soa-tooling/">http://download.jboss.org/jbosstools/updates/development/indigo/soa-tooling/</a><br>
>>><br>
>>> That URL currently contains the M5 bits (which
does not yet include<br>
>>> Switchyard 0.4).<br>
>>><br>
>>> It will persist there until such time as CR1 is
done, and then<br>
>>> we'll<br>
>>> replace the site w/ the CR1 bits.<br>
>>><br>
>>> Isn't that what we do for the JBoss Tools (Core)
[1] entry in the<br>
>>> Eclipse Marketplace today?<br>
>>><br>
>>> [1] <a class="moz-txt-link-freetext" href="http://marketplace.eclipse.org/node/121986">http://marketplace.eclipse.org/node/121986</a><br>
>>><br>
>>> N<br>
>>><br>
>>> On 02/22/2012 10:33 AM, Max Rydahl Andersen
wrote:<br>
>>>> You cant put a nightly build updatesite which
changes and can<br>
>>>> break any minute into the m2e repository used
by all users of<br>
>>>> eclipse.<br>
>>>><br>
>>>> That's insane - you want a *stable* set of
bits up there.<br>
>>>><br>
>>>> /max<br>
>>>><br>
>>>> On Feb 22, 2012, at 3:52 PM, Rob Cernich
wrote:<br>
>>>><br>
>>>>>> you got a stable URL for switchyard
plugins yet to submit ?<br>
>>>>>><br>
>>>>>> We need to be careful which we add
here :)<br>
>>>>><br>
>>>>> I don't quite follow. I was assuming
nightly would work (i.e.<br>
>>>>>
<a class="moz-txt-link-freetext" href="http://download.jboss.org/jbosstools/updates/nightly/soa-tooling/trunk/">http://download.jboss.org/jbosstools/updates/nightly/soa-tooling/trunk/</a>).<br>
>>>>> It doesn't appear that a "version" is
required on the catalog<br>
>>>>> entry and the documentation is doesn't
specify anything other<br>
>>>>> than, "It is assumed that contents of
provided p2 repository<br>
>>>>> will not change in the future unless
corresponding m2e<br>
>>>>> marketplace catalog entry is removed or
amended," which I<br>
>>>>> interpret as, some version of the feature
and bundle must be<br>
>>>>> available from the specified repository.<br>
>>>>><br>
>>>>> Another thing that was unclear was
whether or not my m2e<br>
>>>>> extension needs to be packaged separately
from the rest of the<br>
>>>>> SwitchYard tooling.<br>
>>>>><br>
>>>>> Rob<br>
>>>>>
_______________________________________________<br>
>>>>> jbosstools-dev mailing list<br>
>>>>> <a class="moz-txt-link-abbreviated" href="mailto:jbosstools-dev@lists.jboss.org">jbosstools-dev@lists.jboss.org</a><br>
>>>>>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/jbosstools-dev">https://lists.jboss.org/mailman/listinfo/jbosstools-dev</a><br>
>>>>><br>
>>>>><br>
>>>><br>
>>>><br>
>>>>
_______________________________________________<br>
>>>> jbosstools-dev mailing list<br>
>>>> <a class="moz-txt-link-abbreviated" href="mailto:jbosstools-dev@lists.jboss.org">jbosstools-dev@lists.jboss.org</a><br>
>>>>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/jbosstools-dev">https://lists.jboss.org/mailman/listinfo/jbosstools-dev</a><br>
>>><br>
>>> --<br>
>>> Nick Boldt :: JBoss by Red Hat<br>
>>> Productization Lead :: JBoss Tools& Dev
Studio<br>
>>> <a class="moz-txt-link-freetext" href="http://nick.divbyzero.com">http://nick.divbyzero.com</a><br>
>>> _______________________________________________<br>
>>> jbosstools-dev mailing list<br>
>>> <a class="moz-txt-link-abbreviated" href="mailto:jbosstools-dev@lists.jboss.org">jbosstools-dev@lists.jboss.org</a><br>
>>>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/jbosstools-dev">https://lists.jboss.org/mailman/listinfo/jbosstools-dev</a><br>
>>><br>
>>><br>
>><br>
>><br>
>> _______________________________________________<br>
>> jbosstools-dev mailing list<br>
>> <a class="moz-txt-link-abbreviated" href="mailto:jbosstools-dev@lists.jboss.org">jbosstools-dev@lists.jboss.org</a><br>
>>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/jbosstools-dev">https://lists.jboss.org/mailman/listinfo/jbosstools-dev</a><br>
>><br>
<br>
-- <br>
Nick Boldt :: JBoss by Red Hat<br>
Productization Lead :: JBoss Tools & Dev Studio<br>
<a class="moz-txt-link-freetext" href="http://nick.divbyzero.com">http://nick.divbyzero.com</a><br>
</blockquote>
<br>
<br>
<br>
-- <br>
<div><span name="x"></span><br>
Len DiMaggio (<a class="moz-txt-link-abbreviated" href="mailto:ldimaggi@redhat.com">ldimaggi@redhat.com</a>)<br>
JBoss by Red Hat<br>
314 Littleton Road<br>
Westford, MA 01886 USA<br>
tel: 978.392.3179<br>
cell: 781.472.9912<br>
<a class="moz-txt-link-freetext" href="http://www.redhat.com">http://www.redhat.com</a><br>
<a class="moz-txt-link-freetext" href="http://community.jboss.org/people/ldimaggio">http://community.jboss.org/people/ldimaggio</a><br>
<br>
<a moz-do-not-send="true" href="http://www.redhat.com"><img
doc="Briefcase/RHxJBpngthumb.png"
src="cid:part1.07090207.06030608@redhat.com"
style="border: 0pt none;"></a><br>
<span name="x"></span><br>
</div>
</div>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
Ken Johnson
Director, Product Management
JBoss by Red Hat
978.392.3917
<a class="moz-txt-link-abbreviated" href="mailto:ken.johnson@redhat.com">ken.johnson@redhat.com</a>
</pre>
</body>
</html>