You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@uima.apache.org by sc...@apache.org on 2008/05/05 15:56:58 UTC
svn commit: r653483 -
/incubator/uima/site/trunk/uima-website/xdocs/release.xml
Author: schor
Date: Mon May 5 06:56:57 2008
New Revision: 653483
URL: http://svn.apache.org/viewvc?rev=653483&view=rev
Log:
no Jira - add a bit more info to the how-to release docs, on how to upload to the mirroring system. Still have the eclipse update site to do
Modified:
incubator/uima/site/trunk/uima-website/xdocs/release.xml
Modified: incubator/uima/site/trunk/uima-website/xdocs/release.xml
URL: http://svn.apache.org/viewvc/incubator/uima/site/trunk/uima-website/xdocs/release.xml?rev=653483&r1=653482&r2=653483&view=diff
==============================================================================
--- incubator/uima/site/trunk/uima-website/xdocs/release.xml (original)
+++ incubator/uima/site/trunk/uima-website/xdocs/release.xml Mon May 5 06:56:57 2008
@@ -161,9 +161,10 @@
After the release is approved, we will have the last tagged release candidate which will correspond to the
official release. This should not be updated after this.
<ul>
- <li><TODO> Upload the release artifacts to the distribution server (via uploading to people.apache.org
+ <li>Upload the release artifacts to the distribution server (via uploading to people.apache.org
in the directory: <code>/www/www.apache.org/dist/uima</code>, including the
- release artifacts and the Eclipse update site data.
+ release artifacts and the Eclipse update site data. Be sure to include the gpg/md5/sha1 signatures.
+ Make sure the KEYS file in that uploaded directory is current.
<ul>
<li>The Eclipse update site on w.a.o/dist/uima will have previous versions of the jars for the
features and plugins. The generated site in
@@ -174,7 +175,10 @@
</ul>
</li>
- <li><TODO> Update the documentation page with the new data on the UIMA website</li>
+ <li>Update the documentation page with the new data on the UIMA website. The mirroring stuff is
+ embedded in the markup - just substitute within that markup the name of the new release
+ (assuming you followed the previous release's nameing conventions for the higher-level
+ directories).</li>
<li>Upload the release artifacts to the Maven Incubator repository. To start the upload the
following command must be executed from the uimaj project <br /><br/>
<code>mvn -DsignArtifacts=true process-resources source:jar deploy</code><br/><br/>
Re: svn commit: r653483 - /incubator/uima/site/trunk/uima-website/xdocs/release.xml
Posted by Marshall Schor <ms...@schor.com>.
Michael Baessler wrote:
> Hi Marshall,
>
> I read your changes and have some additional questions.
>
> I think you mean "/www/www.apache.org/dist/incubator/uima" instead of "/www/www.apache.org/dist/uima".
>
Right :-) until we graduate...
> Do I just have to create new subdirectories for the new release and upload the artifacts as
> described?
Yes. Be sure your new directories have the right permissions and group
names. (see what the old ones had)
> Are there any additional changes necessary that the download page shows the latest
> release?
Yes.
> When I remember correctly the archiving of the previous releases is done automatically, right?
>
Archiving is unusual. When a release is uploaded to the dist/ spot, it
is automatically copied to the archive spot, too. So, when we feel
people don't need "mirrored" access to a particular release any more,
just delete it from the dist/ and add a line to the .htaccess file which
does a re-direct. Please see another dist/ project for how these
.htaccess files are set up. There is one there for fixing the problem
with the eclipse update site - please leave that part alone - I plan to
update that when I upload the new eclipse update site, anyway, because
that redirect only works on some of the mirrors, apparently.
> What do we have to do to make the annotator package available for download?
I suggest a new subdirectory for this, since it had a separate release
vote, and in the future may be on a different release cycle.
> Can I just add the
> additional artifacts?
>
In addition, the download page needs to be updated to reflect the new
things to download. I can't remember if I posted this idea to the list,
but I thought about re-formatting the download page into a table that
more concisely listed what's downloadable - one row per item.
--Marshall
Re: svn commit: r653483 - /incubator/uima/site/trunk/uima-website/xdocs/release.xml
Posted by Marshall Schor <ms...@schor.com>.
Michael Baessler wrote:
> When checking again the download.xml file for our website I currently see the following:
>
> <li><a
> href="[preferred]/incubator/uima/binaries/uimaj-2.2.1-incubating/uimaj-2.2.1-incubating-bin.zip">uimaj-2.2.1-incubating-bin.zip</a>
> [<a
> href="http://www.apache.org/dist/incubator/uima/binaries/uimaj-2.2.1-incubating/uimaj-2.2.1-incubating-bin.zip.asc">asc</a>]
> [<a
> href="http://www.apache.org/dist/incubator/uima/binaries/uimaj-2.2.1-incubating/uimaj-2.2.1-incubating-bin.zip.md5">md5</a>]
>
> Does this mean that [preferred] handles the selected mirror and I have to take care about the
> correct path behind.
Right.
> The checksum and signature files are always downloaded from the same source and
> does not use the mirroring system, right?
>
Right - it's supposed to always download from www.apache.org/dist/...
> So the open questions are
> - Do I have to do anything for archiving the 2.2.1 release?
>
I suggest not doing anything now. Leave it in the mirroring system.
Lots of projects keep the last ~5 releases there.
> - Do I have to consider anything when uploading the annotator package release artifacts?
>
Make sure the file permissions and group setting are consistent with
other directories.
-Marshall
Re: svn commit: r653483 - /incubator/uima/site/trunk/uima-website/xdocs/release.xml
Posted by Marshall Schor <ms...@schor.com>.
One other thing:
Make sure all jars / zips etc. are "signed" and the signatures /
checksums are uploaded as well.
-Marshall
Re: svn commit: r653483 - /incubator/uima/site/trunk/uima-website/xdocs/release.xml
Posted by Michael Baessler <mb...@michael-baessler.de>.
When checking again the download.xml file for our website I currently see the following:
<li><a
href="[preferred]/incubator/uima/binaries/uimaj-2.2.1-incubating/uimaj-2.2.1-incubating-bin.zip">uimaj-2.2.1-incubating-bin.zip</a>
[<a
href="http://www.apache.org/dist/incubator/uima/binaries/uimaj-2.2.1-incubating/uimaj-2.2.1-incubating-bin.zip.asc">asc</a>]
[<a
href="http://www.apache.org/dist/incubator/uima/binaries/uimaj-2.2.1-incubating/uimaj-2.2.1-incubating-bin.zip.md5">md5</a>]
Does this mean that [preferred] handles the selected mirror and I have to take care about the
correct path behind. The checksum and signature files are always downloaded from the same source and
does not use the mirroring system, right?
So the open questions are
- Do I have to do anything for archiving the 2.2.1 release?
- Do I have to consider anything when uploading the annotator package release artifacts?
-- Michael
Michael Baessler wrote:
> Hi Marshall,
>
> I read your changes and have some additional questions.
>
> I think you mean "/www/www.apache.org/dist/incubator/uima" instead of "/www/www.apache.org/dist/uima".
>
> Do I just have to create new subdirectories for the new release and upload the artifacts as
> described? Are there any additional changes necessary that the download page shows the latest
> release? When I remember correctly the archiving of the previous releases is done automatically, right?
>
> What do we have to do to make the annotator package available for download? Can I just add the
> additional artifacts?
>
> -- Michael
>
> schor@apache.org wrote:
>> Author: schor
>> Date: Mon May 5 06:56:57 2008
>> New Revision: 653483
>>
>> URL: http://svn.apache.org/viewvc?rev=653483&view=rev
>> Log:
>> no Jira - add a bit more info to the how-to release docs, on how to upload to the mirroring system. Still have the eclipse update site to do
>>
>> Modified:
>> incubator/uima/site/trunk/uima-website/xdocs/release.xml
>>
>> Modified: incubator/uima/site/trunk/uima-website/xdocs/release.xml
>> URL: http://svn.apache.org/viewvc/incubator/uima/site/trunk/uima-website/xdocs/release.xml?rev=653483&r1=653482&r2=653483&view=diff
>> ==============================================================================
>> --- incubator/uima/site/trunk/uima-website/xdocs/release.xml (original)
>> +++ incubator/uima/site/trunk/uima-website/xdocs/release.xml Mon May 5 06:56:57 2008
>> @@ -161,9 +161,10 @@
>> After the release is approved, we will have the last tagged release candidate which will correspond to the
>> official release. This should not be updated after this.
>> <ul>
>> - <li><TODO> Upload the release artifacts to the distribution server (via uploading to people.apache.org
>> + <li>Upload the release artifacts to the distribution server (via uploading to people.apache.org
>> in the directory: <code>/www/www.apache.org/dist/uima</code>, including the
>> - release artifacts and the Eclipse update site data.
>> + release artifacts and the Eclipse update site data. Be sure to include the gpg/md5/sha1 signatures.
>> + Make sure the KEYS file in that uploaded directory is current.
>> <ul>
>> <li>The Eclipse update site on w.a.o/dist/uima will have previous versions of the jars for the
>> features and plugins. The generated site in
>> @@ -174,7 +175,10 @@
>> </ul>
>> </li>
>>
>> - <li><TODO> Update the documentation page with the new data on the UIMA website</li>
>> + <li>Update the documentation page with the new data on the UIMA website. The mirroring stuff is
>> + embedded in the markup - just substitute within that markup the name of the new release
>> + (assuming you followed the previous release's nameing conventions for the higher-level
>> + directories).</li>
>> <li>Upload the release artifacts to the Maven Incubator repository. To start the upload the
>> following command must be executed from the uimaj project <br /><br/>
>> <code>mvn -DsignArtifacts=true process-resources source:jar deploy</code><br/><br/>
>>
>>
>
Re: svn commit: r653483 - /incubator/uima/site/trunk/uima-website/xdocs/release.xml
Posted by Michael Baessler <mb...@michael-baessler.de>.
Hi Marshall,
I read your changes and have some additional questions.
I think you mean "/www/www.apache.org/dist/incubator/uima" instead of "/www/www.apache.org/dist/uima".
Do I just have to create new subdirectories for the new release and upload the artifacts as
described? Are there any additional changes necessary that the download page shows the latest
release? When I remember correctly the archiving of the previous releases is done automatically, right?
What do we have to do to make the annotator package available for download? Can I just add the
additional artifacts?
-- Michael
schor@apache.org wrote:
> Author: schor
> Date: Mon May 5 06:56:57 2008
> New Revision: 653483
>
> URL: http://svn.apache.org/viewvc?rev=653483&view=rev
> Log:
> no Jira - add a bit more info to the how-to release docs, on how to upload to the mirroring system. Still have the eclipse update site to do
>
> Modified:
> incubator/uima/site/trunk/uima-website/xdocs/release.xml
>
> Modified: incubator/uima/site/trunk/uima-website/xdocs/release.xml
> URL: http://svn.apache.org/viewvc/incubator/uima/site/trunk/uima-website/xdocs/release.xml?rev=653483&r1=653482&r2=653483&view=diff
> ==============================================================================
> --- incubator/uima/site/trunk/uima-website/xdocs/release.xml (original)
> +++ incubator/uima/site/trunk/uima-website/xdocs/release.xml Mon May 5 06:56:57 2008
> @@ -161,9 +161,10 @@
> After the release is approved, we will have the last tagged release candidate which will correspond to the
> official release. This should not be updated after this.
> <ul>
> - <li><TODO> Upload the release artifacts to the distribution server (via uploading to people.apache.org
> + <li>Upload the release artifacts to the distribution server (via uploading to people.apache.org
> in the directory: <code>/www/www.apache.org/dist/uima</code>, including the
> - release artifacts and the Eclipse update site data.
> + release artifacts and the Eclipse update site data. Be sure to include the gpg/md5/sha1 signatures.
> + Make sure the KEYS file in that uploaded directory is current.
> <ul>
> <li>The Eclipse update site on w.a.o/dist/uima will have previous versions of the jars for the
> features and plugins. The generated site in
> @@ -174,7 +175,10 @@
> </ul>
> </li>
>
> - <li><TODO> Update the documentation page with the new data on the UIMA website</li>
> + <li>Update the documentation page with the new data on the UIMA website. The mirroring stuff is
> + embedded in the markup - just substitute within that markup the name of the new release
> + (assuming you followed the previous release's nameing conventions for the higher-level
> + directories).</li>
> <li>Upload the release artifacts to the Maven Incubator repository. To start the upload the
> following command must be executed from the uimaj project <br /><br/>
> <code>mvn -DsignArtifacts=true process-resources source:jar deploy</code><br/><br/>
>
>