Regardless of the current state of the documentation, you must deploy
the documentation for the version being released. It is part of our
release process [1], see point 8. This helps our users know exactly
which version of the docs they are reading.
As a personal preference, I consider the documentation a part of a
release. If the docs are not finished, the release should be postponed
until they are. This of course has no bearing on the alpha-2 release,
because it had to go out quickly.
[1] http://maven.apache.org/developers/release/releasing.html
Raphaël Piéroni wrote:
Hi Tomasz,
The documentation for the plugin is currently under construction.
I hope to publish a better asap.
Regards
Raphaël
2008/2/23, Tomasz Pik <[EMAIL PROTECTED]>:
On Sat, Feb 23, 2008 at 1:20 AM, Brian Fox <[EMAIL PROTECTED]> wrote:
> The Maven team would like to announce the release of Maven Archetype
> 2.0-alpha-2. This release corrected backwards compatibility with the
> 1.0 version and a few windows issues. The site has also been updated
> and deployed: http://maven.apache.org/plugins/maven-archetype-plugin
Could you please verify this?
I've just checked and there's 'Last Published: 10 Feb 2008' and most of
'navigation' links points to 'page not found'.
Regards,
Tomek
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
