This is an automated email from the ASF dual-hosted git repository.
danhaywood pushed a change to branch release-4.0.0-M1-RC1
in repository https://gitbox.apache.org/repos/asf/causeway.git
discard b5720eb6a70 further fixes to release procedure
discard c7d9662e078 fixes (?) verify script
discard b2999e8065f updating release verification process docs
discard d0383d26f9e CAUSEWAY-3898: updates release procedure docs
discard 1fba7258cec CAUSEWAY-3898: resetting version
new 433f33ad7cd adds gpg plugin to bom/pom.xml
new c902e3657ca CAUSEWAY-3898: resetting version
new ce7a4d35259 CAUSEWAY-3898: updates release procedure docs
new c8d5001d156 updating release verification process docs
new fda3eb6a3e7 fixes (?) verify script
new a1ba656219a further fixes to release procedure
new b1c88e0656a minor update to release procedure
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (b5720eb6a70)
\
N -- N -- N refs/heads/release-4.0.0-M1-RC1 (b1c88e0656a)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
The 7 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
.../modules/ROOT/pages/post-release-successful.adoc | 2 +-
bom/pom.xml | 18 ++++++++++++++++++
2 files changed, 19 insertions(+), 1 deletion(-)
