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 24bfa6c7769 updating release verification process docs
discard 946f3108028 CAUSEWAY-3898: updates release procedure docs
discard d44742c24a9 CAUSEWAY-3898: resetting version
new 2ecaab7a1d5 adds source plugin to top-level aggregator
new 9af80f59e7a changes source-plugin to use a different goal
new fd07d6bf5da removes the 'dont deploy the aggregator' property;
new 16212c14f8b CAUSEWAY-3898: resetting version
new 1a8c18fcb49 CAUSEWAY-3898: updates release procedure docs
new d6b4f49c43b updating release verification process docs
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 (24bfa6c7769)
\
N -- N -- N refs/heads/release-4.0.0-M1-RC1 (d6b4f49c43b)
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 6 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:
pom.xml | 14 ++++++++++++--
1 file changed, 12 insertions(+), 2 deletions(-)
