Siegfried Goeschl <[EMAIL PROTECTED]> writes: >PS: What's a "CfV"?!
Geee.. :-) A "CfV" is a "Call for Vote". CfV's are mandatory for everything that should hit www.apache.org/dist/ at some point. Ok, so this is how it goes/should go: We can develop and work all we want. However, if we decide that a certain version should be "official" or hit the ASF infrastructure, we have the following options: There is the "unofficial turbine maven repository" at http://jakarta.apache.org/turbine/repo/ which has been invented to get around the "upload to ibiblio" headaches a long time ago. This repo works with a delay of two hours as it is mirrored onto the delivery server from minotaur. There is also the official way on how to deal with non-released versions which is to go through http://cvs.apache.org/dist/ (.../jakarta/turbine in our case.) This location is _intended_ to be used for snapshots, nightlies, rc's, alphas, betas and so on. You can find more information about that on http://www.apache.org/dev/release.html For the current 2.3 RC's and META RC's, I've created http://cvs.apache.org/dist/jakarta/turbine/java-repository which we can use as our repo. This has also the advantage that there is no two hour lag to the delivery servers. The official releases go into www.apache.org/dist. This is the location that is picked up by the apache mirror system and distributes the releases all over the world. Due to this fact, it is very important to make sure that a release confirms to the official ASF guidelines. When we want to 'officially' publish releases of components, the core or anything else, we must hold a vote, send this vote to the PMC for approval and then do "official" publishing as described at the various http://www.apache.org/dev/ pages. Important is e.g. that we do checksums and GPG signing. Using maven, you can do most of the stuff using maven dist:deploy if you project has all the small bits and pieces set correctly. You can look at the current 2.3.2-rc to see how to do it. (This whole mail sounds very buerocratic. It shouldn't. The process itself is not at all complicated but it should make sure that we don't distribute anything that we are not allowed to by accident and have to pull releases later). Best regards Henning -- Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH [EMAIL PROTECTED] +49 9131 50 654 0 http://www.intermeta.de/ RedHat Certified Engineer -- Jakarta Turbine Development -- hero for hire Linux, Java, perl, Solaris -- Consulting, Training, Development 4 - 8 - 15 - 16 - 23 - 42 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
