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