Better would be to follow world practices and make BOINC API versioned.
Or why to keep BOINC client versioned then? Put all in one heap, rebuild it 
after each fix and update unversioned client on site. Why to bother with 
versions, not? ...


Mon, 03 Nov 2014 14:09:26 -0800 от David Anderson <[email protected]>:
>I removed references to server_release.
>-- David
>
>On 31-Oct-2014 4:49 PM, Richard Haselgrove wrote:
>> Documentation file  http://boinc.berkeley.edu/trac/wiki/SourceCodeGit 
>> contains the
>> text
>>
>> "For all software other than the client (i.e., server, web, and API) a 
>> "stable"
>> version is kept in a branch, server_release."
>>
>>
>> That wording has remained unchanged since
>>  http://boinc.berkeley.edu/trac/wiki/SourceCodeGit?version=1 : so far as I 
>> can
>> tell, it wasn't true then, and it certainly isn't true now. Searching 
>> through the
>> Tortoise Git Revision Graph, I can only find three references to 
>> server_release
>> tags, all from 2008 and 2009.
>>
>> Unfortunately, this confusion is leading certain developers to ignore the 
>> second
>> part of the sentence:
>>
>> "Don't use the server software in a client tag or branch; it probably isn't
>> stable."
>>
>> Could we possibly re-phrase this page, and attach some testing confidence 
>> level
>> to potential sources of the Server and API components of the BOINC code?
>> _______________________________________________ boinc_dev mailing list
>>  [email protected]
>>  http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, 
>> visit
>> the above URL and (near bottom of page) enter your email address.
>>
>_______________________________________________
>boinc_dev mailing list
>[email protected]
>http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
>To unsubscribe, visit the above URL and
>(near bottom of page) enter your email address.

_______________________________________________
boinc_dev mailing list
[email protected]
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.

Reply via email to