[jbosstools-dev] Slip the release of JBT/JBDS SOA Tooling to a couple weeks after JBT/JBDS Core? (was Re: Adding Plugins to m2e Discovery Mechanism)

[Burr Sutter]

Does anyone know the SOA & BRMS 5.3 beta dates?

Or the next BRMS 5.3 EA drop date?

JBDS Core needs to be out the door by March 13/14 to align with EAP6 and support the marketing push we have for that event.   Can certainly be staggered as "updates" for N weeks after mid-March.

On Feb 22, 2012, at 1:27 PM, Nick Boldt wrote:

> Well, then, if we target the QE cycle for the SOA Tooling site to start "in a week or two", you could have your Beta1 site (including 0.4.0.Final) out by the end of March.
> 
> Does that work? It'd be very much like the Eclipse release train model with +0, +1, +2, +3 tier projects [1], and the accompanying date offsets needed to have everyone align with their upstream bits.
> 
> (Teiid is also a bit behind -- I'd expected that they'd already be testing w/ the SR1-M target platform so when I flipped the switch on them to start building against that, they'd build fine, but they're broken right now. They too are a +3 project to JBT Core's +0.)
> 
> [1] http://wiki.eclipse.org/Indigo/Simultaneous_Release_Plan
> 
> Adding John, Mark, Burr, and Len so they're in the loop on this "staggered release" idea and suggested 2 week offset. I have no idea if that works from their point of view.
> 
> On 02/22/2012 01:19 PM, Rob Cernich wrote:
>> 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.
>> 
>> I'm happy to wait.
>> 
>> ----- Original Message -----
>>> guys we are working on beta1 - that seem to be a fine place and time
>>> to push such a thing aint it ?
>>> 
>>> /max
>>> 
>>> On Feb 22, 2012, at 6:40 PM, Nick Boldt wrote:
>>> 
>>>> So then we take the nightly site, move it a temporary location that
>>>> won't be overwritten by subsequent nightly spins, and tell QE to go
>>>> wail
>>>> on it (Feb 23).
>>>> 
>>>> Then, after QE vets it as being stable enough and safe enough to
>>>> release
>>>> (Mar 12), it gets moved to here:
>>>> 
>>>> http://download.jboss.org/jbosstools/updates/development/indigo/soa-tooling/
>>>> 
>>>> That URL currently contains the M5 bits (which does not yet include
>>>> Switchyard 0.4).
>>>> 
>>>> It will persist there until such time as CR1 is done, and then
>>>> we'll
>>>> replace the site w/ the CR1 bits.
>>>> 
>>>> Isn't that what we do for the JBoss Tools (Core) [1] entry in the
>>>> Eclipse Marketplace today?
>>>> 
>>>> [1] http://marketplace.eclipse.org/node/121986
>>>> 
>>>> N
>>>> 
>>>> On 02/22/2012 10:33 AM, Max Rydahl Andersen wrote:
>>>>> You cant put a nightly build updatesite which changes and can
>>>>> break any minute into the m2e repository used by all users of
>>>>> eclipse.
>>>>> 
>>>>> That's insane - you want a *stable* set of bits up there.
>>>>> 
>>>>> /max
>>>>> 
>>>>> On Feb 22, 2012, at 3:52 PM, Rob Cernich wrote:
>>>>> 
>>>>>>> you got a stable URL for switchyard plugins yet to submit ?
>>>>>>> 
>>>>>>> We need to be careful which we add here :)
>>>>>> 
>>>>>> I don't quite follow.  I was assuming nightly would work (i.e.
>>>>>> http://download.jboss.org/jbosstools/updates/nightly/soa-tooling/trunk/).
>>>>>>  It doesn't appear that a "version" is required on the catalog
>>>>>> entry and the documentation is doesn't specify anything other
>>>>>> than, "It is assumed that contents of provided p2 repository
>>>>>> will not change in the future unless corresponding m2e
>>>>>> marketplace catalog entry is removed or amended," which I
>>>>>> interpret as, some version of the feature and bundle must be
>>>>>> available from the specified repository.
>>>>>> 
>>>>>> Another thing that was unclear was whether or not my m2e
>>>>>> extension needs to be packaged separately from the rest of the
>>>>>> SwitchYard tooling.
>>>>>> 
>>>>>> Rob
>>>>>> _______________________________________________
>>>>>> jbosstools-dev mailing list
>>>>>> jbosstools-dev at lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>>>> 
>>>>>> 
>>>>> 
>>>>> 
>>>>> _______________________________________________
>>>>> jbosstools-dev mailing list
>>>>> jbosstools-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>> 
>>>> --
>>>> Nick Boldt :: JBoss by Red Hat
>>>> Productization Lead :: JBoss Tools&  Dev Studio
>>>> http://nick.divbyzero.com
>>>> _______________________________________________
>>>> jbosstools-dev mailing list
>>>> jbosstools-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>> 
>>>> 
>>> 
>>> 
>>> _______________________________________________
>>> jbosstools-dev mailing list
>>> jbosstools-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>> 
> 
> -- 
> Nick Boldt :: JBoss by Red Hat
> Productization Lead :: JBoss Tools & Dev Studio
> http://nick.divbyzero.com