+1 (binding)
- verified release signature and hashes
- verified LICENSE, NOTICE, README.md and CHANGELOG.md are present
- no unexpected binary files in the source distribution
- verified build and tests run clean "mvn clean apache-rat:check verify
-Dlicense.skip=false install"
Thank you,
Vlad
GitHub user PramodSSImmaneni opened a pull request:
https://github.com/apache/apex-core/pull/522
APEXCORE-714 Adding a new recovery mode where the operator instance before
a failure event can be reused when recovering from an upstream operator failure
[Review Only]
You can merge
[
https://issues.apache.org/jira/browse/APEXCORE-714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15991331#comment-15991331
]
ASF GitHub Bot commented on APEXCORE-714:
-
GitHub user PramodSSImmaneni opened a
Dear Community,
Please vote on the following Apache Apex Core 3.6.0 release candidate 1.
This release adds the support for custom control tuples, experimental
support for plugins
and other improvements and important bug fixes.
This is a source release with binary artifacts published to Maven.
L
-->
> The remote 3.6.0 branch stays at 3.6.0-SNAPSHOT until release is complete.
> > The tag has the release version.
> >
> >
> There is no step to push release branch to remote while being at
> 3.6.0-SNAPSHOT. Is this step missing from release document?
>
>
Earlier, it would have been sufficient
On Sat, Apr 29, 2017 at 2:16 AM, Thomas Weise wrote:
> The remote 3.6.0 branch stays at 3.6.0-SNAPSHOT until release is complete.
> The tag has the release version.
>
>
There is no step to push release branch to remote while being at
3.6.0-SNAPSHOT. Is this step missing from release document?
