[cross-project-issues-dev] Clarification of repo requirements for projec

[David M Williams <david_williams@xxxxxxxxxx>]

As everyone knows, we have a
requirement that projects participating in Helios provide optimized p2
repositories to deliver their content.  Due to some innovative advances
in builds (see bug
306300 and its predecessor
bug
305939) it turns out
there's more choices than we imagined in exactly how people could provide
those repositories. 

So, the Planning Council agreed
some clarification was in order. At the 3/21
Planning Council meeting,
it was agreed that, for Helios, a project's repositories must contain original
jars, and pack.gz files (where original jar means the jar produced by the
build, but which has been conditioned for pack200). And, of course, the
metadata describing the content, must be accurate and in compliance with
P2's expectations and APIs. While innovation is welcome, the Simultaneous
Release also needs predictability, and meeting the needs of adopters. So,
a large change like the type of repository provided should be worked though
the whole system so all projects can all be consistent, and in agreement
about what's needed. Maybe next year? 

While sort of a separate issue,
thinking about all this got me thinking about the common repository and
what we do there, so I have also opened a bug to re-discuss the issue on
whether or not we should keep both jars and pack.gz files in the common
repository. See bug
307804. 

Comments and questions are welcome,