incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <>
Subject [Incubator Wiki] Update of "ReleaseDistribution" by RobertBurrellDonkin
Date Wed, 24 Oct 2007 21:52:30 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Incubator Wiki" for change notification.

The following page has been changed by RobertBurrellDonkin:

The comment on the change is:
Pulling together ideas about release distribution

New page:
= Release Distribution =


== Preamble ==

Some thoughts about fixing the issue of distributing incubator releases.

This is a draft document. Needs to be discussed on general and agreed with infra. Please feel
free to jump in.

= Existing Releases =

== Status ==

Existing incubator releases are scattered

Need to conduct an audit of locations of existing releases for projects. This probably means
asking projects to fill something in on the wiki.

== To Mirror Or Not To Mirror ==

 * Mirroring reduces bandwidth only when the bandwidth of the archives downloaded exceeds
the bandwidth cost of uploading releases to the mirrors
 * The Incubator contains a large number of podlings. This is likely to cause a major bandwidth
 * It may be worth considering archiving all releases and then mirroring just new ones.

= New Releases =

== Mirroring Strategy ==

New releases should be mirrored. This means deciding the best approach to the download mirroring

 * Ask podlings to create their own scripts and audit them
 * Create central scripts
  * Basic ones
  * Sophisticated XSLT scripts (as pioneered by Jakarta) which also eg. push news. Meta-data?

== Signing Strategy ==

One weakness is that podling release managers rarely have strongly connected signatures. It
is also possible that podlings may end up having no long term future@Apache. All release managers
for a project may become inactive as well as being unconnected. 

 * Does the incubator need to think about IPMC signatures?
 * Do the KEYS need to be maintained in a central location?

== Permissions ==

Set these on a per podling basis?

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message