Re: [boinc_dev] release 7.8.3?

[Steffen Möller]

Hi Laurence,

On 22.10.17 23:04, Laurence wrote:

> The BOINC client v7.8.3 is available for testing on Linux
>
> For Debian/Ubuntu
>
> sudo apt-add-repository ppa:costamagnagianfranco/boinc
> sudo apt-get update
> sudo apt-get install boinc-manager

kind of :)

For the regular user of Debian-derived distros, "sudo apt-get install
boinc" is the way to go. No extras.

boinc-manager is the GUI for controlling local or remote clients.
boinc-client is the client with the boinccmd command line.

to install both in one go there is the aforementioned third package
(consisting only of dependencies to boinc-manager and boinc-client) with
the name "boinc".

Both Debian and Ubuntu have BOINC packages shipping as regular parts of
their distribution since version 5.2.15 in March 2006. This is some
freaking 12 years, see http://snapshot.debian.org/package/boinc/.   Mint
also takes it from there. The PPA (personal package archive) of
Gianfranco is a neat extra service for those aiming at running the very
latest very early but do not run the latest version of the distribution
(where does this guy get all the energy from? Ubuntu Artful is on 7.8.3,
Zesty still on 7.6.33, but later backports to the earlier versions of
Ubuntu are to be expected). The same Gianfranco (and sometimes also I)
do for the backports.debian.org. It is all in perfect shape as seen on
https://tracker.debian.org/pkg/boinc .  As TarotApprentice had pointed
out, this needs an extra flag to apt-get like -t stretch-backports to be
installed instead of the sufficiently recent of Debian stable.

The number of Debian installations are mostly invariant at
https://qa.debian.org/popcon.php?package=boinc .  The Ubuntu PopCon is a
bit more tedious to read - 45204 installations are reported from those
who installed the popularity-contest package. No idea about the other
Debian derivatives.


>
> For Fedora/RedHat/CentOS
>
> sudo dnf config-manager --set-enable updates-testing
> sudo dnf install boinc-manager
>
> Test reports can be sent to the alpha testing project and bugs can be
> reported to the Fedora or Debian bug trackers respectively.
>
OpenSuSE has https://software.opensuse.org/package/boinc-client but is
still at 7.2.42.   For arch I found
https://wiki.archlinux.org/index.php/BOINC and
https://www.archlinux.org/packages/?q=boinc but they are still at 7.6.33
. I have no contact to either of those maintainers but would only be
worried for the also RPM-based SuSE community.

I very much agree that a distribution-agnostic self-extracting static
version makes perfect sense until those distributions are also covered.
However, I would rather work on finding volunteer packagers for those
platforms than to work on the .sea for those who do not want to compile
the very latest versions themselves. archlinux likely only needs a
friendly email informing the maintainers that the 7.8.3 can now be trusted.

Cheers,

Steffen


>
> On 16/10/17 00:49, David Anderson wrote:
>> 7.8.3 has 90% test coverage and it looks good.
>> Any objections to releasing it?
>> -- David
>> ___
>> boinc_dev mailing list
>> boinc_dev@ssl.berkeley.edu
>> https://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
> boinc_dev@ssl.berkeley.edu
> https://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
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.

Re: [boinc_dev] release 7.8.3?

[Laurence]

The BOINC client v7.8.3 is available for testing on Linux

For Debian/Ubuntu

sudo apt-add-repository ppa:costamagnagianfranco/boinc
sudo apt-get update
sudo apt-get install boinc-manager

For Fedora/RedHat/CentOS

sudo dnf config-manager --set-enable updates-testing
sudo dnf install boinc-manager

Test reports can be sent to the alpha testing project and bugs can be 
reported to the Fedora or Debian bug trackers respectively.


Regards,

Laurence


On 16/10/17 00:49, David Anderson wrote:

7.8.3 has 90% test coverage and it looks good.
Any objections to releasing it?
-- David
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://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
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.

Re: [boinc_dev] release 7.8.3?

[Richard Haselgrove]

Presumably it would be worth enquiring into the coverage offered by the 
distribution-specific packaged versions, before committing any resources. What 
proportion of our Linux volunteers (both current and potential) are running a 
dialect of Linux for which there is an active package maintainer?

