[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [epp-dev] EPP 2020-03 M3
|
Jonah,
How is the updates of the p2 repos coordinated?
Currently
/home/data/httpd/download.eclipse.org/releases/2020-03/compositeContent.jar
is like this:
<?xml version='1.0' encoding='UTF-8'?>
<?compositeMetadataRepository version='1.0.0'?>
<repository name='Eclipse Repository'
type='org.eclipse.equinox.internal.p2.artifact.repository.CompositeMetadataRepository'
version='1.0.0'>
<properties size='3'>
<property name='p2.timestamp' value='1313779613118'/>
<property name='p2.compressed' value='true'/>
<property name='p2.atomic.composite.loading'
value='true'/>
</properties>
<children size='4'>
<child
location='../../technology/epp/packages/2020-03/'/>
<child location='202002071000' />
<child location='202001171000' />
</children>
</repository>
Note the wrong size in "<children size='4'>", so this is
clearly being manually maintained...
It appears that
/home/data/httpd/download.eclipse.org/releases/2020-03/compositeContentM3.jar
is ready as a replacement and its content looks correct.
Of course that replacement's timing must be coordinated with the
state change in
/home/data/httpd/download.eclipse.org/technology/epp/packages/2020-03/.
I see M3 as a child so that looks mostly ready.
I can (and do) test the generation of the product catalogs as if
the repos were already updated with an option like this for the
generator:
-staging 2020-03
http://download.eclipse.org/technology/epp/packages/2020-03/M3
http://download.eclipse.org/releases/2020-03/202002281000
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:
https://git.eclipse.org/c/epp/org.eclipse.epp.packages.git/commit/?id=e5905ffa4dd1ac3f66a31fa4d2c455dea5d22f4e
So the question is:
How are the changes to http://download.eclipse.org/technology/epp/packages/2020-03
and http://download.eclipse.org/releases/2020-03
coordinated?
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:
-useComposite 2020-03
Then the generated catalog will directly refer to the child of
http://download.eclipse.org/releases/2020-03/<release-repo>,
avoiding that users hammer the down.eclipse.org server with far
fewer p2 requests for repository metadata.
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:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=548497#c29
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.
or
Jonah
_______________________________________________
epp-dev mailing list
epp-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/epp-dev