[petsc-dev] PetscObjectIsNull()

[Pierre Jolivet]

> On 31 Jul 2024, at 6:59 AM, Adrian Croucher <a.croucher at auckland.ac.nz> wrote:
> 
> This Message Is From an External Sender
> This message came from outside your organization.
> 
> 
> On 31/07/24 4:47 pm, Satish Balay wrote:
>> 
>> Major releases [i.e. 3.21.0, 3.22.0 etc.]  are spun from main branch once every 6 months.
>> And bug fix updates [i.e. 3.21.1, 3.21.2 etc.] are spun from release branch once every month [during this 6 month cycle].
>> 
>> i.e PetscObjectIsNull() change that's currently in main branch won't be in a tarball (or a tagged version) until 3.22.0 release in Sept end.
> I guess I'm still a bit confused by your system. What exactly is e.g. the recent commit with tag "3.21.4", if it isn't a "tagged version”?
> 
Did someone said it wasn’t?
> That tag appears to be on the "release" branch as well as "main" - i.e. I can see it if I look at the commits for the "release" branch. So it looked to me like a minor release. How are users supposed to interpret those tags?
> 
One could interpret those as available tarballs.
What you want, PetscObjectIsNull(), is in no tagged release, so you need the “main” branch.
Obviously, I’m just restating what Barry and Satish have been saying, but maybe with a different twist?

Thanks,
Pierre
> - Adrian
> 
> -- 
> Dr Adrian Croucher
> Senior Research Fellow
> Department of Engineering Science
> Waipapa Taumata Rau / University of Auckland, New Zealand
> email: a.croucher at auckland.ac.nz <mailto:a.croucher at auckland.ac.nz>
> tel: +64 (0)9 923 4611

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20240731/313661eb/attachment-0001.html>