SETI@Home used to maintain a list of client versions used at their project. The 
script hasn't been maintained for several years, but 
https://setiathome.berkeley.edu/client_types.php shows what was being used as 
at March 19 2013 (considerably earlier than the last Berkeley compatibility 
packages). If that script could be tickled into life again for one last hurrah, 
we might get a snapshot of the balance between Linux versions 7.2.42/7.4.22 
(presumed Berkeley) and versions 7.6.33/7.8.3 (presumed distro maintainer).

We ought also to mention security. As I understand it, the distro maintainers 
tend to implement restricted-user sandboxing, whereas the Berkeley 
static-linked .sea packages ran in user space. Volunteers who like to tinker 
with their installations sometimes find the latter approach easier to work 
with. 

On Sunday, 22 October 2017, 15:49, Steffen Möller  
wrote:
 

 Hello,

On 17.10.17 00:15, David Anderson wrote:
> Our policy for a long time was:
>
> - provide a .sea release (including manager) for current Ubuntu/x86,
>   with no effort to make it run anywhere else.
> - provide a client-only (no manager) release built on an old Linux
> system,
>   everything static, for maximum compatibility.
>   We have a "compatability VM" in which to build this.
Close to nothing on Ubuntu is statically linked. And for BOINC there is
not need to be statically linked, either - when shipping as as part of the
distribution, this is.
> At some point (maybe when Rom left) we stopped doing this.
> I suggest that we start again.
> Maybe change to 64 bit.

Of course you can just go and do that. And for the "competition is
always good"
mantra or as a reference for bug reports I am also embracing that. A
complementary strategy could be to just embrace all those volunteer
packagers out there and call them a part of BOINC.

I have not talked back to Gianfranco about it, but I have some confidence
that he does not mind to move the Debian/Ubuntu-package build instructions
from git.debian.org to github for easier accessibility, if that is of
any help.

Best,

Steffen


>
> On 10/16/2017 7:46 AM, Steffen Möller wrote:
>> On 16.10.17 15:07, Laurence wrote:
>>> Hi Jord,
>>>
>>> On 16/10/17 12:24, Jord van der Elst wrote:
 On Mon, Oct 16, 2017 at 12:06 PM, Richard Haselgrove
 mailto:r.haselgr...@btopenworld.com>>
 wrote:

  Berkeley has outsourced the distribution of Linux clients to the
  package maintainers for individual distributions, for several
  years now.


 Laurence is the release manager for Linux, I suspect he knows about
 all of that. :-)
>>> No I didn't, so thanks.  Only stepped forward after the September
>>> workshop.
 But even if the distro package maintainers release these versions,
 they also do so first for testing and can then still ask people to
 report their results on the Alpha project. Their source code is still
 coming from github as well.
>>> Even if the package maintainers build and release, as you pointed out
>>> the versioned upstream code still comes from the project. I have just
>>> discovered that Gianfranco is doing daily builds (every 4h) and
>>> creating packages for Debian from the git master. This is a nice step
>>> towards CI.
>> And he also builds the complete packages together with the server side
>> components afterwards that go to the experimental section of Debian -
>> see the boinc-server-maker package
>> https://packages.qa.debian.org/b/boinc/news/20171005T094923Z.html.  It
>> would help a lot if the server bits in master are always be at a stage
>> that it could be released.
>>
>> In my mind this goes as far as that for automated testing we could have
>> dummy project set up in an automated fashion and do few workunits on
>> those.
>>
>> Cheers,
>>
>> Steffen
>>
>> ___
>> boinc_dev mailing list
>> boinc_dev@ssl.berkeley.edu
>> https://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
> boinc_dev@ssl.berkeley.edu
> https://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
boinc_dev@ssl.berkeley.edu
https://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
boinc_dev@ssl.berkele

Re: [boinc_dev] release 7.8.3?

[Steffen Möller]

Hello,

On 17.10.17 00:15, David Anderson wrote:
> Our policy for a long time was:
>
> - provide a .sea release (including manager) for current Ubuntu/x86,
>   with no effort to make it run anywhere else.
> - provide a client-only (no manager) release built on an old Linux
> system,
>   everything static, for maximum compatibility.
>   We have a "compatability VM" in which to build this.
Close to nothing on Ubuntu is statically linked. And for BOINC there is
not need to be statically linked, either - when shipping as as part of the
distribution, this is.
> At some point (maybe when Rom left) we stopped doing this.
> I suggest that we start again.
> Maybe change to 64 bit.

