[petsc-dev] confusing download instructions

Barry Smith bsmith at mcs.anl.gov
Thu Jun 27 23:27:59 CDT 2013


    On http://www.mcs.anl.gov/petsc/download/index.html  you have

	• petsc-3.4.1.tar.gz - full distribution (including all current patches) with documentation
	• petsc-lite-3.4.1.tar.gz - smaller version with no documentation (all documentation may be accessed on line)
	• The latest stable version can also be downloaded using Git with the following command:

                     git clone -b maint https://bitbucket.org/petsc/petsc petsc

   This is confusing. What does "latest stable version" mean here, under normal git convention it could mean master, but here it does not.

    Can you please rephrase this to say 

      petsc-3.4.1 with additional fixes that have not yet been been included in a patch release can be downloaded ….

     And how about generating a maint tarball each night? Then users can get PETSc 3.4 with all current fixes directly without needing git? 

      Philosphically it seems silly that we are putting fixes into maint on a random regular basis but end users don't benefit until someone manually creates a new petsc-3.4.*.tar.gz every couple of weeks. Why doesn't each new fix to maint lead to an automatic new petsc-3.4.*++ tar ball ready for people to use (or at least each night generate a new one). Now people are installing known buggy code for a bunch of days for no good reason.


More information about the petsc-dev mailing list