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 anything released needs to be put in the offical > release area, so you may need permission form the board to do it like this? > No need to rush to change anything right now. I can get back to you after > this is discussed at (or before) the next board meeting. >
I'd argue there is nothing wrong with what we and AFAICS numerous other ASF projects do here. These are official releases of artifatcs that have a slightly different lifecycle than the framework releases relevant to end users, which is why they were separated. End users will consume theses artifacts as transitive dependencies when upgrading to the next framework release, but it does not make sense to download them or use or upgrade them directly in end user software projects. So these are official releases that do not qualify for, say, issueing a press release :) But if the board thinks this needs adjustment we will be happy to apply the then requested changes. >> Does it make sense to list them in the report regardless? > > The PMC voted on them so I'd say it makes sense to list then, but then you > might get asked why they are not in the release area.:-) > Actually we have done this in the past, and as I stated, I have simply overseen it :) But this also raised the question above... >> Should I adjust the already submitted report? > > If you want to sure, but there's no need as I’ve added a comment to the > report. Given that there is enough time left before the board meeting starts, I'll adjust it then. Thanks, René > > Thanks, > Justin > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org > For additional commands, e-mail: dev-h...@struts.apache.org > -- René Gielen http://twitter.com/rgielen --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
