Github user revans2 commented on the pull request:
https://github.com/apache/storm/pull/736#issuecomment-143232892
@ptgoetz
What exactly is the release process? I don't see it documented anywhere?
Our internally release process is mostly.
```
mvn -Pstorm-core,storm-more versions:set -DnewVersion=${NEW_VERSION}
mvn -Pstorm-core,storm-more versions:update-child-modules
mvn -Pnative -Pstorm-core -Dworker-launcher.conf.dir=${EXEC_CONF_DIR}
install
mvn -Pstorm-more install
```
we typically will package thins a little differently here because we don't
use the .tgz or .zip directly but the following works fine.
```
cd storm-dist/binary
mvn clean package
```
We typically don't check in the version changes so revert them with
```
mvn versions:revert
mvn versions:update-child-modules
```
and just tag the base. But checking in the specific version to a new
branch is helpful too.
How exactly are you pushing the finished jars/poms to the maven repository?
Is it really that hard to manually use git manually instead of relying on
the release plugin?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
