[
https://issues.apache.org/jira/browse/BEAM-9219?focusedWorklogId=381140&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-381140
]
ASF GitHub Bot logged work on BEAM-9219:
----------------------------------------
Author: ASF GitHub Bot
Created on: 03/Feb/20 18:54
Start Date: 03/Feb/20 18:54
Worklog Time Spent: 10m
Work Description: rosetn commented on issue #10745: [BEAM-9219]
Streamline creation of Python and Java dependencies pages
URL: https://github.com/apache/beam/pull/10745#issuecomment-581562131
> > Should we keep the old information in the same page for previous
releases? Removing might be a regression for existing users. We could hide in a
collapsed box maybe?
>
> I worry that keeping these tables will lead to the expectation that we'll
create more tables. Based on the feedback of the Java deps page, it seems to be
confusing to just have tables for some of the old versions.
I agree with Cyrus. If it's the same process to access the old information
as listed here, it's confusing to stop at an old version and might make this
page look stale.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 381140)
Time Spent: 1h (was: 50m)
> 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
> Time Spent: 1h
> Remaining Estimate: 0h
>
> 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)
