Stream: Mirror: Isabelle Development Mailing List

Topic: Fork of isabelle-dev vs. isabelle-release


view this post on Zulip Email Gateway (Nov 28 2025 at 17:18):

From: Makarius <makarius@sketis.net>

As already explained on the mail thread "Towards Isabelle2025-1-RC3 and AFP
release", the fork of isabelle-dev vs. isabelle-release has happened 2 days ago:

changeset: 83654:52cd371a36dd
user: wenzelm
date: Wed Nov 26 20:00:47 2025 +0100
files: Admin/Mercurial/mercurial-6.1.4-hgweb.patch
description:
adhoc patch for hgweb.wsgi: provide "hg clone" via HTTP without suffering from
Denial-of-Service attacks on website content (e.g. by Non-Intelligent Agents);

This means:

- pushes to isabelle-dev after that change are for the next release,
presumably something like "Isabelle2026 (October 2026)"

- until afp-devel becomes afp-2025-1 next week, changes on isabelle-dev
must not break AFP

- changes that really need to be on the current release need to be sent to
me via email (using "hg export" or "hg bundle"), and not pushed onto
isabelle-dev at the same time (that produces ugly clones in the history that
are difficult to discern later on)

- the release process continues here:
https://isabelle.sketis.net/repos/isabelle-release -- that is only the
"wireprotocol" for "hg clone" or "hg pull", not a web interface anymore.

Makarius

view this post on Zulip Email Gateway (Oct 03 2026 at 10:24):

From: Makarius <makarius@sketis.net>

According to plan https://sketis.net/2025/plan-for-isabelle2026-october-2026
we now have the fork of isabelle-dev vs. isabelle-release:

changeset: 85764:e2ccfaa6754e
user: wenzelm
date: Sat Oct 03 11:59:48 2026 +0200
files: ANNOUNCE CONTRIBUTORS
description:
misc tuning for release;

This means:

- pushes to isabelle-dev after that change are for the next release, after
current Isabelle2026 (October 2026)

- until afp-devel becomes afp-2026 rather soon, changes on isabelle-dev
must not break AFP

- changes that really need to be on the current release must be sent to me
via email (using "hg export" or "hg bundle"), and not pushed onto
isabelle-dev at the same time

- the release process continues here:
https://isabelle.sketis.net/repos/isabelle-release -- that is only the
"wireprotocol" for "hg clone" or "hg pull", no web interface.

The next release candidate is scheduled for Mon 05-Oct-2026, then based on the
isabelle-release repository. We still need to sort out various technical
questions.

Makarius

view this post on Zulip Email Gateway (Oct 05 2026 at 06:32):

From: Gerwin Klein <gerwin.klein@proofcraft.systems>

The afp-2026 fork has now happened.

Development and testing on afp-devel can continue as before with respect to Isabelle development repo.

Cheers,
Gerwin

On 3 Oct 2026, at 20:24, Makarius <makarius@sketis.net> wrote:

According to plan https://sketis.net/2025/plan-for-isabelle2026-october-2026 we now have the fork of isabelle-dev vs. isabelle-release:

changeset: 85764:e2ccfaa6754e
user: wenzelm
date: Sat Oct 03 11:59:48 2026 +0200
files: ANNOUNCE CONTRIBUTORS
description:
misc tuning for release;

This means:

- pushes to isabelle-dev after that change are for the next release, after current Isabelle2026 (October 2026)

- until afp-devel becomes afp-2026 rather soon, changes on isabelle-dev must not break AFP

- changes that really need to be on the current release must be sent to me via email (using "hg export" or "hg bundle"), and not pushed onto isabelle-dev at the same time

- the release process continues here: https://isabelle.sketis.net/repos/isabelle-release -- that is only the "wireprotocol" for "hg clone" or "hg pull", no web interface.

The next release candidate is scheduled for Mon 05-Oct-2026, then based on the isabelle-release repository. We still need to sort out various technical questions.

Makarius


Last updated: Oct 05 2026 at 16:54 UTC