The API reference docs (Java and Python at least) are versioned, so we have a durable reference there and it's possible to link to particular sections of API docs for particular versions.
For the major bits of introductory documentation (like the Beam Programming Guide), I think it's a good thing to have only a single version, so that people referencing it are always getting the most up-to-date wording and explanations, although it may be worth adding callouts there about minimum versions anywhere we discuss newer features. We should be encouraging the community to stay reasonably current, so I think any feature that's present in the latest LTS release should be fine to assume is available to users, although perhaps we should also state that explicitly on the website. Are there particular parts of the Beam website that you have in mind that would benefit from versioning? Are there specific cases you see where the current website would be confusing for someone using a Beam SDK that's a few versions old? On Tue, Dec 3, 2019 at 6:46 PM Ankur Goenka <goe...@google.com> wrote: > Hi, > > We are constantly adding features to Beam which makes each new Beam > version more feature rich and compelling. > This also means that the old Beam released don't have the new features and > might have different ways to do certain things. > > (I might be wrong here) - Our Beam website only publish a single version > which is the latest version of documentation. > This means that the users working with older SDK don't really have an easy > way to lookup documentation for old versions of Beam. > > Proposal: Shall we consider publishing versioned Beam website to help > users with old Beam version find the relevant information? > > Thanks, > Ankur >
