beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (BEAM-1345) Mark @Experimental and @Internal where needed in user-facing bits of the codebase
Date Thu, 11 May 2017 18:41:04 GMT


ASF GitHub Bot commented on BEAM-1345:

GitHub user sb2nov opened a pull request:

    [BEAM-1345] Mark windowed value as experimental

    Be sure to do all of the following to help us incorporate your contribution
    quickly and easily:
     - [ ] Make sure the PR title is formatted like:
       `[BEAM-<Jira issue #>] Description of pull request`
     - [ ] Make sure tests pass via `mvn clean verify`.
     - [ ] Replace `<Jira issue #>` in the title with the actual Jira issue
           number, if there is one.
     - [ ] If this contribution is large, please file an Apache
           [Individual Contributor License Agreement](
    R: @aaltay PTAL

You can merge this pull request into a Git repository by running:

    $ git pull BEAM-1345-mark-windowed-value-experimental

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #3087
commit 45775726f30905b2fbc99c13f82dc1bfc1ffd750
Author: Sourabh Bajaj <>
Date:   2017-05-11T18:38:46Z

    [BEAM-1345] Mark windowed value as experimental


> Mark @Experimental and @Internal where needed in user-facing bits of the codebase
> ---------------------------------------------------------------------------------
>                 Key: BEAM-1345
>                 URL:
>             Project: Beam
>          Issue Type: Improvement
>          Components: sdk-java-core, sdk-java-extensions, sdk-java-gcp
>            Reporter: Kenneth Knowles
>              Labels: backward-incompatible
>             Fix For: 2.0.0
> A blanket JIRA to ensure that before a stable release we make sure to mark those pieces
that would be unwise to freeze yet and consider how best to communicate this to users, who
may just autocomplete those features in their IDE anyhow. (conversely, put infrastructure
in place to enforce freezing of the rest)
> Not technically "backwards incompatible" with pre-Beam Dataflow SDKs, but certainly needs
to be on the burndown for the first stable release.

This message was sent by Atlassian JIRA

View raw message