Re: Fwd: [CI] What are the troubles projects face with CI and Infra
Another thing worth mentioning is the overhead with providing, setting up, and managing infrastructure. While donations of servers/VM’s works to some extent, it’s a somewhat archaic donation policy – and this whole structure of CI gives both the ASF and the C* project very limited choices. From my perspective it would be much more suitable for the C* project to receive financial or credit based donations, on which we could utilise against whatever CI/CD we desired. This would open up modern options for CI and not limit us to just ASF-ran Jenkins. I’m sure this would be much more suitable for many smaller organisations, with possible tax benefits as well, rather than providing infrastructure (which lets face it, is rarely bare metal servers these days) that they have to maintain. For example, It’d be ideal if there was a C* CircleCI account (or deployment) that the project could use that could be funded by the community, rather than the big backers being the only ones able to run the tests effectively (and thus everyone relying on them paying for and doing it for them). On 2020/02/02 21:51:54, Nate McCall wrote: > Hi folks, > The board is looking for feedback on CI infrastructure. I'm happy to take > some (constructive) comments back. (Shuler, Mick and David Capwell > specifically as folks who've most recently wrestled with this a fair bit). > > Thanks, > -Nate > > -- Forwarded message - > From: Dave Fisher > Date: Mon, Feb 3, 2020 at 8:58 AM > Subject: [CI] What are the troubles projects face with CI and Infra > To: Apache Board > > > Hi - > > It has come to the attention of the board through looking at past board > reports that some projects are having problems with CI infrastructure. > > Are there still troubles and what are they? > > Regards, > Dave > Sent from Mail for Windows 10
Re: Ideas for Cassandra 2020 - Remote Meetups / Mastermind
Rahul, Don't cut yourself short. I love what you've done with Awesome Cassandra and organizing meetups. Those are really valuable contributions. For everyone else on this ML, if you don't know about Awesome Cassandra. Rahul picked it up and has been keeping it up to date. https://cassandra.link/awesome/ Patrick On Mon, Feb 10, 2020 at 8:52 AM Rahul Singh wrote: > Thanks, Michael. I sent that before I read up on the notes. > > @nate , @jon , @dinesh I can help with the Documentation. > > If you have any specific doc issues you want reviewed, edited, etc, > please let me know. > > If there's a specific JQL on the JIRA board I can start with there. > > rahul.xavier.si...@gmail.com > > http://cassandra.link > > > > On Mon, Feb 10, 2020 at 8:36 AM Michael Shuler > wrote: > > > This is great, thanks, the project appreciates the effort. 2019 is over, > > don't worry about the past. Moving forward in little or large steps is > > the goal. :) > > > > If you didn't get a chance to attend the first Contributor Meeting, > > there will be more. Patrick sent out a survey last week for feedback, so > > I imagine these will continue at a regular interval with continued > > interest and attendance. Perhaps you could schedule some in-person > > meetup thing to coincide, as an idea, or just get the word out to others > > that might be interested in listening in? > > > > (Next one has not been scheduled yet, but will show up here on dev@ > list.) > > > > > > > https://cwiki.apache.org/confluence/display/CASSANDRA/Apache+Cassandra+Contributor+Meeting > > > > Michael > > > > On 2/8/20 10:06 PM, Rahul Singh wrote: > > > Folks, (Initially meant for User , but realized after I wrote it , it’s > > more sausage making talk which en users probably don’t care about) > > > > > > I took on a bunch of work and finally starting to get my head out of > the > > sand and realized I failed to deliver on some promises last year I made > to > > myself and others to contribute to this community. I wanted to resurface > a > > few thoughts on which I would like to contribute. > > > > > > We had a conversation on here a while ago to try doing a virtual > > conference.. which I think is a bit too ambitious. I also spoke to Dinesh > > last year briefly about doing periodic development meetings which focused > > on the development planning and execution. > > > > > > I’d like to help this project but I don’t know where to start. I tried > > getting some Jr. members internally at Anant who had time to make fixes > on > > content and docs but it didn’t get looked at or reviewed so they lost > > interest. There’s only so much they would want to do based on my > requests. > > The failure to deliver on better documentation organization was mainly > mine > > because I didn’t commit enough time into it. > > > > > > I don’t think our community does a good enough job communicating the > > Cassandra value proposition to the enterprise community whether they are > > developers, architects, or directors. I’ve been meeting with many folks > > that haven’t touched their clusters since installing 2.1 (because it’s > > pretty damn good for most people!). When I ask them why, it’s a > combination > > of team member churn but also because the knowledge is not as accessible. > > > > > > This year as January closes I am recommitting myself to some ideas and > > would LOVE your feedback. If somethings like this are in progress, I will > > help. > > > > > > > > > 1. Cassandra Lunch - I’ve been seeing a colleague getting together with > > his fellow practitioners for a weekly “Sitecore Lunch” and I found it a > > very easy way to get people talking that normally wouldn’t be interacting > > with each other in realtime. > > > 2. Coordinated Remote Meetup - I think this would be way easier to > > organize and get cross promoted as a quarterly event with the help of > local > > organizers. I’m currently organizing DC / Chicago and have been cross > > promoting virtual talks to both and have gotten a good show with people > > curious about Cassandra. > > > 3. Documentation - I know I said I’d help last year. I underestimated > my > > free time and over estimated my capacity to focus. That being said , this > > is one of my passions and I help a lot of orgs get their [blank] together > > on how to manage their people, process, info and systems and the first > > thing is always knowledge management. If there’s someone I can shadow and > > apprentice under to help with Cassandra.Apache.org I really want to help > > revitalize our site. > > > > > > > > > These may still be overestimating my capacity but I’m willing to fail > > and try again. :) > > > > > > > > > rahul.xavier.si...@gmail.com > > > > > > http://cassandra.link > > > The Apache Cassandra Knowledge Base. > > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > > For additional commands, e-mail:
[VOTE] Release Apache Cassandra 2.2.16
Proposing the test build of Cassandra 2.2.16 for release. sha1: c4d9e9ca4ade40b956e37935bce68737b0c063b9 Git: https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.2.16-tentative Maven Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-1191/org/apache/cassandra/cassandra-all/2.2.16/ The Source and Build Artifacts, and the Debian and RPM packages are available here: https://dist.apache.org/repos/dist/dev/cassandra/2.2.16/ The vote will be open for 72 hours (longer if needed). Everyone who has tested the build is invited to vote. Votes by PMC members are considered binding. A vote passes if there are at least three binding +1s. Again note the release process is undergoing improvements to deal with sha256|512 checksums and to use the ASF dev dist staging location. Please be extra critical. The deb and rpm repositories are also now available to verify before the vote. [1]: CHANGES.txt: https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/2.2.16-tentative [2]: NEWS.txt: https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/2.2.16-tentative - To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
Re: Feedback from the last Apache Cassandra Contributor Meeting
Just a Monday reminder on the survey link I sent. I got a few responses but could use a few more to give us some decent N. If you have < 5minutes today, I would appreciate your feedback. I'll keep it open until tomorrow and then send results. Patrick On Mon, Feb 3, 2020 at 4:21 PM Patrick McFadin wrote: > Hi everyone, > > One action item I took from our first contributor meeting was gather > feedback for the next meetings. I've created a short survey if you would > like to offer feedback. I'll let it run for the week and report back on the > results. > > https://www.surveymonkey.com/r/C95B7ZP > > Thanks, > > Patrick >
Re: Ideas for Cassandra 2020 - Remote Meetups / Mastermind
Thanks, Michael. I sent that before I read up on the notes. @nate , @jon , @dinesh I can help with the Documentation. If you have any specific doc issues you want reviewed, edited, etc, please let me know. If there's a specific JQL on the JIRA board I can start with there. rahul.xavier.si...@gmail.com http://cassandra.link On Mon, Feb 10, 2020 at 8:36 AM Michael Shuler wrote: > This is great, thanks, the project appreciates the effort. 2019 is over, > don't worry about the past. Moving forward in little or large steps is > the goal. :) > > If you didn't get a chance to attend the first Contributor Meeting, > there will be more. Patrick sent out a survey last week for feedback, so > I imagine these will continue at a regular interval with continued > interest and attendance. Perhaps you could schedule some in-person > meetup thing to coincide, as an idea, or just get the word out to others > that might be interested in listening in? > > (Next one has not been scheduled yet, but will show up here on dev@ list.) > > > https://cwiki.apache.org/confluence/display/CASSANDRA/Apache+Cassandra+Contributor+Meeting > > Michael > > On 2/8/20 10:06 PM, Rahul Singh wrote: > > Folks, (Initially meant for User , but realized after I wrote it , it’s > more sausage making talk which en users probably don’t care about) > > > > I took on a bunch of work and finally starting to get my head out of the > sand and realized I failed to deliver on some promises last year I made to > myself and others to contribute to this community. I wanted to resurface a > few thoughts on which I would like to contribute. > > > > We had a conversation on here a while ago to try doing a virtual > conference.. which I think is a bit too ambitious. I also spoke to Dinesh > last year briefly about doing periodic development meetings which focused > on the development planning and execution. > > > > I’d like to help this project but I don’t know where to start. I tried > getting some Jr. members internally at Anant who had time to make fixes on > content and docs but it didn’t get looked at or reviewed so they lost > interest. There’s only so much they would want to do based on my requests. > The failure to deliver on better documentation organization was mainly mine > because I didn’t commit enough time into it. > > > > I don’t think our community does a good enough job communicating the > Cassandra value proposition to the enterprise community whether they are > developers, architects, or directors. I’ve been meeting with many folks > that haven’t touched their clusters since installing 2.1 (because it’s > pretty damn good for most people!). When I ask them why, it’s a combination > of team member churn but also because the knowledge is not as accessible. > > > > This year as January closes I am recommitting myself to some ideas and > would LOVE your feedback. If somethings like this are in progress, I will > help. > > > > > > 1. Cassandra Lunch - I’ve been seeing a colleague getting together with > his fellow practitioners for a weekly “Sitecore Lunch” and I found it a > very easy way to get people talking that normally wouldn’t be interacting > with each other in realtime. > > 2. Coordinated Remote Meetup - I think this would be way easier to > organize and get cross promoted as a quarterly event with the help of local > organizers. I’m currently organizing DC / Chicago and have been cross > promoting virtual talks to both and have gotten a good show with people > curious about Cassandra. > > 3. Documentation - I know I said I’d help last year. I underestimated my > free time and over estimated my capacity to focus. That being said , this > is one of my passions and I help a lot of orgs get their [blank] together > on how to manage their people, process, info and systems and the first > thing is always knowledge management. If there’s someone I can shadow and > apprentice under to help with Cassandra.Apache.org I really want to help > revitalize our site. > > > > > > These may still be overestimating my capacity but I’m willing to fail > and try again. :) > > > > > > rahul.xavier.si...@gmail.com > > > > http://cassandra.link > > The Apache Cassandra Knowledge Base. > > > > - > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > For additional commands, e-mail: dev-h...@cassandra.apache.org > >
2/10/2020 4.0 status update
2/10/2020: Today's 4.0 status update: The 4.0 board can be found at https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=355. The broad view: We have a total of 95 tickets open for 4.0 releases (No change from 11 days ago, though 5 are cwiki migration tests): https://issues.apache.org/jira/issues/?filter=12347896 Cumulative flow updated, now restricted to last 3 months: https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=355=CASSANDRA=reporting=cumulativeFlowDiagram=939=936=931=1505=1506=1514=1509=1512=1507=90 What pops for me: velocity on closes look healthy, we just had new tickets open to match what we closed out: https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=355=1670 5 of those are the test epic + 4 test tracking tickets from me looking into migrating cwiki stuff to JIRA. That filter above is last 7d and it's been 11 since our last email, but the trajectory stands. It's almost entirely new flaky test failures or those testing JIRAs, so we're likely replacing larger scoped "chunky" tickets with smaller test failures, meaning we should see close-out velocity catch up and surpass creation within the next couple cycles. All healthy signs at this point in our release lifecycle (working through alphas) IMO. We closed out 16 tickets in the past 11 days ( https://issues.apache.org/jira/issues/?filter=12347782=project%20%3D%20cassandra%20AND%20fixversion%20in%20(4.0%2C%204.0.0%2C%204.0-alpha%2C%204.0-beta)%20AND%20resolved%20%3E%3D%20-11d%20ORDER%20BY%20priority%20DESC%2C%20assignee) giving us a rolling 4 week total of 46, up from 37. This puts our 4 week rolling change in the past 3 weeks at 26, 37, and now 46 - increasing close momentum. *Newly opened tickets* We had 9 new tickets open in the last week that were not the epic test: https://issues.apache.org/jira/issues/?filter=12347782=project%20%3D%20cassandra%20AND%20fixversion%20in%20(4.0%2C%204.0.0%2C%204.0-alpha%2C%204.0-beta)%20AND%20created%20%3E%20-11d%20and%20resolution%20%3D%20unresolved%20and%20type%20!%3D%20epic%20and%20(%22Epic%20Link%22%20!%3D%20CASSANDRA-15536%20OR%20%22Epic%20Link%22%20is%20empty) Of the unassigned, 5 are flaky tests and CASSANDRA-15549 is a pretty straightforward doc / recommendation change ticket, so all good candidates to pick up if you want to start getting more involved with the project. *LHF / Failing Tests*: We have 8 unassigned test failures that are all great candidates to pick up and get involved in: https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=355=CASSANDRA=1660=1661=1658 *Needs Reviewer*: 11 tickets need a reviewer. This is *up* from 7 last time, so this is growing. 3 alpha, 1 beta, and 7 RC; I'd advocate that people take a moment to help out with reviews if you have flexible cycles to burn that queue down. https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=355=1659 *Available to work*: 9 alpha, 4 beta, and 14 RC tickets are available for work (no assignee): https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=355=detail=CASSANDRA-15308=1661=1658 Most of these are pretty low friction to pick up and work. *Ready to Commit*: 4 tickets (down from 6) are marked ready to commit. https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=355=CASSANDRA-14688=1672=1661 *Testing*: I have a JIRA epic for tracking the cwiki status I put together; I emailed the dev list and got some general "Lazy Consensus ftw, do what makes you happy" style responses on it. I'll be traveling (again) this week, but I'll see if I can't migrate the rest of the wiki into JIRA so I have a final alpha of what it'll look like to get a final +1 on before marking the cwiki deprecated and we can start driving assignee / reviewer / etc through this email on the broader 4.0 testing initiatives. Epic is here: https://issues.apache.org/jira/browse/CASSANDRA-15536 As always, thanks everyone for the time and effort you're putting into this release specifically and the project in general. If you have any feedback about ways I could improve the signal / value of information in this email, please don't hesitate to let me know. My goal for this effort is to reduce friction to contribution, save everyone's time by consolidating information and visibility here, and help align us all on the project, so let me know if there's something I can do to improve any of this. Thanks again! ~Josh
Re: Ideas for Cassandra 2020 - Remote Meetups / Mastermind
This is great, thanks, the project appreciates the effort. 2019 is over, don't worry about the past. Moving forward in little or large steps is the goal. :) If you didn't get a chance to attend the first Contributor Meeting, there will be more. Patrick sent out a survey last week for feedback, so I imagine these will continue at a regular interval with continued interest and attendance. Perhaps you could schedule some in-person meetup thing to coincide, as an idea, or just get the word out to others that might be interested in listening in? (Next one has not been scheduled yet, but will show up here on dev@ list.) https://cwiki.apache.org/confluence/display/CASSANDRA/Apache+Cassandra+Contributor+Meeting Michael On 2/8/20 10:06 PM, Rahul Singh wrote: Folks, (Initially meant for User , but realized after I wrote it , it’s more sausage making talk which en users probably don’t care about) I took on a bunch of work and finally starting to get my head out of the sand and realized I failed to deliver on some promises last year I made to myself and others to contribute to this community. I wanted to resurface a few thoughts on which I would like to contribute. We had a conversation on here a while ago to try doing a virtual conference.. which I think is a bit too ambitious. I also spoke to Dinesh last year briefly about doing periodic development meetings which focused on the development planning and execution. I’d like to help this project but I don’t know where to start. I tried getting some Jr. members internally at Anant who had time to make fixes on content and docs but it didn’t get looked at or reviewed so they lost interest. There’s only so much they would want to do based on my requests. The failure to deliver on better documentation organization was mainly mine because I didn’t commit enough time into it. I don’t think our community does a good enough job communicating the Cassandra value proposition to the enterprise community whether they are developers, architects, or directors. I’ve been meeting with many folks that haven’t touched their clusters since installing 2.1 (because it’s pretty damn good for most people!). When I ask them why, it’s a combination of team member churn but also because the knowledge is not as accessible. This year as January closes I am recommitting myself to some ideas and would LOVE your feedback. If somethings like this are in progress, I will help. 1. Cassandra Lunch - I’ve been seeing a colleague getting together with his fellow practitioners for a weekly “Sitecore Lunch” and I found it a very easy way to get people talking that normally wouldn’t be interacting with each other in realtime. 2. Coordinated Remote Meetup - I think this would be way easier to organize and get cross promoted as a quarterly event with the help of local organizers. I’m currently organizing DC / Chicago and have been cross promoting virtual talks to both and have gotten a good show with people curious about Cassandra. 3. Documentation - I know I said I’d help last year. I underestimated my free time and over estimated my capacity to focus. That being said , this is one of my passions and I help a lot of orgs get their [blank] together on how to manage their people, process, info and systems and the first thing is always knowledge management. If there’s someone I can shadow and apprentice under to help with Cassandra.Apache.org I really want to help revitalize our site. These may still be overestimating my capacity but I’m willing to fail and try again. :) rahul.xavier.si...@gmail.com http://cassandra.link The Apache Cassandra Knowledge Base. - To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
