I see - makes sense. Is there any legal issue with posting documentation that references prior versions?
-T On Mon, Mar 16, 2009 at 4:11 PM, Martijn Dashorst <[email protected]> wrote: > Unless the old releases are actual Apache releases, you won't be > allowed to publish them through the Apache website. Only Apache > releases are distributable through Apache (and its mirroring system). > > See for example Wicket: > - only apache releases: http://archive.apache.org/dist/wicket/ > - only old non-apache release: > http://sourceforge.net/project/showfiles.php?group_id=119783 > > The reason being that code that is developed at Apache (and brought in > through the incubator) can be released as Apache releases. Apache > can't take legal responsibility for old code. > > You'll have to build a release (and bring it to the Incubator PMC) > before you can unleash it to the masses. See the release guide for > more information [1]. > > Martijn > > [1] http://incubator.apache.org/guides/releasemanagement.html > > On Mon, Mar 16, 2009 at 8:41 PM, Todd Volkert <[email protected]> wrote: >>> Similar mechanism exist for releases, where you place the release >>> artifacts in dedicated locations on people.apache.org, and the mirrors >>> will pull it from there. (For releases, mirrors are definitely needed) >> >> Niclas, >> >> I'm setting up our documentation site, and I'd like to provide links >> to download the previous releases of Pivot (namely 1.0.1, but 1.0 in >> the archives too if possible). What's the mechanism for how we get >> the release artifacts out to all mirrors and create pages from which >> users can download them? >> >> Thanks, >> -T >> > > > > -- > Become a Wicket expert, learn from the best: http://wicketinaction.com > Apache Wicket 1.3.5 is released > Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3. >
