[petsc-dev] removing sieve
Jed Brown writes: > I pushed this on 'knepley/remove-sieve': And a few more fragments (first is required to build). commit 608682ac090728f9d7f752b4b3da057f6f3e683a Author: Jed Brown Date: Sun May 12 16:51:37 2013 -0500 DMMesh: remove from makefile and Fortran modules include/finclude/makefile | 6 +++--- src/dm/f90-mod/petscdmmod.F | 12 src/ts/f90-mod/petsctsmod.F | 2 -- 3 files changed, 3 insertions(+), 17 deletions(-) commit ec1151fb5e6fa85072f9f467062343c41813686e Author: Jed Brown Date: Sun May 12 16:54:21 2013 -0500 DMMesh: remove declaration of SNES callback include/petscsnes.h | 3 --- 1 file changed, 3 deletions(-) commit a05fad5378af7043713a4ef3a27e52e37312bd9b Author: Jed Brown Date: Sun May 12 16:55:02 2013 -0500 DMPlex: remove bad "DMMESH" documentation src/dm/impls/plex/examples/tests/ex3.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
[petsc-dev] release naming scheme
Satish Balay writes: > Right now PETSC_VERSION_PATCH_DATE is automatically set when the > tarball is spun. [And we also have PETSC_VERSION_DATE_GIT - primarily > for configure.log] > > So your suggestion is to remove PETSC_VERSION_PATCH_DATE - and set > PETSC_VERSION_DATE [automatically during tarball creation] Yes, is there a reason not to do this? Having two dates is more complexity and I don't see the benefit. > Also - I see petscnagupgrade.py checks > http://www.mcs.anl.gov/petsc/petsc-dev/include/petscversion.h for > latest release version info. So for the old versions [of petsc > petscnagupgrade.py] to work - we'll have to retain PETSC_VERSION_PATCH > [as you suggested] The commit below is in 'jed/nagupgrade-subminor'. Since 3.4 will increase MINOR, the old script will still ask people to upgrade to 3.4. commit e9b81f52c562140219af174f5ca7d2825fc8b69f Author: Jed Brown Date: Sun May 12 13:20:52 2013 -0500 nagupgrade: check subminor version and use distutils.version Subminor version will be used for maintenance releases starting with the 3.4 series. Version comparison is simpler with distutils.version. > BTW: before switching the scripts to handle the new version naming - I > created petsc-3.3-p7 tarballs with the current outstanding patches in > the maint branch [via balay/maint-3.3-p7 branch]. If its ok - it can > be merged into maint/master. > > ftp://ftp.mcs.anl.gov/pub/petsc/release-snapshots/petsc-3.3-p7.tar.gz > [web page isn't updated though] Sounds good to me.
[petsc-dev] removing sieve
Matthew Knepley writes: >> We can delete the sieve-dev mailing list and reference to it. >> >> src/docs/website/miscellaneous/mailing-lists.html: : For >> Sieve users I pushed this on 'knepley/remove-sieve': commit 5ddce99b6248cc49505df26585a376cb69f2d661 Author: Jed Brown Date: Sun May 12 11:49:03 2013 -0500 Sieve: remove reference to sieve-dev mailing list diff --git a/src/docs/website/miscellaneous/mailing-lists.html b/src/docs/website/miscellaneous/mailing-lists.html index 2510ccb..5b6b136 100644 --- a/src/docs/website/miscellaneous/mailing-lists.html +++ b/src/docs/website/miscellaneous/mailing-lists.html @@ -72,14 +72,6 @@ : http://lists.mcs.anl.gov/pipermail/petsc-dev/";>archives : For petsc-dev users - - - • - sieve-dev at mcs.anl.gov - : https://lists.mcs.anl.gov/mailman/listinfo/sieve-dev";>subscribe/unsubscribe - : http://lists.mcs.anl.gov/pipermail/sieve-dev/";>archives - : For Sieve users - @@ -91,7 +83,7 @@ Notes: petsc-announce is an announcement only list. [i.e users cannot post on this list] -petsc-users, petsc-dev, sieve-dev are subscriber-only lists. [i.e to post to this list - you have to subscribe first] +petsc-users and petsc-dev are subscriber-only lists. [i.e to post to this list - you have to subscribe first] the lists have limits on message sizes - so if you have to send in > Satish, how do I delete this? You are the list administrator, but it may take asking systems to get it completely deleted. May as well leave the archives, though I don't recall any significant discussion taking place there. https://lists.mcs.anl.gov/mailman/admin/sieve-dev
[petsc-dev] removing sieve
On Sat, May 11, 2013 at 6:18 PM, Jed Brown wrote: > Matt, I take it that you intend for this removal to be merged for > petsc-3.4 so that users are not distracted by something we aren't > supporting. An alternative would be to add a #warning to petscdmmesh.h. > > If we are deleting it from petsc-3.4, there are a few files that can > have more stuff deleted: > > $ git grep -l 'ALE::' > bin/processSummary.py > Removed. > config/PETSc/FEM.py > This will be removed when we finish moving FIAT to DMDT. > src/dm/impls/plex/plexfem.c > This is code that needs to be rewritten. > src/docs/doxygen/Doxyfile > Fixed > src/snes/examples/tutorials/ex72.c > Fixed. > We can delete the sieve-dev mailing list and reference to it. > > src/docs/website/miscellaneous/mailing-lists.html: : For > Sieve users > Satish, how do I delete this? > Update the FAQ to recommend DMPlex. > > src/docs/website/documentation/faq.html: use the Sieve construct > in PETSc, this is a high > Fixed > Remove src/docs/tex/manual/sieve.tex > Done. > Sieve is also referenced from src/docs/strategy.tex, which is an > outdated personal fragment that should probably also be deleted. > Removed. Matt -- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener -- next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20130512/0bc30087/attachment.html>
[petsc-dev] release naming scheme
On Sat, 11 May 2013, Jed Brown wrote: > Satish Balay writes: > > >> What is the utility of PETSC_VERSION_PATCH_DATE? > > > > In the current scheme we have: [for each petsc-3.3-pX tarball] > > > > PETSC_VERSION_DATE: date of the primary release [i.e when the first 3.3 > > tarball was spun] > > PETSC_VERSION_PATCH_DATE: date of the patched tarball release [i.e when > > 3.3-pX was spun] > > > > And we use PETSC_VERSION_DATE [manually transcribed] in a bunch of > > places. > > > > - https://www.mcs.anl.gov/petsc/ > > "The current version of PETSc is 3.3; released June 5, 2012" > > > > - https://www.mcs.anl.gov/petsc/documentation/changes/index.html > > > > - manual > > > > But PETSC_VERSION_PATCH_DATE: is the date the tarball is respun [with > > patches] - and that doesn't change the above docs. > > How is this information useful? Would it be simple enough to "release" > the manual once per feature release (3.4, 3.5, ...) so that it's date > would not need to be updated every maintenance (subminor) release and > then PETSC_VERSION_DATE would always reflect the date of the last > release? > > We could stop hard-coding these values and switch to obtaining them from > Git, in which case releasing would just involve tagging and spinning the > tarballs, but that automation can wait. Right now PETSC_VERSION_PATCH_DATE is automatically set when the tarball is spun. [And we also have PETSC_VERSION_DATE_GIT - primarily for configure.log] So your suggestion is to remove PETSC_VERSION_PATCH_DATE - and set PETSC_VERSION_DATE [automatically during tarball creation] Also - I see petscnagupgrade.py checks http://www.mcs.anl.gov/petsc/petsc-dev/include/petscversion.h for latest release version info. So for the old versions [of petsc petscnagupgrade.py] to work - we'll have to retain PETSC_VERSION_PATCH [as you suggested] BTW: before switching the scripts to handle the new version naming - I created petsc-3.3-p7 tarballs with the current outstanding patches in the maint branch [via balay/maint-3.3-p7 branch]. If its ok - it can be merged into maint/master. ftp://ftp.mcs.anl.gov/pub/petsc/release-snapshots/petsc-3.3-p7.tar.gz [web page isn't updated though] Satish
[petsc-dev] removing sieve
Great. Thanks a lot. The timeline should be fine. Blaise Sent from a handheld device. On May 11, 2013, at 8:17 PM, "Jed Brown" mailto:jedbrown at mcs.anl.gov>> wrote: Matt and I just talked offline. We'll leave it in for the release, but remove it from master. So it will be in 3.4.x (deprecated), but not in 'master' and gone in 3.5. On May 11, 2013 7:57 PM, "Blaise A Bourdin" mailto:bourdin at lsu.edu>> wrote: Can we keep it in 3.4 with a warning? I have a lot more work to do before I can switch to dmplex. Blaise On May 11, 2013, at 6:18 PM, Jed Brown mailto:jedbrown at mcs.anl.gov>> wrote: > Matt, I take it that you intend for this removal to be merged for > petsc-3.4 so that users are not distracted by something we aren't > supporting. An alternative would be to add a #warning to petscdmmesh.h. > > If we are deleting it from petsc-3.4, there are a few files that can > have more stuff deleted: > > $ git grep -l 'ALE::' > bin/processSummary.py > config/PETSc/FEM.py > src/dm/impls/plex/plexfem.c > src/docs/doxygen/Doxyfile > src/snes/examples/tutorials/ex72.c > > > We can delete the sieve-dev mailing list and reference to it. > > src/docs/website/miscellaneous/mailing-lists.html: : For Sieve > users > > > Update the FAQ to recommend DMPlex. > > src/docs/website/documentation/faq.html: use the Sieve construct in > PETSc, this is a high > > Remove src/docs/tex/manual/sieve.tex > > > Sieve is also referenced from src/docs/strategy.tex, which is an > outdated personal fragment that should probably also be deleted. > -- Department of Mathematics and Center for Computation & Technology Louisiana State University, Baton Rouge, LA 70803, USA Tel. +1 (225) 578 1612, Fax +1 (225) 578 4276 http://www.math.lsu.edu/~bourdin -- next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20130512/23cad694/attachment.html>
[petsc-dev] removing sieve
Can we keep it in 3.4 with a warning? I have a lot more work to do before I can switch to dmplex. Blaise On May 11, 2013, at 6:18 PM, Jed Brown wrote: > Matt, I take it that you intend for this removal to be merged for > petsc-3.4 so that users are not distracted by something we aren't > supporting. An alternative would be to add a #warning to petscdmmesh.h. > > If we are deleting it from petsc-3.4, there are a few files that can > have more stuff deleted: > > $ git grep -l 'ALE::' > > bin/processSummary.py > config/PETSc/FEM.py > src/dm/impls/plex/plexfem.c > src/docs/doxygen/Doxyfile > src/snes/examples/tutorials/ex72.c > > > We can delete the sieve-dev mailing list and reference to it. > > src/docs/website/miscellaneous/mailing-lists.html: : For Sieve > users > > > Update the FAQ to recommend DMPlex. > > src/docs/website/documentation/faq.html: use the Sieve construct in > PETSc, this is a high > > Remove src/docs/tex/manual/sieve.tex > > > Sieve is also referenced from src/docs/strategy.tex, which is an > outdated personal fragment that should probably also be deleted. > -- Department of Mathematics and Center for Computation & Technology Louisiana State University, Baton Rouge, LA 70803, USA Tel. +1 (225) 578 1612, Fax +1 (225) 578 4276 http://www.math.lsu.edu/~bourdin
