www-legal-discuss mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stephen Connolly <stephen.alan.conno...@gmail.com>
Subject Re: Asking on users@ for release candidate testers
Date Mon, 30 Jun 2014 14:12:40 GMT
Andrea's answer struck a better cord with me: namely if the project's PMC
says that their testers are on users@ and their user community understands
test artifacts... all is good.

The reason I suggested an additional list is that users may want to help
testing, but don't want the noise of the dev mailing list... or at least
fear the noise of a dev@ list. If they are signing up to a ML that is
specifically for people testing RCs then they know that only emails
relevant to that purpose *should* be served on that ML.

But at the end of the day, each individual PMC knows its community best, as
long as the only "public" artifacts published from ASF hardware are
official releases then it should not matter... the question is when does a
link become public.

Certainly once it hits the announce@ ML the link is public... whether or if
the users@ list is considered public sounds like a PMC decision per project

On 30 June 2014 13:03, Andy Wenk <andywenk@apache.org> wrote:

> Hi,
> please don't get me wrong, but the suggested answers here do bring a
> tremendous overhead which is not needed.
> As far as I understand, dev@ is the list where the request to test rc
> artefacts should be sent to. The dev@ list is intended to do all the work
> on development and so is to test rc candidates. Imho there is no need to
> introduce more ml's. The risk that developers are kept away to help or test
> rc's is out of my experience high.
> I would like to understand why it could be problematic to distribute rc
> artefacts from ASF hardware. Or did I misunderstand that point in the
> discussion above?
> Furthermore I would like to understand better, why people could be scared
> by a dev@ list? Who is 'people' here :) ?
> Again, maybe I do miss some important points. If so, I would be happy to
> understand it better :). Otherwise I suggest to send the rc artefacts to
> dev@ and ask for testing.
> Cheers
> Andy
> On 30 June 2014 12:11, Stephen Connolly <stephen.alan.connolly@gmail.com>
> wrote:
>> Why not just set up a mailing list for testing releases and that way you
>> can encourage users to sign up as "testers" that way they are not the
>> general public.
>> For the artifacts to be distributed from ASF hardware (other that peoples
>> ~username sites AFAIR) then they need to be voted on and released.
>> You could distribute them from non-ASF hardware, but then the people
>> creating those binaries now have to *personally* worry about whether they
>> are covered in the event that a virus/trojan was bundled in the binary, etc
>> as the binary is being distributed from *their* hardware (or from their
>> ~username site on apache.org)
>> So if the dev@ list is too scary, I would just set up a qa or
>> release-testers list. That way you can call them out and give credit for
>> their assistance when the release is cut, and you can safely publish links
>> in that list.
>> On 30 June 2014 10:44, Paul Libbrecht <paul@hoplahup.net> wrote:
>>> Alex,
>>> get the folks to discuss RC on some other place than the dev list…
>>> people are scared by dev lists.
>>> IRC or Jira, or even a single mail thread in the users list, are fairly
>>> constrained places where you wouldn't scare people to come, I think.
>>> paul
>>> On 30 juin 2014, at 08:59, Alex Harui <aharui@adobe.com> wrote:
>>> > Today's debate is about whether Apache Flex can email its users@ ML
>>> and ask folks there to help us test the current release candidate.  I think
>>> current release policy says no.  But is there a loophole where we can email
>>> users@ and ask folks to join dev@ in order to find out how to test the
>>> RC?
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
>>> For additional commands, e-mail: legal-discuss-help@apache.org
> --
> Andy Wenk
> Hamburg - Germany
> RockIt!
> GPG fingerprint: C044 8322 9E12 1483 4FEC 9452 B65D 6BE3 9ED3 9588
>  https://people.apache.org/keys/committer/andywenk.asc

View raw message