[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [epp-dev] update of package status - please test
|
Roy:
If it can't be slid into the Galileo update site or a respun EPP
package, it can still be on the PDT update site.
I liken this to the recent Fedora 11 release. A *very* cool new feature
(support for delta rpms) was added *just after* the code freeze, and as
such isn't on the .ISOs for Fedora 11 (the OS equivalent of an EPP
bundle). But it's in the Fedora update repo, so as soon as you install
Fedora, you run an update, install the yum-presto plugin, and voom,
you're away to the races.
So, we just need to tell people in the PDT community that there'll be an
early PDT 2.1.1 (in July?), and a 2.1.2 in September w/ the SR1 train.
People can get the fix off the PDT 2.1 milestone site if they need it
sooner than the 2.1.1 release.
Sure, not *ideal*, but a freeze is a freeze, come what may.
David M Williams wrote:
Sounds ok by me, actually I am not sure we need any feature patch since
an alternative RC5 is released, people who update their software will be
able to get the latest RC5. Or can't they?
I honestly don't now, but not sure how p2 treats a qualifier only change.
If it would see that as a "new version" to install "automatically". If it
was on your update site, they could for sure explicitly select it
and install it. Maybe its just what I'm used to, but I'd recommend a patch
feature, or else it's not exact a "simultaneous release". I'd think it'd
be confusing to have a different Galileo-ish build that's different from
the
Galileo build. And, then there might be trouble when/if people want to
update
to to Galileo SR1. But, again, I am not sure. Just things for you to
consider.
Can you tell me what are the complications in re-generating the whole
process and use it only for the php package? others can stay with build
20090619-0630.
EPP uses the code that's in /releases/staging and there's really no
process
in place to replace or update only part of /releases/staging ... after
all,
it's simultaneous :) One complication ... even if we could re-generate
/staging,
is that others have already broken the build ... I guess renaming sites,
or something.
So, it's complicated, error prone, to re-do.
[And, in case, it's not clear, my request for a possible respin didn't
involve
changes in code, nothing in /staging, just some property files for the
package
specific bundles].
Hope that helps.
_______________________________________________
epp-dev mailing list
epp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epp-dev
--
Nick Boldt :: http://nick.divbyzero.com
Release Engineer :: Eclipse Modeling & Dash Athena
