[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
RE: [gmf-dev] This weeks integration build target ...
|
-1 to switch to integration builds as targets for N
builds.
Integration build (well, the "intergration"
term itself :) justifies for me some extra work to do to set it up and make
appropriate changes in the code. "nightly" is a mere wrap-up for the day, and it
seems reasonable to target it same build most of us use as 'target platform' for
development. I'm not sure everyone updates it's target platform each week
(personally I don't do this, and nobody I'm aware of does). In addition, none of
our dependencies (except EMFT) seems to change that rapidly in API part for us
to strive to target latest I builds instead of M.
As an ultimate reason :)), we should benefit
GMF is +2 project, and grasping hot I builds for me sounds somewhat
contradictiuos ;).
With current approach, I builds serve as an
indicator to put some dedicated efforts to deal with issues and justify
installing new target (equal to one used in I build) and cheching against it.
Besides, I build will warn you about possible "end-of-milestone crunch" (simply failing) so it's up to
developer to handle these issues as soon as he could.
As for EMFT, is it possible to target their N
builds in our nightly builds?
Best wishes,
Artem Tikhomirov
I vote for picking up the latest
integration build, this allows us to stay current and avoids end-of-milestone
crunch to adapt to new milestone builds. Also, not having a weekly drop for
EMFT components may prove to be very difficult as we move to EMFT components
as target.
Thanks
-
Fred
_________________________________
Frédéric Plante
Rational
Software, IBM Software Group
"Richard Gronback"
<Richard.Gronback@xxxxxxxxxxx> Sent by: gmf-dev-bounces@xxxxxxxxxxx
01/25/2006 12:09 PM
Please respond
to "GMF Project developer
discussions." |
|
To
| "GMF Project developer
discussions." <gmf-dev@xxxxxxxxxxx>
|
cc
|
|
Subject
| RE: [gmf-dev] This
weeks integration build target ... |
|
Hi Steve,
The current
philosophy on our target configs for continuous and integration builds is to
utilize the most recent stable builds. This is based on the assumption
that developers are using these for their dev environments, so the two are
matched. This makes the most sense to me, and would otherwise require we
update our dev targets weekly, or live with the understanding our dev target
is different than our continuous/nightly builds (not a good idea, imo).
Of course, there may be some issues
that may force an update, but those you list dont seem too critical.
So, lets take a vote!
Thanks,
Rich
From: gmf-dev-bounces@xxxxxxxxxxx
[mailto:gmf-dev-bounces@xxxxxxxxxxx] On Behalf Of Steven
Shaw
Sent: Wednesday, January 25, 2006 8:42 AM
To:
gmf-dev@xxxxxxxxxxx
Subject: [gmf-dev] This weeks integration build
target ...
Hello Rich,
I
was wondering if we could update the nightly build targets to match this weeks
integration build targets? We have a couple of bugzillas that are
blocked until the nightly build targets are updated...
https://bugs.eclipse.org/bugs/show_bug.cgi?id=124715
https://bugs.eclipse.org/bugs/show_bug.cgi?id=125158
Regards,
Steve.
________________________________________
Steven R.
Shaw
Rational Modeling Platform Diagram Layer Lead
Rational Software |
IBM Software Group
770 Palladium Drive, Kanata, ON, Canada, K2V 1C8
tel:
613.591.7979
steveshaw@xxxxxxxxxx _______________________________________________
gmf-dev mailing
list
gmf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/gmf-dev