[petsc-users] Release canditate?

[Barry Smith]

  Eric,

   Would it be possible for the release candidates to be a git repository branch or does it have to be a tarball? Generating and regenerating the tarball is a time consuming process which is why we don't use release candidates, but if you are able to test off the git repository we could certainly "pre announce" releases and allow testing before the actual release.


  Barry

> On Dec 11, 2015, at 10:18 PM, Éric Chamberland <Eric.Chamberland at giref.ulaval.ca> wrote:
> 
> Hi,
> 
> we just waited since petsc 3.5.4 until 3.6.3 to retrieve a working petsc for our usages (got bugs with 3.6.1, 3.6.2)
> 
> Now, just discovered 3.6.3 have a bug with mkl_pardiso... :/
> 
> We will have to wait until 3.6.4 (or patch the source with 3f7bb31...
> 
> I was thinking that it could have been otherwise if release candidate packages would have been made available for anyone to test...
> and to give you feedback... and then a better official release...
> 
> We can easily install it here and use the RC with our non-regression tests.
> 
> Maybe other users would be interested, like me, to test the release candidates?
> 
> Does that sounds interesting to you?
> 
> Thanks,
> 
> Eric
>