Satish Balay via petsc-dev <[email protected]> writes: > On Wed, 31 Mar 2021, Lisandro Dalcin wrote: > >> On Wed, 31 Mar 2021 at 18:07, Satish Balay <[email protected]> wrote: >> >> > And we just use 2 level workflow, and have branches for each of the >> > 'releases' [as we move from one to the other] >> > >> >> Maybe I'm not making myself clear. >> What I find a bit awkward is that I can define >> >> x=3 >> y=15 >> z=0 >> >> and then do: >> >> wget >> https://ftp.mcs.anl.gov/pub/petsc/release-snapshots/petsc-$x.$y.$z.tar.gz >> tar zxf petsc-$x.$y.$z.tar.gz >> cd petsc-$x.$y.$z >> ... >> >> But I cannot do >> >> git clone ... >> git checkout v$x.$y.$z >> >> because there is no tag v3.15.0, just v3.15 > > I agree - the current usage causes this problem. > > I vote for switching over to v3.15.0 [or add both tags v3.15.0 and > v3.15 - to not break things for 'v3.15' usage - assuming 2 tags wont' > cause other issues]
It's okay with me to add v3.15.0 (without removing v3.15) and just tag v3.16.0 in future releases.
