Rob Weir wrote: > Every time we release we need to generate quite a few files related to > the release. > > Here's the list I know of: > > 1) The ASC/SHA/MD5 hashes and signature files, one for every released file
We're using scripts for these of course. With the more than 400 packages we're providing everything else would be insane. The checksums should and are created on the machines they are built on to help protect the gigabytes of data as early as possible. > 2) A CWiki page listing all the built files with hyperlinks to hashes, etc. > > https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds#DevelopmentSnapshotBuilds-AOOSnapshot > > This is used when voting on a Release Candidate. Jürgen uses a self written script for that. AFAIK it is not publically available yet. If needed it can be rewritten with a few lines of a script language. > 3) release_matrix.js, used by the download page's logic to decide what > file to recommend based on user's locale: > [...] > 7) The XML files used by the upgrade notification server, one XML file > per release: Don't know about these. It would be stupid to do all of it manually. I suggest the owners of these tasks share their scripts, e.g. in the http://svn.apache.org/repos/asf/openoffice/devtools/scripts/ directory. > How close are we to this? Is any part of this automated already today? The parts I'm aware of are automated. Herbert --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
