[
https://issues.apache.org/jira/browse/NIFI-13931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892648#comment-17892648
]
David Handermann commented on NIFI-13931:
-----------------------------------------
Thanks again for raising this question [~szaszm].
On further consideration, I added a RewriteRule on the website project, and
submitted PR 9447 to update the README.md to use `nifi-latest` instead of the
particular version number.
> Links in the README of the source package point to 2.0.0-M4 instead of 2.0.0
> ----------------------------------------------------------------------------
>
> Key: NIFI-13931
> URL: https://issues.apache.org/jira/browse/NIFI-13931
> Project: Apache NiFi
> Issue Type: Bug
> Reporter: Marton Szasz
> Assignee: David Handermann
> Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In the Getting Started section, current links have the "nifi-2.0.0-M4"
> version in their URL. The same version in the URL made it to the 2.0.0-RC1
> source package, but I think that should point to the 2.0.0 version docs, even
> if the doc links for that version are not yet deployed and available on the
> website during the RC vote.
>
> Ideally the source package generation script would replace all occurrences of
> the old version with the next one, and we could ignore the not-yet-working
> link during the RC review and voting. But manually changing it before
> packaging works too.
>
> I believe this is related to NIFI-13909
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
