Do you plan to be doing significant development on both the v1 and v2 branches, and if so, for how long? I have been bitten badly by that pattern in the past. Developers put lots of unrelated, destabilizing changes into v2, it look longer than expected to stabilize v2, product management lost confidence in v2 and shifted resources back to v1, and v2 never caught up with v1.
One important question: Which branch will you ask people to target for pull requests? v1, v2 or both? If they submit to v2, and v2 is broken, how will you know whether the patches are good? My recommendation is to choose one of the following: (1) put a strict time limit of say 2 months after which v2 would become the master branch (and v1 master would become a maintenance branch), or (2) make v2 focused on a particular architectural feature; create multiple independent feature branches with breaking API changes if you need to. Julian > On Mar 26, 2016, at 1:41 PM, Paul Rogers <[email protected]> wrote: > > Hi All, > > 2.0 is a good opportunity to enhance our ZK information. See DRILL-4543: > Advertise Drill-bit ports, status, capabilities in ZooKeeper. This change > will simplify YARN integration. > > This enhancement will change the “public API” in ZK. To Parth’s point, we can > do so in a way that old clients work - as long as a Drill-bit uses default > ports. > > I’ve marked this JIRA as a candidate for 2.0. > > Thanks, > > - Paul > >> On Mar 24, 2016, at 4:11 PM, Parth Chandra <[email protected]> wrote: >> >> What's our proposal for backward compatibility between 1.x and 2.x? >> My thoughts: >> Optional - Allow a mixture of 1.x and 2.x drillbits in a cluster. >> Required - 1.x clients should be able to talk to 2.x drillbits. >> >> >> >> On Thu, Mar 24, 2016 at 8:55 AM, Jacques Nadeau <[email protected]> wrote: >> >>> There are some changes that either have reviews pending or are in progress >>> that would require breaking changes to Drill core. >>> >>> Examples Include: >>> DRILL-4455 (arrow integration) >>> DRILL-4417 (jdbc/odbc/rpc changes) >>> DRILL-4534 (improve null performance) >>> >>> I've created a new 2.0.0 release version in JIRA and moved these tasks to >>> that umbrella. >>> >>> I'd like to propose a new v2 release branch where we can start >>> incorporating these changes without disrupting v1 stability and >>> compatibility. >>> >>> >>> -- >>> Jacques Nadeau >>> CTO and Co-Founder, Dremio >>> >
