> On Jun 28, 2017, at 4:01 PM, Jungtaek Lim <kabh...@gmail.com> wrote: > > If my memory is right, when releasing 1.1.0 we postponed resolving some > critical issues for storm-kafka-client, and seems like it still haven't > been sorted out. I even think these issues can be effectively blocker for > 1.1.1 if we want to treat this module as stable. > > So in fact and ideally, it should've been marked as experimental or beta > until it has no more critical issue, and I feel it's still in beta phase.
+1 IIRC, I think we had one issue opened during the voting phase when we released 1.1.0, and it has since snowballed somewhat. For a 1.1.1 release I think we need to make sure it is solid, and if not, retroactively give it a beta/experimental/etc. label in the release announcement. -Taylor
