i'm starting to think about the mechanics of correctly distributing releases and find some topics deserving of discussion
IMO the IPMC needs to think a little about the division of responsibility between podling and IPMC in the final publication stage of release distribution. new releases need to be mirrored. setting up mirroring takes some work but it's once only. the question is how much responsibility we want to devolve to podlings for ensuring that this is done correctly. jakarta uses XSLT to push out news of a release and update mirroring code. with some effort it would be possible to create scripts that automate quite a lot of the mirroring setup and update process for new releases (plus cool stuff like pushing out news and updating the website). this would give a uniform interface and make life much easier for podlings but would be less educational. i wonder about permissions for the distribution directories. podling release managers are less likely to be well connected to the apache web of trust. these signatures could be difficult to verify later. opinions? - robert --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
