streampipes-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christofer Dutz <>
Subject Re: Website Migration / Non-Apache releases
Date Sat, 16 Nov 2019 13:30:51 GMT
If, for example you have a look here:

If you select the version: 0.7.0 it clearly states "pre-Apache" ... 


´╗┐Am 16.11.19, 14:28 schrieb "Christofer Dutz" <>:

    Hi Dominik,
    I don't think that you have to remove the references. But you have to make it clearly
visible that these are NOT Apache Releases. I think as soon as it's obvious (By being located
in a section "Non-Apache releases pre entering Incubation" this schoud be ok .. but I'm sure
Justin will know what and how to do it.
    Am 16.11.19, 13:40 schrieb "Dominik Riemer" <>:
        Sorry, the last sentence should have been: "Is that ok or do we need to remove all
references that allow users to download a pre-Apache release?
        On 2019/11/16 12:38:31, Dominik Riemer <<>>
        > Hi,
        > I'm currently working on migrating the current website to an Apache website and
read a little bit on how to handle pre-Apache releases.
        > I'd like to ask whether the following changes would be sufficient to comply with
ASF policy, while we would still allow users to download pre-Apache releases until our first
        > - on,  (will be later,
we would mark all versions with some "non-apache release" appendix (see the version in the
upper left corner) and also update the user guide with some disclaimer
        > - on,  (later,
we would add some fat disclaimer stating that the installer downloads a pre-Apache release
        > - on Github, we would add a "non-apache-release" appendix to all previously released
        > Is that ok or do we need to remove all references that allow users a pre-Apache
        > Dominik

View raw message