Re: [VOTE] Apache Cassandra Release Lifecycle
What exactly will be the implication of the outcome of this vote, in case the content is agreed upon? What's the proposal of the voting? The document seems to be informative rather then formal. It's verbose on definitions that should be commonly understood or can only broadly defined (what is alpha/beta/RC, GA for production, etc.), while at the same time is unclear and weasel-wordy on our actual commitment and rules. On 30.09.19 20:51, sankalp kohli wrote: Hi, We have discussed in the email thread[1] about Apache Cassandra Release Lifecycle. We came up with a doc[2] for it. Please vote on it if you agree with the content of the doc[2]. Thanks, Sankalp [1] https://lists.apache.org/thread.html/c610b23f9002978636b66d09f0e0481ed3de9b78895050da22c91c6f@%3Cdev.cassandra.apache.org%3E [2] https://docs.google.com/document/d/1bS6sr-HSrHFjZb0welife6Qx7u3ZDgRiAoENMLYlfz8/edit#heading=h.633eppni91tw - To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
Re: [DISCUSS] C* track for ApacheCon 2020 (was: ApacheCon North America 2020, project participation)
Completely agree, we should absolutely do it. On Tue, Oct 1, 2019 at 12:27 PM Nate McCall wrote: > [Moved to C* only thread] > > We got a lot of feedback from folks after this year's track. I'm keen to do > this again. At this point I think we are just looking at saying "yes we > would like to participate" and all details about tracks, etc. will be TBD. > > Thoughts? > > -Nate > > -- Forwarded message - > From: Rich Bowen > Date: Wed, Oct 2, 2019 at 5:36 AM > Subject: ApacheCon North America 2020, project participation > To: plann...@apachecon.com > > > Hi, folks, > > (Note: You're receiving this email because you're on the dev@ list for > one or more Apache Software Foundation projects.) > > For ApacheCon North America 2019, we asked projects to participate in > the creation of project/topic specific tracks. This was very successful, > with about 15 projects stepping up to curate the content for their > track/summit/event. > > We need to know if you're going to do the same for 2020. This informs > how large a venue we book for the event, how long the event runs, and > many other considerations. > > If you intend to participate again in 2020, we need to hear from you on > the plann...@apachecon.com mailing list. This is not a firm commitment, > but we need to know if you're, say, 75% confident that you'll be > participating. > > And, no, we do not have any details at all, but assume that it will be > in roughly the same calendar space as this year's event, ie, somewhere > in the August-October timeframe. > > Thanks. > > -- > Rich Bowen > VP Conferences > The Apache Software Foundation > @apachecon > > - > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > For additional commands, e-mail: dev-h...@cassandra.apache.org >
[DISCUSS] C* track for ApacheCon 2020 (was: ApacheCon North America 2020, project participation)
[Moved to C* only thread] We got a lot of feedback from folks after this year's track. I'm keen to do this again. At this point I think we are just looking at saying "yes we would like to participate" and all details about tracks, etc. will be TBD. Thoughts? -Nate -- Forwarded message - From: Rich Bowen Date: Wed, Oct 2, 2019 at 5:36 AM Subject: ApacheCon North America 2020, project participation To: plann...@apachecon.com Hi, folks, (Note: You're receiving this email because you're on the dev@ list for one or more Apache Software Foundation projects.) For ApacheCon North America 2019, we asked projects to participate in the creation of project/topic specific tracks. This was very successful, with about 15 projects stepping up to curate the content for their track/summit/event. We need to know if you're going to do the same for 2020. This informs how large a venue we book for the event, how long the event runs, and many other considerations. If you intend to participate again in 2020, we need to hear from you on the plann...@apachecon.com mailing list. This is not a firm commitment, but we need to know if you're, say, 75% confident that you'll be participating. And, no, we do not have any details at all, but assume that it will be in roughly the same calendar space as this year's event, ie, somewhere in the August-October timeframe. Thanks. -- Rich Bowen VP Conferences The Apache Software Foundation @apachecon - To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
Re: [VOTE] Apache Cassandra Release Lifecycle
I made a couple of additional changes to the document based on the comments, and there are a couple more that need to be addressed. I will work on moving this document to cwiki. Thanks, Sumanth On Tue, Oct 1, 2019 at 10:02 AM Dinesh Joshi wrote: > There are a few points that need to be clarified in doc. I am also fine if > we want to adopt the document as-is and then refine it as we build > experience with the process. > > Dinesh > > > On Sep 30, 2019, at 3:24 PM, sankalp kohli > wrote: > > > > Sure..lets do that. > > > > On Mon, Sep 30, 2019 at 3:21 PM Benedict Elliott Smith < > bened...@apache.org> > > wrote: > > > >> Perhaps we should move the proposed document to the cwiki for purposes > of > >> voting? That way it's in a place owned by the project, with a permanent > >> history. Otherwise it's not entirely clear what was voted on. > >> > >> > >> On 30/09/2019, 20:10, "Sumanth Pasupuleti" < > >> sumanth.pasupuleti...@gmail.com> wrote: > >> > >>+1 > >> > >>On Mon, Sep 30, 2019 at 12:00 PM Nate McCall > >> wrote: > >> > >>> +1 > >>> > >>> On Tue, Oct 1, 2019 at 7:52 AM sankalp kohli >>> > >>> wrote: > >>> > Hi, > We have discussed in the email thread[1] about Apache Cassandra > >>> Release > Lifecycle. We came up with a doc[2] for it. Please vote on it if > >> you > >>> agree > with the content of the doc[2]. > > Thanks, > Sankalp > > [1] > > > >>> > >> > https://lists.apache.org/thread.html/c610b23f9002978636b66d09f0e0481ed3de9b78895050da22c91c6f@%3Cdev.cassandra.apache.org%3E > [2] > > > >>> > >> > https://docs.google.com/document/d/1bS6sr-HSrHFjZb0welife6Qx7u3ZDgRiAoENMLYlfz8/edit#heading=h.633eppni91tw > > >>> > >> > >> > >> > >> > >> - > >> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > >> For additional commands, e-mail: dev-h...@cassandra.apache.org > >> > >> > > > - > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > For additional commands, e-mail: dev-h...@cassandra.apache.org > >
Re: [VOTE] Apache Cassandra Release Lifecycle
There are a few points that need to be clarified in doc. I am also fine if we want to adopt the document as-is and then refine it as we build experience with the process. Dinesh > On Sep 30, 2019, at 3:24 PM, sankalp kohli wrote: > > Sure..lets do that. > > On Mon, Sep 30, 2019 at 3:21 PM Benedict Elliott Smith > wrote: > >> Perhaps we should move the proposed document to the cwiki for purposes of >> voting? That way it's in a place owned by the project, with a permanent >> history. Otherwise it's not entirely clear what was voted on. >> >> >> On 30/09/2019, 20:10, "Sumanth Pasupuleti" < >> sumanth.pasupuleti...@gmail.com> wrote: >> >>+1 >> >>On Mon, Sep 30, 2019 at 12:00 PM Nate McCall >> wrote: >> >>> +1 >>> >>> On Tue, Oct 1, 2019 at 7:52 AM sankalp kohli >> >>> wrote: >>> Hi, We have discussed in the email thread[1] about Apache Cassandra >>> Release Lifecycle. We came up with a doc[2] for it. Please vote on it if >> you >>> agree with the content of the doc[2]. Thanks, Sankalp [1] >>> >> https://lists.apache.org/thread.html/c610b23f9002978636b66d09f0e0481ed3de9b78895050da22c91c6f@%3Cdev.cassandra.apache.org%3E [2] >>> >> https://docs.google.com/document/d/1bS6sr-HSrHFjZb0welife6Qx7u3ZDgRiAoENMLYlfz8/edit#heading=h.633eppni91tw >>> >> >> >> >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org >> For additional commands, e-mail: dev-h...@cassandra.apache.org >> >> - To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
ApacheCon North America 2020, project participation
Hi, folks, (Note: You're receiving this email because you're on the dev@ list for one or more Apache Software Foundation projects.) For ApacheCon North America 2019, we asked projects to participate in the creation of project/topic specific tracks. This was very successful, with about 15 projects stepping up to curate the content for their track/summit/event. We need to know if you're going to do the same for 2020. This informs how large a venue we book for the event, how long the event runs, and many other considerations. If you intend to participate again in 2020, we need to hear from you on the plann...@apachecon.com mailing list. This is not a firm commitment, but we need to know if you're, say, 75% confident that you'll be participating. And, no, we do not have any details at all, but assume that it will be in roughly the same calendar space as this year's event, ie, somewhere in the August-October timeframe. Thanks. -- Rich Bowen VP Conferences The Apache Software Foundation @apachecon - To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
Re: "4.0: TBD" -> "4.0: Est. Q4 2019"?
> Seems like the intersection of this is: "Lazy consensus is simply an > announcement of 'silence gives assent.'" with a caveat of "you have N hours > to dissent before we take silence as assent" when you're unsure or a topic > is contentious, which tracks with what I've seen kind of informally happen > on the project in the past 5.5 years. Agree Joshua, the project has already 'silence as assent' and lazy consensus as part of its culture. It's useful when reasonably confident of a change but still hesitant and it is safer to at least mention it on the dev ML, eg "i'm going to do this in a few days unless anyone objects…" It is a complex enough project. - To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
