<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<p dir="ltr">Hi guys,</p>
<p dir="ltr">Here's a simple and stupid suggestion:</p>
<p dir="ltr">1. Make a roadmap/plan that specifies when new releases should be made.</p>
<p dir="ltr">2. Stick to it.</p>
<p dir="ltr">3. Just check the system clock to see whether a new release is (probably) available</p>
<p dir="ltr">4. Nag the user to upgrade.</p>
<p dir="ltr">(I guess 1. and 2. are the hard part ;)</p>
<p dir="ltr">Regards,<br>
Åsmund<br>
</p>
<p dir="ltr">> From: Aron Ahmadia <aron@ahmadia.net><br>
> To: Matthew Knepley <knepley@gmail.com><br>
> Cc: For users of the development version of PETSc<br>
> <petsc-dev@mcs.anl.gov><br>
> Subject: Re: [petsc-dev] I hate nagupgrade<br>
> Message-ID:<br>
> <CAPhiW4i=1g55J=DWUR0Ncb07Q3cn91uObN-i9CCAwN0U5CfKRg@mail.gmail.com><br>
> Content-Type: text/plain; charset="utf-8"<br>
><br>
> On Tue, Nov 11, 2014 at 11:36 PM, Matthew Knepley <knepley@gmail.com> wrote:<br>
><br>
> > I don't actually care whether we keep this check. However, I do think the<br>
> > arguments advanced so far do<br>
> > not amount to more than prejudice. I don't think a security argument holds<br>
> > water for a system that<br>
> > downloads tarballs from other sites without any kind of check.<br>
> ><br>
><br>
> Are you referring to PETSc? All HashDist downloads are cryptographically<br>
> verified, which is one of the reasons we're trying to move away from this<br>
> sort of thing.<br>
><br>
> A</p>
</body>
</html>