Re: JIRA Workflow Proposals

2018-12-12 Thread Ariel Weisberg
Hi, Updating to reflect the new options for 1. 2, 3, and 4 remain unchanged. 1. E, D, C, B, A 2. B, C, A 3. A 4. -.5 Ariel On Tue, Dec 11, 2018, at 10:55 AM, Ariel Weisberg wrote: > Hi, > > Sorry I was just slow on the uptake as to what auto-populate meant RE #2. > > 1. -1, while

Re: Revisit the proposal to use github PR

2018-12-12 Thread Benedict Elliott Smith
Perhaps somebody could summarise the tradeoffs? I’m a little concerned about how it would work for our multi-branch workflow. Would we open multiple PRs? Could we easily link with external CircleCI? It occurs to me, in JIRA proposal mode, that an extra required field for a permalink to

Re: JIRA Workflow Proposals

2018-12-12 Thread jay.zhu...@yahoo.com.INVALID
My two cents: 1. C, D, E, B, A2. A, B, C3. A4. -1 On Wednesday, December 12, 2018, 10:14:25 AM PST, Benedict Elliott Smith wrote: Ok, so feel free to keep your votes coming, but we have a pretty clear majority for everything except Wish - which presently stands at -1 (maybe -2 if

Revisit the proposal to use github PR

2018-12-12 Thread jay.zhu...@yahoo.com.INVALID
It was discussed 1 year's ago:  https://www.mail-archive.com/dev@cassandra.apache.org/msg11810.html As all Apache projects are moving to gitbox:  https://reference.apache.org/committer/github, should we revisit that and change our review/commit process to use github PR?A good example is

Re: cassandra-stress HexStrings generator

2018-12-12 Thread Benedict Elliott Smith
Yes, I’m pretty sure you understood correctly (I wrote most of this, but it’s been a long time so I cannot remember much for certain). It should be implemented like the Strings generator. It looks like both HexStrings and HexBytes are incorrect, and have been for a long time. > On 12 Dec

Re: Revisit the proposal to use github PR

2018-12-12 Thread dinesh.jo...@yahoo.com.INVALID
I've been already using github PRs for some time now. Once you specify the ticket number, the comments and discussion are persisted in Apache Jira as work log so it can be audited if desired. However, committers usually squash and commit the changes once the PR is approved. We don't use the

Re: JIRA Workflow Proposals

2018-12-12 Thread Sylvain Lebresne
On Wed, Dec 12, 2018 at 7:14 PM Benedict Elliott Smith wrote: > Ok, so feel free to keep your votes coming, but we have a pretty clear > majority for everything except Wish - which presently stands at -1 (maybe > -2 if Sylvain updates his vote). > Yes, I did meant -1 on the wish issue if that

Re: JIRA Workflow Proposals

2018-12-12 Thread Sam Tunnicliffe
1: D C B A E 2: B C A 3: A 4: -1 (get rid of Wish entirely) Thanks, Sam > On 11 Dec 2018, at 22:01, Joseph Lynch wrote: > > Just my 2c > > 1. D C B E A > 2. B, C, A > 3. A > 4. +0.5 > > -Joey > > On Tue, Dec 11, 2018 at 8:28 AM Benedict Elliott Smith > wrote: > >> Just to re-summarise

Re: JIRA Workflow Proposals

2018-12-12 Thread Marcus Eriksson
1. D C B A E 2. B C A 3. A 4. -0.5, leaning towards remove but don't really care On Tue, Dec 11, 2018 at 06:42:09PM +, Aleksey Yeshchenko wrote: > 1. C, D, A, B, E > 2. B, C, A > 3. A > 4. Meh > > > On 11 Dec 2018, at 16:28, Benedict Elliott Smith > > wrote: > > > > Just to re-summarise