You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@avro.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2023/03/13 14:06:00 UTC
[jira] [Commented] (AVRO-3651) [web] Build and separate release-specific pages.
[ https://issues.apache.org/jira/browse/AVRO-3651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17699658#comment-17699658 ]
ASF subversion and git services commented on AVRO-3651:
-------------------------------------------------------
Commit 2eb04ccf4746da808ff00e306056f455e2d27414 in avro's branch refs/heads/avro-3631/fix-fixed-serialization from Rik Heijdens
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=2eb04ccf4 ]
AVRO-3651: Add test to de.rs to illustrate issue with Fixed fields
> [web] Build and separate release-specific pages.
> ------------------------------------------------
>
> Key: AVRO-3651
> URL: https://issues.apache.org/jira/browse/AVRO-3651
> Project: Apache Avro
> Issue Type: Task
> Components: website
> Reporter: Ryan Skraba
> Priority: Major
>
> One of the major complications with the Avro website is maintaining the pages for old version. The website documentation is treated as a release artifact for the release, which makes sense since the pages are contained in the release.
> The Flink community separates the pages that apply to the flink project from the pages that apply to a speciific release. They are integrated together to navigate easily from release 1.x.0 -> project -> release 1.y.0
> This technique would make it quite a bit easier to deploy the website, and allow us to have links to "Edit this page" that can automatically open a PR on GitHub.
> Project: [https://flink.apache.org/]
> Release: [https://nightlies.apache.org/flink/flink-docs-release-1.15/docs/try-flink/local_installation/]
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)