i'd like this a lot.  Let's make sure to add notes about this in all
relevant docs, so these don't turn stale.

On 8/14/07, Will Glass-Husain <[EMAIL PROTECTED]> wrote:
> Claude,
>
> I've been meaning to add .htaccess files to redirect each high level product
> directory to the latest release.  How does this sound?
>
> e.g.
>
> http://velocity.apache.org/anakia/
>
> would redirect to:
>
> http://velocity.apache.org/anakia/1.0
>
> I think this would be more useful to users than another generic and possibly
> out of date product description.
>
> WILL
>
>
>
> On 8/13/07, Claude Brisson <[EMAIL PROTECTED]> wrote:
> >
> > Hi. I'm in the process of releasing DVSL. No real problem for now except
> > that the JIRA site fell down and that I need to be in the apcvs group on
> > people.apache.org to deploy the jar to maven repositories.
> >
> > The remaining of this mail goes deeper into some details.
> >
> > Done for now:
> >
> > * copied release files to /www/www.apache.org/dist/velocity/dvsl/1.0
> >
> > * deployed DVSL dev site using velocity.zones scripts
> >
> >   note: even after "newgrp velocity", maven was searching
> > for /export/home/velocity/.ssh/id_rsa, so, as the velocity user, I had
> > to:
> >   - "ssh-key -t rsa" in /export/home/velocity/.ssh
> >   - chmod g+rx /export/home/velocity/.ssh
> >   - chmod g+r /export/home/velocity/.ssh/id_rsa
> >   and to copy id_rsa.pub to my authorized hosts file on
> > people.apache.org
> >
> > * created the DVSL release site directory and script
> >
> > Not done yet:
> >
> > * deploy the DVSL release site (just waiting for the JIRA site to come
> > back online, it just went down)
> >
> > * update and deploy the velocity site (xdoc, doap file, news).
> >
> > * deploy the jar to maven repositories. I found the maven command in an
> > email from Henning:
> >
> > mvn -Dfile=dist/velocity-dvsl-1.0.jar \
> >     -Drepository.id=apache.releases \
> >     -DpomFile=pom.xml \
> >     -Durl=
> > scpexe://[EMAIL 
> > PROTECTED]/www/people.apache.org/repo/m2-ibiblio-rsync/repository\
> >     deploy:deploy-file
> >
> > but I don't have enough karma on people.apache.org (apcvs group needed
> > IMO).
> >
> > * other things I may have forgotten?
> >
> >
> > One remark: all the URLs in the current doap_dvsl.rdf file end
> > with /devel/, while others don't...
> >
> >     for instance :
> >
> >       <Project rdf:about="http://velocity.apache.org/anakia/";>
> >         ...
> >         <name>Anakia</name>
> >         <homepage rdf:resource="http://velocity.apache.org/anakia/"; />
> >
> >     both the about and homepage URL point to
> > http://velocity.apache.org/anakia/ whereas this URL points to an empty
> > page. In fact, only http://velocity.apache.org/engine/index.html does
> > contain something. You guessed my question: shoud we put some content in
> > http://velocity.apache.org/anakia, http://velocity.apache.org/texen,
> > http://velocity.apache.org/tools and http://velocity.apache.org/dvsl ?
> > Or should we use /devel/ links in the doap/rdf file when this index is
> > empty?
> >
> > My suggestion: add short descriptions for all subprojects, modeled after
> > engine/index.html, that serve as a subproject home. When this is ready
> > I'd even like to replace the "Development" menu section with a
> > "Subprojects" one, linked to those homes rather than directly to
> > the /devel/ site. Otherwise those new subprojects homes are not
> > accessible from the main index, and adding both "Development" and
> > "Subprojects" menu sections is rather heavy.
> >
> >
> > Claude
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
> --
> Forio Business Simulations
>
> Will Glass-Husain
> [EMAIL PROTECTED]
> www.forio.com
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to