Of course you can just go and do that. And for the "competition is
always good"
mantra or as a reference for bug reports I am also embracing that. A
complementary strategy could be to just embrace all those volunteer
packagers out there and call them a part of BOINC.

I have not talked back to Gianfranco about it, but I have some confidence
that he does not mind to move the Debian/Ubuntu-package build instructions
from git.debian.org to github for easier accessibility, if that is of
any help.

Best,

Steffen


>
> On 10/16/2017 7:46 AM, Steffen Möller wrote:
>> On 16.10.17 15:07, Laurence wrote:
>>> Hi Jord,
>>>
>>> On 16/10/17 12:24, Jord van der Elst wrote:
 On Mon, Oct 16, 2017 at 12:06 PM, Richard Haselgrove
 mailto:r.haselgr...@btopenworld.com>>
 wrote:

  Berkeley has outsourced the distribution of Linux clients to the
  package maintainers for individual distributions, for several
  years now.


 Laurence is the release manager for Linux, I suspect he knows about
 all of that. :-)
>>> No I didn't, so thanks.  Only stepped forward after the September
>>> workshop.
 But even if the distro package maintainers release these versions,
 they also do so first for testing and can then still ask people to
 report their results on the Alpha project. Their source code is still
 coming from github as well.
>>> Even if the package maintainers build and release, as you pointed out
>>> the versioned upstream code still comes from the project. I have just
>>> discovered that Gianfranco is doing daily builds (every 4h) and
>>> creating packages for Debian from the git master. This is a nice step
>>> towards CI.
>> And he also builds the complete packages together with the server side
>> components afterwards that go to the experimental section of Debian -
>> see the boinc-server-maker package
>> https://packages.qa.debian.org/b/boinc/news/20171005T094923Z.html.  It
>> would help a lot if the server bits in master are always be at a stage
>> that it could be released.
>>
>> In my mind this goes as far as that for automated testing we could have
>> dummy project set up in an automated fashion and do few workunits on
>> those.
>>
>> Cheers,
>>
>> Steffen
>>
>> ___
>> boinc_dev mailing list
>> boinc_dev@ssl.berkeley.edu
>> https://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
> boinc_dev@ssl.berkeley.edu
> https://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
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.

Re: [boinc_dev] release 7.8.3?

[David Anderson]

https://boinc.berkeley.edu/trac/wiki/AdminTasks
and
https://boinc.berkeley.edu/trac/wiki/AdminAlphaTest

On 10/16/2017 2:16 AM, Laurence wrote:
Thanks,  I did not know about this. Is this documented anywhere? How are the 
results collected? I notice that there is an absence for the Linux operating 
system but as 3/4 of the resources are from Windows user, the Windows client is 
obviously more important.


Laurence



On 16/10/17 10:47, Jord van der Elst wrote:
Laurence, the test number comes from 
https://boinc.berkeley.edu/alpha/test_summary.php with no red reports at all: 
https://boinc.berkeley.edu/alpha/test_details.php?version=7.8.3


The only (major) problem still there is for the Spanish person, but I think 
that's either a missing character and thus easily fixed, or it requires a major 
Spanish translation of everything and that's then a slightly bigger problem. But 
this problem will continue until it's been fixed in Transifex and tested.



-- Jord van der Elst.

On Mon, Oct 16, 2017 at 10:17 AM, Laurence > wrote:


    On 16/10/17 00:49, David Anderson wrote:

    7.8.3 has 90% test coverage and it looks good.

    Where does the 90% come from?

    Any objections to releasing it?

    A few issues need to be addressed before releasing on Linux. There
    is no reason why this should block the Windows and Mac releases
    though. We can skip 7.8.3 for Linux and release 7.8.4.

    Cheers,

    Laurence
    ___
    boinc_dev mailing list
    boinc_dev@ssl.berkeley.edu 
    https://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
boinc_dev@ssl.berkeley.edu
https://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
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.

