[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn commit: r957751 - /subversion/site/publish/packages.html

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: Fri, 25 Jun 2010 15:12:11 -0400

Greg Stein wrote:
> On Fri, Jun 25, 2010 at 14:31, Mark Phippard <markphip_at_gmail.com> wrote:
>> The distinction we make internally at CollabNet over when we use the
>> term certified on our binaries is the process they go through before
>> posting.
>>
>> ...explanation...
>
> Thanks for that explanation. It helps below:
>
>> ...
>> I was fine with your wording change, and I am also fine with Julian's
>> corrections. If you think his changes are confusing I have no
>> objection to removing those changes. FWIW, I do think Julian's
>> wording makes it plainly clear that the certification is coming from
>> the company and not the Subversion project.
>
> I do think his wording is better than before my changes, but as I
> mentioned: any use of the word "certify" implies some kind of
> authority. Thus, the use implies somebody is reviewing and approving
> the process of creating those binaries.

Is "qualified" a more appropriate word for this purpose?

-- 
C. Michael Pilato <cmpilato_at_collab.net>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand

Received on 2010-06-25 21:12:51 CEST

This is an archived mail posted to the Subversion Dev mailing list.