Thanks for your reply. I'll remove the stuff from the download site and try to figure out how to replace it with snapshot builds that indicate that it is no official release. Please apologies the trouble I've caused.
Daniel > -----Urspr�ngliche Nachricht----- > Von: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > Im Auftrag von robert burrell donkin > Gesendet: Sonntag, 20. Februar 2005 14:21 > An: Jakarta Commons Developers List > Betreff: Re: AW: [ANN] Commons I18n 0.5 released > > On Sun, 2005-02-20 at 11:16, Daniel Florey wrote: > > Hi folks, > > Sorry for the confusion. I just wanted to make the current version of > the > > component available to people interested in this component. > > It's no official release yet and as such there has been no voting > thread. > > The mail to the developers list was created by maven as I tried to > complete > > the maven based build environment to allow distros and releases to be > done > > easily later on. > > I'll try to avoid sending any "announcements" to the list in future if > this > > is considered harmful. So: Sorry again for that one. > > it's not the announcement that's considered harmful: it's the act. > > posting something that seems to be an official ASF release without it > actually being an official ASF release is not acceptable. > > getting releases right is very, very important. the board expects the > jakarta project to provide particular oversight when it comes to > release. the jakarta pmc has entrusted the commons subproject with > particular supervision of the sandbox. if the board cannot trust us to > ensure all release related matters are dealt with correctly, then we > soon won't have a project at all... > > > I'm currently working on completing this tiny component (javadocs, > tests, > > documentation) in order to be able to prepare an "official" release. > > part of process of promotion from sandbox to proper (so that an official > ASF release can be prepare) is an educational one. to some extent, we > trust that ASF committers should already be aware of the importance of > process when it comes to releases and should know when to ask. > > so, questions are good :) > > when asked, we always say: releases are not possible from the sandbox. > making development and test builds available to those who are not able > to build from source is a different matter but it's very important to > recognise the difference between these and official ASF releases. > > > There are some questions left: > > - What is the correct place to put unofficial sandbox-releases for > download? > > Or is it needed for anyone interested to check out the sources and build > a > > jar themselves? > > there can be no such thing as sandbox releases: no releases are > possible. (all ASF releases require approve and due process.) > > making spot, developing and test builds available is a different matter. > i'd like to be able to point you at a suitable document detailing the > usual conventions but i think it needs moving from the old wiki to the > foundation site. (i'll try to take a look into this later.) > cvs.apache.org is the right place, i think. (but i'll need to look into > this.) > > often they are designated with a date stamp (rather than a version > number) so avoid confusion. for example: > > commons-i18-20050220.tar.gz > > > - I still can not find any maven documentation on how to use the dist- > plugin > > in a useful way. Is there any commons project around using maven in a > proper > > way to generate releases/distros and generate an appropriate download > page? > > If you have a look at i18n you'll see that the download link points to > one > > of the distributions .zip file. I would like to point to the distro > > directory as such. > > i think that work is being done on creating a maven-friendly version of > the commons release instructions. i'm not sure what stage it's > reached... > > > - What are the steps that need to be done to move a component (once it > is > > completed and considered useful) to commons-proper? > > a vote by the commons (proper) committers. > > - robert > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
