On 5/20/07, Eddie O'Neil <[EMAIL PROTECTED]> wrote:
+1 -- assuming the code is ready to go, I agree that it's a good
idea to go straight to 1.0.
+1 as well to waiting until the TLP infrastructure is complete,
which could take a week or more to unbrand from the Incubator, move
the website content, etc.
you will also need to set up the release infrastructure (mirroring,
download page and so on)
i recommend setting this up first (yes, apache should have
comprehensive scripts to do this but we don't as yet) so that people
can check everything
it's worth investing a little time on creating a good download page.
for many potential users, this is the only page they are going to
read. so, it's worth adding information about OpenJPA on that page.
the same content as the release notes is fine.
the documentation is on http://www.apache.org/dev. the mirrors take
24-48 to sync so you need to hold off the announcement till they have
so that the release is available for downloaders when the announcement
is made.
it's best to keep a record of all releases on the website. apache
releases are archived indefinitely and it's not uncommon for people to
want to know about historic releases. so, it's good to keep details of
each release around on the website. this is also good for indexing.
consider keeping full documentation of each release available on the
site.
- robert
