Sounds good. I’ll prepare a release candidate and as I mentioned in another
thread use the opportunity to document the release process.
-Taylor
> On Jan 27, 2017, at 10:41 AM, Bobby Evans wrote:
>
> I am +1 on a release of 1.0.3
>
>
> - Bobby
>
> On Wednesday,
I am +1 on a release of 1.0.3
- Bobby
On Wednesday, January 25, 2017, 4:25:06 AM CST, Jungtaek Lim
wrote:Bump. Any other opinions? I got two non-binding +1
but also would like to
see PMCs opinions.
And I also would like to volunteer the release manager on this version.
Github user jnioche commented on the issue:
https://github.com/apache/storm/pull/1896
See issue with #1900 - closing for now
---
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
Github user jnioche closed the pull request at:
https://github.com/apache/storm/pull/1896
---
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
Github user jnioche commented on the issue:
https://github.com/apache/storm/pull/1900
Needs more work. I am getting the following in supervisor.log
```
2017-01-27 11:45:55.788 Thread-12 o.a.s.u.Utils [INFO] Worker Process
9318e633-f5fc-476f-825c-2f68a21163fd:Exception in
Github user jnioche closed the pull request at:
https://github.com/apache/storm/pull/1900
---
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
GitHub user jnioche opened a pull request:
https://github.com/apache/storm/pull/1900
Port STORM-2326 Upgrade log4j and slf4j to branch 1.0.x
See #1896
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jnioche/storm STORM-2326-2