[petsc-dev] PTScotch 6

[Jed Brown]

On Tue, Mar 19, 2013 at 11:20 AM, Satish Balay <balay at mcs.anl.gov> wrote:

> I don't understand this. you mean 'master' at the end? So you mean:
> - create a 'patch' branch off 'maint' and apply this patch.
>

yes


> - merge this 'patch' branch to 'maint'
> - merge this 'patch' branch to 'next'
>

Merge 'patch' into 'next' first so that it can be tested before going to
more stable branches.


> Sorry - I meant to say 'it has merges from 3.2' - so I'm not sure how
> eqivalent it is to previous 3.3-petsc+3.3-bs - and if we should generate
> patch updates for 3.3 from this or not.
>

Yes, it's basically the same, except for 'patch' branches being able to go
spend time in 'next' before 'patch' appears in 'maint', as above. We'll
make maintenance releases from 'maint'.



Also, I would prefer to name maintenance releases 3.4.X instead of 3.4pX so
that version comparison macros can be used. Sometimes PETSc fixes a bug in
a maintenance release and other applications do not have a nice way to test
for that. Subminor release numbers conventionally mean "source- and
binary-compatible", so I don't see any value in  3.4pX numbering.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20130319/85805b78/attachment.html>