User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.5.0
I just regenerated the catalog without the redirections that I
use to test it ahead of time. That's working well now, picking up
the latest changes, which I've committed.
So the installers should be able to install M3 based on the
latest catalog within about 20 minutes.
Thanks everyone!
Regards,
Ed
On 28.02.2020 17:48, Markus Knauer
wrote:
I just checked, and the correct content is included in the
compositeContent.jar (and the compositeArtifacts.jar, of
course):
Thanks for asking the question. As you know
this step was initially missed on M2 release
day.
I don't know how the coordination was done
in the past. I assume that Fred @ EF does the
/releases/2020-03/ one and that Markus had
historically done the EPP one. It seems what
is needed here is for one of us to do both.
I assume I don't have access
to /releases/2020-03/ and that Fred does have
access to EPP's p2. Therefore, if,
like /releases/2020-03/ directory I provide a
ready to
go compositeContentM3.jar/compositeArtifactsM3.jar
in the EPP's p2 location then Fred can rename
both at the same time?
Fred, does that work for you?
> A note of caution as well. [...]
At the moment I only have "For the final
release, this composite p2 repository is being
transformed into a flat p2 repository." in the
process doc. I will read through the mentioned
comments and make sure I expand on that.
I can then inspect the changes to the
generated catalogs (and can even test that
they install). In this case the only
significant semantic change is in the JEE
product and that looks correct because I
can see that did indeed change for M3:
In the ideal world, the timing of the
generated catalogs is also coordinated.
This is less essential when there are no
changes to product definitions because the
catalog uses the composites (for the
currently release cycle versions) so will
see new content as soon as there is new
content in the composites. At a later
point in time, I remove this option for
the generator:
A note of caution as well. On
the release day, the http://download.eclipse.org/technology/epp/packages/2020-03
repository transitions from being a
composite to being a simple repository.
This has been a source of significant
grief over the years. See this comment
for the most recent incident during the
most recent release:
Of course we all hope to avoid such an
incident again, but it's particularly
problematic that such incidents occur
precisely when it's most essential that
there not be a problem, i.e., on the
release day when users see the problems.
Thanks so much for stepping up to manage
all this and for transparently documenting
the process!
Regards,
Ed
On 27.02.2020 20:02, Jonah Graham
wrote:
Hi everyone,
Our next milestone build is available
for testing: EPP 2020-03 M3
Can someone on Mac please verify
the Notarization
for Mac is working as expected. I
have added the notarization step
into the build but I want to make
sure it produced the correct
results.