[
https://issues.apache.org/jira/browse/NIFI-13931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892646#comment-17892646
]
David Handermann commented on NIFI-13931:
-----------------------------------------
Thanks for noting this [~szaszm].
Part of the general release process includes publishing the documentation. The
current website configuration forwards old versions to current versions, and
that would address the direct problem.
Going forward, we should look at a different approach that uses something like
a "latest" directory.
With that background, I think we can update these links after the release, and
also improvement the website link layout so we don't need to update for every
release version.
> 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
> Affects Versions: 2.0.0-M4
> Reporter: Marton Szasz
> Priority: Minor
>
> 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)