Re: [boinc_dev] release 7.8.3?

[David Anderson]

Our policy for a long time was:

- provide a .sea release (including manager) for current Ubuntu/x86,
  with no effort to make it run anywhere else.
- provide a client-only (no manager) release built on an old Linux system,
  everything static, for maximum compatibility.
  We have a "compatability VM" in which to build this.

At some point (maybe when Rom left) we stopped doing this.
I suggest that we start again.
Maybe change to 64 bit.

-- David


On 10/16/2017 7:46 AM, Steffen Möller wrote:

On 16.10.17 15:07, Laurence wrote:

Hi Jord,

On 16/10/17 12:24, Jord van der Elst wrote:

On Mon, Oct 16, 2017 at 12:06 PM, Richard Haselgrove
mailto:r.haselgr...@btopenworld.com>>
wrote:

     Berkeley has outsourced the distribution of Linux clients to the
     package maintainers for individual distributions, for several
     years now.


Laurence is the release manager for Linux, I suspect he knows about
all of that. :-)

No I didn't, so thanks.  Only stepped forward after the September
workshop.

But even if the distro package maintainers release these versions,
they also do so first for testing and can then still ask people to
report their results on the Alpha project. Their source code is still
coming from github as well.

Even if the package maintainers build and release, as you pointed out
the versioned upstream code still comes from the project. I have just
discovered that Gianfranco is doing daily builds (every 4h) and
creating packages for Debian from the git master. This is a nice step
towards CI.

And he also builds the complete packages together with the server side
components afterwards that go to the experimental section of Debian -
see the boinc-server-maker package
https://packages.qa.debian.org/b/boinc/news/20171005T094923Z.html.  It
would help a lot if the server bits in master are always be at a stage
that it could be released.

In my mind this goes as far as that for automated testing we could have
dummy project set up in an automated fashion and do few workunits on those.

Cheers,

Steffen

___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://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
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.

Re: [boinc_dev] release 7.8.3?

[Steffen Möller]

On 16.10.17 23:07, Laurence Field wrote:
> Hi Steffen,
>
> On 16/10/17 16:46, Steffen Möller wrote:
>>
>> And he also builds the complete packages together with the server side
>> components afterwards that go to the experimental section of Debian -
>> see the boinc-server-maker package
>> https://packages.qa.debian.org/b/boinc/news/20171005T094923Z.html.  It
>> would help a lot if the server bits in master are always be at a stage
>> that it could be released.
> Thanks, I was already aware of the server in the experimental section
> and completely agree that master should always be 'deployable'.
> Recently I built a server package for CentOS7 and asked for some
> feedback on this very list. There was none.

That server-side package is somewhat of importance to me - please kindly
(re)send me a pointer to your packaging instructions and I certainly
will have comments - I mean, I have tons of comments on what I had once
come up with :)

> At the BOINC workshop in Paris this was discussed and the consensus
> was to try using Docker for the server releases.

Right. Would work. And it would make some sense to capsule it all away,
too. I just hope you get it into Docker/Singularity as a package, not
from the sources.

The boinc-server-maker package ships make-project, including the example
apps, so there is no need to perform the compilation, and the Docker
image is based on Debian (old-stable) anyway. Takes far less than five
minutes, too :)

> The approach was stimulated by this presentation from Marius. We at
> LHC@home plan to investigate this for our project at some point in the
> future.
>
> https://indico.cern.ch/event/648533/contributions/2710464/attachments/1519821/2373725/boincserverdocker.pdf
>

Except that your are in Scientific Linux land, so I presume.


>> In my mind this goes as far as that for automated testing we could have
>> dummy project set up in an automated fashion and do few workunits on
>> those.
>>
> It seems from the presentation that we are not that far from this goal.

Good.

The server side is not only about getting the project going. It is also
about clarifying the exact include paths and generally helping projects
with updates/upgrades of the BOINC-parts of their infrastructure. And
then it does not matter if you run on bare metal or with some sort of
virtualisation. You want to know about what version of the BOINC server
was updated with what other version and that it has worked. Linux
distributions are pretty good at this. As a neat side effect, the
example projects get compiled for the many architectures of Debian,
which you can collect and distribute to clients.

