[jbosstools-dev] Why does update/kepler now point to Alpha2 ?

[Nick Boldt]

Because Alpha2 was an interim state: Kepler M5 w/ newer Jetty 8 (plus 
Atlassian 3.0.7, SWTBot 2.0.5).

Alpha3 is incompatible w/ Alpha2 as it includes Kepler M6, Atlassian 
3.2, and SWTBot 2.1.

N

On 03/23/2013 09:01 AM, Mickael Istria wrote:
> On 03/23/2013 11:37 AM, Max Rydahl Andersen wrote:
>> On Sat, Mar 23, 2013 at 11:31:07AM +0100, Mickael Istria wrote:
>>> On 03/23/2013 05:41 AM, Nick Boldt wrote:
>>>> Alpha2 (M5 + Jetty 8) and Alpha3 (Kepler M6 + Atlassian, etc.) won't be
>>>> linked from there until were release JBT 4.1.0.Alpha2
>>> Why would we need an Alpha3, and why would we release an Alpha2 ?
>>
>> I assume you mean why would we not just release an Alpha2 so the
>> latest TP are available to use for next JBT release which coincidently
>> is named Alpha2 too ?
> Yes, that's what I mean.
> I mainly mean: why do we already have an Alpha3 whereas we still are
> doing snapshots of Alpha2. All TP changes until we release a new
> milestone of JBT should be in the current snapshot (TP
> 4.30.5.Alpha2-SNAPSHOT).
>
> --
> Mickael Istria
> Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
> My blog <http://mickaelistria.wordpress.com> - My Tweets
> <http://twitter.com/mickaelistria>

-- 
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com