[cross-project-issues-dev] Initialization for 2019-06

[Ed Merks <ed.merks@xxxxxxxxx>]

I'm very happy to see that http://download.eclipse.org/releases/2019-06 
already exists.

But of course I'm going to complain and ask for more! :-P

The contents current look like this:

<?xml version='1.0' encoding='UTF-8'?>
<?compositeMetadataRepository version='1.0.0'?>
<repository name='Eclipse Repository' 
type='org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepository' 
version='1.0.0'>
  <properties size='3'>
    <property name='p2.timestamp' value='1313779613121'/>
    <property name='p2.compressed' value='true'/>
    <property name='p2.atomic.composite.loading' value='true'/>
  </properties>
  <children size='1'>
    <child location='../2019-03/201903201000' />
  </children>
</repository>

Note that the EPP repo is absent and that's because 
https://download.eclipse.org/technology/epp/packages/2019-06 doesn't yet 
exist.  But more important note that there is now no EPP repo specified 
anywhere, so this isn't really going to be workable in this state...

What would be really great would be if 
https://download.eclipse.org/technology/epp/packages/2019-06 also 
already existed; it would be a composite that references exactly one 
child via ../2019-03.

Then http://download.eclipse.org/releases/2019-06 would be changed to this:

<?xml version='1.0' encoding='UTF-8'?>
<?compositeMetadataRepository version='1.0.0'?>
<repository name='Eclipse Repository' 
type='org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepository' 
version='1.0.0'>
  <properties size='3'>
    <property name='p2.timestamp' value='1313779613121'/>
    <property name='p2.compressed' value='true'/>
    <property name='p2.atomic.composite.loading' value='true'/>
  </properties>
  <children size='2'>
    <child 
location='http://download.eclipse.org/technology/epp/packages/2019-09' />
    <child location='../2019-03/201903201000' />
  </children>
</repository>

In this state, the two repos would serve up the exactly same contents as 
2019-03 via composition, until that point in time when the first 
milestone is produced for 2019-06 when they would reference the new 
2019-06 repos instead.

This would really help me maintain the Oomph setups better (and to 
prepare the first EMF builds targeting 2019-06).

Of course I'm more than willing to do all the work to prepare these if I 
my account emerks has the necessary permissions on build.eclipse.org.

BTW, special thanks to whomever changed 
http://download.eclipse.org/releases/latest to look like this:

<?xml version='1.0' encoding='UTF-8'?>
<?compositeMetadataRepository version='1.0.0'?>
<repository name='Eclipse Project latest repository' 
type='org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepository' 
version='1'>
  <properties size='3'>
    <property name='p2.timestamp' value='1439691484871'/>
    <property name='p2.compressed' value='true'/>
    <property name='p2.atomic.composite.loading' value='true'/>
  </properties>
  <children size='1'>
    <child location='http://download.eclipse.org/releases/2019-03/'/>
  </children>
</repository>