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

[Nick Boldt]

Then we should coordinate the changes better. Your addition of Jetty (to 
Alpha2) happened a week before I started on the move to Kepler M6. Had 
they all happened the same day, then yes, they would have all been part 
of Alpha2.

But because there was a chance someone was using Alpha2 with the new 
Jetty with Kepler M5, I didn't want to break them by suddenly changing 
the underlying baseline.

The last time we had a workflow where contents of the target platform 
could change "at random", to use Max's favourite phrase, Max complained 
every time.

Now, I version them explicitly so that every substantial commit is a new 
version... and ya'll complain about that too.

In the grand scheme of things, wouldn't you rather have snapshots you 
can ignore (Alpha2, than snapshots that no longer exist because they 
were overwritten?

IMHO it's *more confusing* if you're building one day with Alpha2 and it 
works (because Kepler M5) and the next day it stops working (because 
Kepler M6), than if you discover an email saying "want to use Kepler M6? 
Grab the Alpha3 version of the target platform."

N

On 03/25/2013 02:42 AM, Mickael Istria wrote:
>
>> Does it really matter as long as the version goes up?
> It will introduce many "useless" TP versions and confuse us, and the
> rest of the team. I'm in favor in releasing as few TPs as necessary.
>
> --
> 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