Jörn Kottmann wrote:
Hello,
the first release of the Cas Editor was approved by the IPMC.
Congratulations!
Are these the next steps, I have to do ?
1. Upload the release artifacts to:
p.a.o//www/www.apache.org/dist/incubator/uima/binaries
CasEditor-2.2.2-incubating
a slash missing in above. Also, to follow convention (not required, but
advised) use lower case?
pa.o/www/www.apache.org/dist/incubator/uima/sources/CasEditor-2.2.2-incubating
I haven't thought about this, but if you plan to have maven artifacts
(jars and poms) you need to upload these to the special incubator
repository for maven artifacts on people.a.o.
Any zips or jars (but not other files) need to have the signatures (asc,
md5, and sha) uploaded, as well. There are standard scripts to do this
(which you've probably already used).
2. Then update the download area of the uima website.
Keep the strange stuff that looks like codes in square brackets - this
is boilerplate used by the "mirroring" system for downloading.
3. Add a news item.
4. Send announce mails to uima-users and [EMAIL PROTECTED]
Announce mails according to protocol need to be sent from your
apache.org email address (otherwise they are rejected), and are supposed
to be signed by your code-signing key, used for the release artifacts.
And, the announcement *must* include the standard incubation disclaimer.
Anything else ?
Will this project use the Eclipse update site mechanism? If so, you
need to decide if it will use the same eclipse update site as other UIMA
projects, or one of its own, and build that site. See
http://incubator.apache.org/uima/release.html#Publish%20The%20Release
for details.
If you have a blog, you can blog a bit about this new capability. More
extensive PR has to be cleared by the Apache PR group (see
http://incubator.apache.org/guides/branding.html ).
-Marshall
Jörn