Most important to me is that the BOINC server as a package in a regular
Linux distribution brings (data parallel) HPC to every home, to every
scientific institute. I tend to think of it as a social achievement.
Having containers/a VM in between is desirable for security purposes,
but it also weakens the point a bit.

Sorry for being somewhat "emotional" here,

Steffen


___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.

Re: [boinc_dev] release 7.8.3?

[Laurence Field]

Hi Steffen,

On 16/10/17 16:46, Steffen Möller wrote:


And he also builds the complete packages together with the server side
components afterwards that go to the experimental section of Debian -
see the boinc-server-maker package
https://packages.qa.debian.org/b/boinc/news/20171005T094923Z.html.  It
would help a lot if the server bits in master are always be at a stage
that it could be released.
Thanks, I was already aware of the server in the experimental section 
and completely agree that master should always be 'deployable'. Recently 
I built a server package for CentOS7 and asked for some feedback on this 
very list. There was none. At the BOINC workshop in Paris this was 
discussed and the consensus was to try using Docker for the server 
releases. The approach was stimulated by this presentation from Marius. 
We at LHC@home plan to investigate this for our project at some point in 
the future.


https://indico.cern.ch/event/648533/contributions/2710464/attachments/1519821/2373725/boincserverdocker.pdf

In my mind this goes as far as that for automated testing we could have
dummy project set up in an automated fashion and do few workunits on those.


It seems from the presentation that we are not that far from this goal.

Cheers,

Laurence
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.

Re: [boinc_dev] release 7.8.3?

[Steffen Möller]

On 16.10.17 15:07, Laurence wrote:
> Hi Jord,
>
> On 16/10/17 12:24, Jord van der Elst wrote:
>> On Mon, Oct 16, 2017 at 12:06 PM, Richard Haselgrove
>> mailto:r.haselgr...@btopenworld.com>>
>> wrote:
>>
>>     Berkeley has outsourced the distribution of Linux clients to the
>>     package maintainers for individual distributions, for several
>>     years now.
>>
>>
>> Laurence is the release manager for Linux, I suspect he knows about
>> all of that. :-)
> No I didn't, so thanks.  Only stepped forward after the September
> workshop.
>> But even if the distro package maintainers release these versions,
>> they also do so first for testing and can then still ask people to
>> report their results on the Alpha project. Their source code is still
>> coming from github as well.
> Even if the package maintainers build and release, as you pointed out
> the versioned upstream code still comes from the project. I have just
> discovered that Gianfranco is doing daily builds (every 4h) and
> creating packages for Debian from the git master. This is a nice step
> towards CI.

And he also builds the complete packages together with the server side
components afterwards that go to the experimental section of Debian -
see the boinc-server-maker package
https://packages.qa.debian.org/b/boinc/news/20171005T094923Z.html.  It
would help a lot if the server bits in master are always be at a stage
that it could be released.

In my mind this goes as far as that for automated testing we could have
dummy project set up in an automated fashion and do few workunits on those.

Cheers,

Steffen

___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.

Re: [boinc_dev] release 7.8.3?

[Laurence]

Hi Jord,

On 16/10/17 12:24, Jord van der Elst wrote:
On Mon, Oct 16, 2017 at 12:06 PM, Richard Haselgrove 
mailto:r.haselgr...@btopenworld.com>> 
wrote:


Berkeley has outsourced the distribution of Linux clients to the
package maintainers for individual distributions, for several
years now.


Laurence is the release manager for Linux, I suspect he knows about 
all of that. :-)

No I didn't, so thanks.  Only stepped forward after the September workshop.
But even if the distro package maintainers release these versions, 
they also do so first for testing and can then still ask people to 
report their results on the Alpha project. Their source code is still 
coming from github as well.
Even if the package maintainers build and release, as you pointed out 
the versioned upstream code still comes from the project. I have just 
discovered that Gianfranco is doing daily builds (every 4h) and creating 
packages for Debian from the git master. This is a nice step towards CI.


Cheers,

Laurence
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.

Re: [boinc_dev] release 7.8.3?

[Jord van der Elst]

On Mon, Oct 16, 2017 at 12:06 PM, Richard Haselgrove <
r.haselgr...@btopenworld.com> wrote:

