Hi,
> I'd argue there is nothing wrong with what we and AFAICS numerous other
> ASF projects do here.
That's a little concerning. I'd just like to point out ASF policy says
otherwise [1]. It will probably end up being discussed with Infra as they own
that policy, once that's been done, I get
Hi Justin,
Am 13.04.20 um 08:23 schrieb Justin Mclean:
> Hi,
>
>> Both artifacts however are technical upstream artifacts for framework
>> releases and it does not make any sense for them to be used outside of
>> this context, say by end users upgrading their stack.
>
> Well ASF policy states
Hi,
> Both artifacts however are technical upstream artifacts for framework
> releases and it does not make any sense for them to be used outside of
> this context, say by end users upgrading their stack.
Well ASF policy states anything released needs to be put in the offical release
area, so
Hi Justin,
good catch - it was overseen.
Both artifacts however are technical upstream artifacts for framework
releases and it does not make any sense for them to be used outside of
this context, say by end users upgrading their stack.
Does it make sense to list them in the report regardless?
Hi,
I see votes Struts Master 14 and Struts Annotations 1.0.7 that are not
mentioned in the board report or in the normal release area [1], but they seem
to have been published via maven and I just wondering why that is the case.
Thanks,
Justin
1.
