To share it better, you can use your directory ~/public_html that is directly accessible via http for everyone.
Gilles 2008/6/19 Nicolas Lalevée <[EMAIL PROTECTED]>: > Le jeudi 19 juin 2008, Scheper, Erik-Berndt a écrit : >> By the way, I noticed that the IVYDE roadmap, >> http://issues.apache.org/jira/browse/IVYDE?report=com.atlassian.jira.plugin >>.system.project:roadmap-panel , does not contain a version for this release. >> >> It would be nice if you could create it, and assign all resolved issues to >> the release. This would help greatly in testing the alpha release. > > good catch. Actually I will rename the 2.0.0 version to 2.0.0.alpha1 > And the issues not fixed I will move them to a new 2.0 version. > >> I have tried to download the files, but cannot find your home dir. >> Can you please post the entire URL? > > these are in my UNIX home directory on people.apache.org, only committers have > access to it. > > (a release to be accepted by the PMC should be more visible to the public ? as > far as I remember the apache guidelines it should not) > > Nicolas > >> >> ________________________________ >> >> Van: Nicolas Lalevée [mailto:[EMAIL PROTECTED] >> Verzonden: wo 18-6-2008 18:42 >> Aan: dev@ant.apache.org >> Onderwerp: [VOTE] Release of Apache IvyDE 2.0.0.alpha1 >> >> >> >> Hi, >> >> I am pleased to announce that I have a version of IvyDE ready to be >> released. You will find the files in my home directory on people.apache.org >> /home/hibou/ivyde-release >> >> About the released files: >> two files are classic release files: >> * apache-ivyde-sources-2.0.0.alpha1.zip: the source distribution. >> it includes every files which is needed to build that distribution >> * org.apache.ivyde.feature-2.0.0.alpha1.zip: the binary distribution. >> it includes the files ready to be deployed into an Eclipse install >> >> Then there are the files deployed into the IvyDE update site. First few >> words on the update site. It will deployed at the URL: >> http://ant.apache.org/ivy/ivyde/updatesite >> Then, the files that will be effectively there, so in www.apache.org: >> * the site.xml: discribe the deployed features >> * the digest.zip: the compress manifest of every features (optimized >> eclipse update site) >> * eclipse-update--xml.cgi and eclipse-update--xml.html: the files that >> defines the apache mirrors for Eclipse. >> And the binary files packaged for the updatesite (the jar and jar.pack.gz) >> will be in the apache dist directory. More precisely the plugins and >> features directories and all of their files will be in >> dist/ant/ivy/ivyde/updatesite/ >> >> One note on the packaging of Ivy as an Eclipse updatable plug-in. Due to >> two bugs in the packaging of Ivy (IVY-828,IVY-802), a repackaging is >> needed. The repackaging I have done can be reproduced with the target >> install-ivy. It is based on the official 2.0.0.beta2 release. >> >> If you want to reproduce the build, just do: >> ant /release dist -DbaseLocation=$YOUR_ECLIPSE_HOME >> >> If you want to test the update site, just get locally the "updatesite" >> directory from the release, and in Eclipse, setup a "local site" that point >> to your local copy of the "updatesite" directory. >> >> About verifying the signatures, you will find mine there: >> http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x7BF8BE8E >> But I am not sure how to update the KEYS file. I have found how to append >> my public key: >> (gpg --list-sigs <your name> && gpg --armor --export <your name>) >> KEYS >> But then should I just re-copy it into /www/www.apache.org/dist/ant/common >> on people.apache.org ? There is no commit or whatever, right ? >> >> Last but not least, your vote: >> +1 : you agree with the release >> +0 : you agree but the next release should contain some fixes >> -1 : you don't agree, there is a blocker issue with the release >> >> so +1 for me (non binding) >> >> Nicolas >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> >> >> Disclaimer: >> >> This message contains information that may be privileged or confidential >> and is the property of Sogeti Nederland B.V. or its Group members. It is >> intended only for the person to whom it is addressed. If you are not the >> intended recipient, you are not authorized to read, print, retain, copy, >> disseminate, distribute, or use this message or any part thereof. If you >> receive this message in error, please notify the sender immediately and >> delete all copies of this message. >> >> >> >> >> Disclaimer: >> This message contains information that may be privileged or confidential >> and is the property of Sogeti Nederland B.V. or its Group members. It is >> intended only for the person to whom it is addressed. If you are not the >> intended recipient, you are not authorized to read, print, retain, copy, >> disseminate, distribute, or use this message or any part thereof. If you >> receive this message in error, please notify the sender immediately and >> delete all copies of this message. > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Gilles Scokart --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
