[
https://issues.apache.org/jira/browse/COMDEV-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17688192#comment-17688192
]
Andrew Musselman commented on COMDEV-293:
-----------------------------------------
Is this still relevant, are there people needing it, etc.?
I see it's looking for this pattern `RELEASE_MATCH = r"^release/([^/]+)/" #
match any name followed by /`. Not immediately clear why it's not catching the
path in `A /release/spark/spark-2.2.2 (from /dev/spark/v2.2.2-rc2-bin:27901)`
> scandist does not detect releases renamed from dist/dev
> -------------------------------------------------------
>
> Key: COMDEV-293
> URL: https://issues.apache.org/jira/browse/COMDEV-293
> Project: Community Development
> Issue Type: Bug
> Components: Reporter Tool
> Reporter: Sebb
> Priority: Major
>
> The scandist script ignores commits which only affect a directory.
> This is OK for simple directory creation, but means that releases which are
> created by renaming/copying from dist/dev are ignored.
> For example the following did not cause an email to be sent:
> $ svn log -r27902 -v https://dist.apache.org/repos/dist/
> ------------------------------------------------------------------------
> r27902 | tgraves | 2018-07-03 19:08:54 +0100 (Tue, 03 Jul 2018) | 2 lines
> Changed paths:
> D /dev/spark/v2.2.2-rc2-bin
> A /release/spark/spark-2.2.2 (from /dev/spark/v2.2.2-rc2-bin:27901)
> Publish spark 2.2.2
> ------------------------------------------------------------------------
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org
