[
https://issues.apache.org/jira/browse/BEAM-9219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Wrede updated BEAM-9219:
------------------------------
Description:
This issue is about the need to address keeping both Python and Java SDK
dependency pages more relevant and up-to-date while reducing the amount of time
it takes to provide that information. The current method of scraping and
copying dependencies into a table for every release is a non-trivial task
because of the semi-automated workflows done by the tech writers on the website.
In an effort to provide accurate dependency listings that are always in sync
with SDK releases, referring people to the appropriate places in the source
code (or through CLI commands) should provide people the information they are
looking for and not require the creation and maintenance of an automated
tooling solution to generate the dependency tables.
was:
This issue is about the need to address keeping both Python and Java SDK
dependency pages more relevant and up-to-date while reducing the amount of time
it takes to provide that information. The current method of scraping and
copying dependencies into a table for every release is a non-trivial task
because of some semi-automated workflows done by the tech writers on the
website.
In an effort to provide accurate dependency listings that are always in sync
with SDK releases, referring people to the appropriate places in the source
code (or through CLI commands).
> Streamline creation of Python and Java dependencies pages
> ---------------------------------------------------------
>
> Key: BEAM-9219
> URL: https://issues.apache.org/jira/browse/BEAM-9219
> Project: Beam
> Issue Type: Improvement
> Components: website
> Reporter: David Wrede
> Priority: Minor
>
> This issue is about the need to address keeping both Python and Java SDK
> dependency pages more relevant and up-to-date while reducing the amount of
> time it takes to provide that information. The current method of scraping and
> copying dependencies into a table for every release is a non-trivial task
> because of the semi-automated workflows done by the tech writers on the
> website.
> In an effort to provide accurate dependency listings that are always in sync
> with SDK releases, referring people to the appropriate places in the source
> code (or through CLI commands) should provide people the information they are
> looking for and not require the creation and maintenance of an automated
> tooling solution to generate the dependency tables.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