> Berkeley has outsourced the distribution of Linux clients to the package
> maintainers for individual distributions, for several years now.
>

Laurence is the release manager for Linux, I suspect he knows about all of
that. :-)
But even if the distro package maintainers release these versions, they
also do so first for testing and can then still ask people to report their
results on the Alpha project. Their source code is still coming from github
as well.

-- Jord van der Elst.
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.

Re: [boinc_dev] release 7.8.3?

[Richard Haselgrove]

Berkeley has outsourced the distribution of Linux clients to the package 
maintainers for individual distributions, for several years now.

The latest versions endorsed by Berkeley and offered on 
http://boinc.berkeley.edu/download_all.php are:

Recommended version: 7.2.42 (28 February 2014)
'Development' version: 7.4.22 (17 September 2014)

Releases of the 7.4 branch stopped well before development was deemed complete: 
that branch reached 7.4.42 for Windows and Mac on 9 March 2015. 

On Monday, 16 October 2017, 10:29, Jord van der Elst  
wrote:
 

 Start here: https://boinc.berkeley.edu/alpha/index.php
There's an absence of Linux entries, because we do not have a 7.8.3
available for testing 'from Berkeley', but only via people like Gianfranco
from his personal PPA. If he (or you) were to request that the people
testing that version would add their outcome to that page, we (read David)
can add Linux options to the Test Form (
https://boinc.berkeley.edu/alpha/test_form.php) page.

As David explained in the past meeting a set of requirements are needed for
a version to pass testing.
I can't find so quickly that these are documented on this page, but that
can always be added.


-- Jord van der Elst.

On Mon, Oct 16, 2017 at 11:16 AM, Laurence  wrote:

> Thanks,  I did not know about this. Is this documented anywhere? How are
> the results collected? I notice that there is an absence for the Linux
> operating system but as 3/4 of the resources are from Windows user, the
> Windows client is obviously more important.
>
> Laurence
>
>
> On 16/10/17 10:47, Jord van der Elst wrote:
>
> Laurence, the test number comes from https://boinc.berkeley.edu/
> alpha/test_summary.php with no red reports at all:
> https://boinc.berkeley.edu/alpha/test_details.php?version=7.8.3
>
> The only (major) problem still there is for the Spanish person, but I
> think that's either a missing character and thus easily fixed, or it
> requires a major Spanish translation of everything and that's then a
> slightly bigger problem. But this problem will continue until it's been
> fixed in Transifex and tested.
>
>
> -- Jord van der Elst.
>
> On Mon, Oct 16, 2017 at 10:17 AM, Laurence  wrote:
>
>> On 16/10/17 00:49, David Anderson wrote:
>>
>>> 7.8.3 has 90% test coverage and it looks good.
>>>
>> Where does the 90% come from?
>>
>>> Any objections to releasing it?
>>>
>> A few issues need to be addressed before releasing on Linux. There is no
>> reason why this should block the Windows and Mac releases though. We can
>> skip 7.8.3 for Linux and release 7.8.4.
>>
>> Cheers,
>>
>> Laurence
>> ___
>> boinc_dev mailing list
>> boinc_dev@ssl.berkeley.edu
>> https://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
boinc_dev@ssl.berkeley.edu
https://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
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.

Re: [boinc_dev] release 7.8.3?

[Jord van der Elst]

Start here: https://boinc.berkeley.edu/alpha/index.php
There's an absence of Linux entries, because we do not have a 7.8.3
available for testing 'from Berkeley', but only via people like Gianfranco
from his personal PPA. If he (or you) were to request that the people
testing that version would add their outcome to that page, we (read David)
can add Linux options to the Test Form (
https://boinc.berkeley.edu/alpha/test_form.php) page.

As David explained in the past meeting a set of requirements are needed for
a version to pass testing.
I can't find so quickly that these are documented on this page, but that
can always be added.


-- Jord van der Elst.

On Mon, Oct 16, 2017 at 11:16 AM, Laurence  wrote:

> Thanks,  I did not know about this. Is this documented anywhere? How are
> the results collected? I notice that there is an absence for the Linux
> operating system but as 3/4 of the resources are from Windows user, the
> Windows client is obviously more important.
>
> Laurence
>
>
> On 16/10/17 10:47, Jord van der Elst wrote:
>
> Laurence, the test number comes from https://boinc.berkeley.edu/
> alpha/test_summary.php with no red reports at all:
> https://boinc.berkeley.edu/alpha/test_details.php?version=7.8.3
>
> The only (major) problem still there is for the Spanish person, but I
> think that's either a missing character and thus easily fixed, or it
> requires a major Spanish translation of everything and that's then a
> slightly bigger problem. But this problem will continue until it's been
> fixed in Transifex and tested.
>
>
> -- Jord van der Elst.
>
> On Mon, Oct 16, 2017 at 10:17 AM, Laurence  wrote:
>
>> On 16/10/17 00:49, David Anderson wrote:
>>
>>> 7.8.3 has 90% test coverage and it looks good.
>>>
>> Where does the 90% come from?
>>
>>> Any objections to releasing it?
>>>
>> A few issues need to be addressed before releasing on Linux. There is no
>> reason why this should block the Windows and Mac releases though. We can
>> skip 7.8.3 for Linux and release 7.8.4.
>>
>> Cheers,
>>
>> Laurence
>> ___
>> boinc_dev mailing list
>> boinc_dev@ssl.berkeley.edu
>> https://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
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.

Re: [boinc_dev] release 7.8.3?

[Laurence]

Thanks,  I did not know about this. Is this documented anywhere? How are 
the results collected? I notice that there is an absence for the Linux 
operating system but as 3/4 of the resources are from Windows user, the 
Windows client is obviously more important.


Laurence



On 16/10/17 10:47, Jord van der Elst wrote:
Laurence, the test number comes from 
https://boinc.berkeley.edu/alpha/test_summary.php with no red reports 
at all: https://boinc.berkeley.edu/alpha/test_details.php?version=7.8.3


The only (major) problem still there is for the Spanish person, but I 
think that's either a missing character and thus easily fixed, or it 
requires a major Spanish translation of everything and that's then a 
slightly bigger problem. But this problem will continue until it's 
been fixed in Transifex and tested.



-- Jord van der Elst.

On Mon, Oct 16, 2017 at 10:17 AM, Laurence > wrote:


On 16/10/17 00:49, David Anderson wrote:

7.8.3 has 90% test coverage and it looks good.

Where does the 90% come from?

Any objections to releasing it?

A few issues need to be addressed before releasing on Linux. There
is no reason why this should block the Windows and Mac releases
though. We can skip 7.8.3 for Linux and release 7.8.4.

Cheers,

Laurence
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu 
https://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
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.

Re: [boinc_dev] release 7.8.3?

[Jord van der Elst]

Laurence, the test number comes from
https://boinc.berkeley.edu/alpha/test_summary.php with no red reports at
all: https://boinc.berkeley.edu/alpha/test_details.php?version=7.8.3

The only (major) problem still there is for the Spanish person, but I think
that's either a missing character and thus easily fixed, or it requires a
major Spanish translation of everything and that's then a slightly bigger
problem. But this problem will continue until it's been fixed in Transifex
and tested.


-- Jord van der Elst.

On Mon, Oct 16, 2017 at 10:17 AM, Laurence  wrote:

> On 16/10/17 00:49, David Anderson wrote:
>
>> 7.8.3 has 90% test coverage and it looks good.
>>
> Where does the 90% come from?
>
>> Any objections to releasing it?
>>
> A few issues need to be addressed before releasing on Linux. There is no
> reason why this should block the Windows and Mac releases though. We can
> skip 7.8.3 for Linux and release 7.8.4.
>
> Cheers,
>
> Laurence
> ___
> boinc_dev mailing list
> boinc_dev@ssl.berkeley.edu
> https://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
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.

Re: [boinc_dev] release 7.8.3?

[Laurence]

On 16/10/17 00:49, David Anderson wrote:

7.8.3 has 90% test coverage and it looks good.

Where does the 90% come from?

Any objections to releasing it?
A few issues need to be addressed before releasing on Linux. There is no 
reason why this should block the Windows and Mac releases though. We can 
skip 7.8.3 for Linux and release 7.8.4.


Cheers,

Laurence
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.