RE: [mylar-dev] Dev-builds for Eclipse 3.2

["Mik Kersten" <beatmik@xxxxxxx>]

While the cost of creating a dev build is negligible, creating a 3.2 build
involves a careful merge of HEAD with the 3.2 branch.  There's too much
overhead for me to do this on a weekly basis, which is why I've been doing
it on demand when someone asks.

But now that we're following the 6 week Platform release cycle this is more
of a problem.  As Willian points out the more people use the dev builds the
better, and we also rely on the feedback of 3.2 users since all the
bootstrapped committers have to be on 3.3.  What I propose is:
1) We always put out a 3.2 dev build on the day of the SDK Milestone
release.
2) We consider having another regular 3.2 dev build during the cycle (e.g.
3rd week).

So this Friday we'll do (1).  Regarding (2), I'm curious as to how many of
the people who would download the dev build will move to M5 (a lot did last
year). 

Willian: after M5 goes out it would be good if you could post back on
whether you could move to it or not.

Mik

> -----Original Message-----
> From: mylar-dev-bounces@xxxxxxxxxxx [mailto:mylar-dev-
> bounces@xxxxxxxxxxx] On Behalf Of Willian Mitsuda
> Sent: Tuesday, February 06, 2007 9:43 AM
> To: Mylar developer discussions
> Subject: [mylar-dev] Dev-builds for Eclipse 3.2
> 
> Hi,
> 
> Since Mylar 2.0 will officially support both Eclipse 3.3 and 3.2, is
> it possible to provide dev-builds for 3.2 too?
> 
> Actually I work most of my time on Eclipse 3.2, perhaps I'll start
> experimenting with 3.3 on M5 alternating with 3.2.
> 
> I'd like to help trying Mylar 2.0, but I cannot compromise on using
> 3.3 for now. And I think having dev-builds for 3.2 would guarantee a
> "field testing" for this version.
> _______________________________________________
> mylar-dev mailing list
> mylar-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/mylar-dev