zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From anmolnar <...@git.apache.org>
Subject [GitHub] zookeeper issue #184: ZOOKEEPER-236: SSL Support for Atomic Broadcast protoc...
Date Mon, 17 Sep 2018 13:14:10 GMT
Github user anmolnar commented on the issue:

    https://github.com/apache/zookeeper/pull/184
  
    Additionally I've noticed that you haven't created a separate Jira for #621 which makes
the administration of these issues quite cumbersome. 
    
    I think the following would be feasible and might be acceptable for everybody:
    - Get this patch in and leave `portUnification=false` by default. It might be good to
add a note in the docs that port unification is experimental and we have a jira to fix it,
    - Create separate jira for fixing port unification,
    - Create another jira if needed for other improvements and fixes.
    - Release 3.5 whatever gets in, but don't mark the new tickets as blockers.
    
    I think it's fine if there're known issues in the stable release as long as they don't
impact the core functionality and turned off by default. For instance, we have a ticket for
TTL nodes as well, but that's not a blocker either.
    
    Thoughts?


---

Mime
View raw message