[petsc-dev] plans for PETSc release

[Jed Brown]

Barry Smith <bsmith at mcs.anl.gov> writes:
>    Is it really crucial that all the packages that depend on PETSc
>    have to make their releases exactly when PETSc makes a release?

Definitely not.  They make releases when it works for them, or not (some
projects don't make releases).  The point is that they have a chance to
test their development branch with PETSc's RC (i.e., 'master' during
feature freeze).  Yeah, they could test any time, but if new features
that they don't know/care about are continually coming into PETSc, there
is no motivation to test now versus next week or next month.  And I
realize most probably won't pay attention, but I think the odds of
checking an RC is much higher for people that have contributed to PETSc.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 818 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20160424/bd0b6b36/attachment.sig>