Sharing some thoughts about this particular question. The intention of the
guideline is to clearly distinguish the Apache from non-apache ones (to
protect apache's brand).
There are a few ways to achieve so:
- W0: Change the release note to indicate the tag is non-apache
- W1: Change the release
Hi Justin,
I have a question about the guidelines.
> Any releases that exist before coming into incubation need to be clearly
described on the release page and tagged as such on
Does this mean that we need to change the tag/release name from something
like "4.1.0" to be "4.1.0-non-apache-release
On 2020/10/05 11:35:39, Justin Mclean wrote:
> Hi,
>
> Thanks for the feedback.
>
> > There's some spurious text at the start of the page.
>
> I’ll remove this.
>
> > Also, what does the acronym IP mean?
>
> IP = Intellectual property
It was a rhetorical question: the reader may not know wh
Hi,
Thanks for the feedback.
> There's some spurious text at the start of the page.
I’ll remove this.
> Also, what does the acronym IP mean?
IP = Intellectual property
> - "Releases must be placed in the Apache mirror system."
> Which releases are being referred to here? Source and binaries,
There's some spurious text at the start of the page:
"Skip to end of metadata Created by ASF Infrabot, last modified by
Justin Mclean on Jul 14, 2020 Go to start of metadata"
Also, what does the acronym IP mean?
I think there are some ambiguities:
- "Releases must be placed in the Apache mirror
