You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pivot.apache.org by Todd Volkert <tv...@gmail.com> on 2009/03/16 20:41:34 UTC
Release artifacts
> 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
Re: Release artifacts
Posted by Niclas Hedhman <ni...@hedhman.org>.
Just chipping in and confirming Martijn's suggestions. Be very clear!
A link to SourceForge project home is Ok, an automatic download link
from SF is not.
Cheers
Niclas
On Tue, Mar 17, 2009 at 5:13 AM, Martijn Dashorst
<ma...@gmail.com> wrote:
> On Mon, Mar 16, 2009 at 9:55 PM, Todd Volkert <tv...@gmail.com> wrote:
>> I see - makes sense. Is there any legal issue with posting
>> documentation that references prior versions?
>
> If that documentation is covered by your ICLA and grants, then not.
> Just make sure that it is absolutely clear that those releases are not
> Apache releases. See for example Wicket's download page:
>
> http://wicket.apache.org/getting-wicket.html
>
> We show people the way to Wicket 1.2.7 (which is the previous version
> of Wicket), but make it explicit that this is not an Apache release.
>
> Docs describing old behavior are not an issue at all, as long as the
> docs are covered by a CLA or grant.
>
> Martijn
>
--
http://www.qi4j.org - New Energy for Java
Re: Release artifacts
Posted by Martijn Dashorst <ma...@gmail.com>.
On Mon, Mar 16, 2009 at 9:55 PM, Todd Volkert <tv...@gmail.com> wrote:
> I see - makes sense. Is there any legal issue with posting
> documentation that references prior versions?
If that documentation is covered by your ICLA and grants, then not.
Just make sure that it is absolutely clear that those releases are not
Apache releases. See for example Wicket's download page:
http://wicket.apache.org/getting-wicket.html
We show people the way to Wicket 1.2.7 (which is the previous version
of Wicket), but make it explicit that this is not an Apache release.
Docs describing old behavior are not an issue at all, as long as the
docs are covered by a CLA or grant.
Martijn
Re: Release artifacts
Posted by Todd Volkert <tv...@gmail.com>.
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
<ma...@gmail.com> 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 <tv...@gmail.com> 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.
>
Re: Release artifacts
Posted by Martijn Dashorst <ma...@gmail.com>.
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 <tv...@gmail.com> 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.