Re: Cassandra project biweekly status update 2022-01-03

[Joshua McKenzie]

I'll follow up with Chris on slack about this. He and I are looking into a
couple other updates to the site as well so this should complement that
workflow nicely.


On Tue, Jan 4, 2022 at 10:27 AM Melissa Logan  wrote:

> Josh, shall we add these details to the monthly Changelog blog that Chris
> T drafts? He uses your recaps as a basis.
>
> Shared on the #cassandra-website channel. Example:
> https://cassandra.apache.org/_/blog/Apache-Cassandra-Changelog-10-October-2021.html
>
> On Tue, Jan 4, 2022 at 7:21 AM Joshua McKenzie 
> wrote:
>
>> Could we post these on the blog as well
>>
>> I always wanted to be a blogger. Sounds like now's my chance. ;)
>>
>> In all seriousness I think this is a great idea. I'll find out what I
>> need to know to make this happen and make it so.
>>
>> On Mon, Jan 3, 2022 at 7:38 PM Patrick McFadin 
>> wrote:
>>
>>> What Ellis said.
>>>
>>> On Mon, Jan 3, 2022 at 1:48 PM Jonathan Ellis  wrote:
>>>
 +10

 Could we post these on the blog as well to reach a wider audience?

 On Mon, Jan 3, 2022 at 3:16 PM Mick Semb Wever  wrote:

>
>
> /wave Happy 2022 everyone! …
>> …
>>
>> It's been incredibly encouraging to see how active the project has
>> been in 2021 and I look forward to seeing how things evolve with some of
>> the upcoming significant CEP's and features this year. Thanks everyone!
>>
>
>
>
> These updates are really awesome Josh and also a big part of the
> project's new activity. Thanks for keeping at them!
>


 --
 Jonathan Ellis
 co-founder, http://www.datastax.com
 @spyced

>>>
>
> --
> Melissa Logan (she/her)
> Principal, Constantia.io
> meli...@constantia.io
> Cell: 503-317-8498
> LinkedIn  | Twitter
> 
>
>

Re: Cassandra project biweekly status update 2022-01-03

[Melissa Logan]

Josh, shall we add these details to the monthly Changelog blog that Chris T
drafts? He uses your recaps as a basis.

Shared on the #cassandra-website channel. Example:
https://cassandra.apache.org/_/blog/Apache-Cassandra-Changelog-10-October-2021.html

On Tue, Jan 4, 2022 at 7:21 AM Joshua McKenzie  wrote:

> Could we post these on the blog as well
>
> I always wanted to be a blogger. Sounds like now's my chance. ;)
>
> In all seriousness I think this is a great idea. I'll find out what I need
> to know to make this happen and make it so.
>
> On Mon, Jan 3, 2022 at 7:38 PM Patrick McFadin  wrote:
>
>> What Ellis said.
>>
>> On Mon, Jan 3, 2022 at 1:48 PM Jonathan Ellis  wrote:
>>
>>> +10
>>>
>>> Could we post these on the blog as well to reach a wider audience?
>>>
>>> On Mon, Jan 3, 2022 at 3:16 PM Mick Semb Wever  wrote:
>>>


 /wave Happy 2022 everyone! …
> …
>
> It's been incredibly encouraging to see how active the project has
> been in 2021 and I look forward to seeing how things evolve with some of
> the upcoming significant CEP's and features this year. Thanks everyone!
>



 These updates are really awesome Josh and also a big part of the
 project's new activity. Thanks for keeping at them!

>>>
>>>
>>> --
>>> Jonathan Ellis
>>> co-founder, http://www.datastax.com
>>> @spyced
>>>
>>

-- 
Melissa Logan (she/her)
Principal, Constantia.io
meli...@constantia.io
Cell: 503-317-8498
LinkedIn  | Twitter

Re: Cassandra project biweekly status update 2022-01-03

[Joshua McKenzie]

>
> Could we post these on the blog as well

I always wanted to be a blogger. Sounds like now's my chance. ;)

In all seriousness I think this is a great idea. I'll find out what I need
to know to make this happen and make it so.

On Mon, Jan 3, 2022 at 7:38 PM Patrick McFadin  wrote:

> What Ellis said.
>
> On Mon, Jan 3, 2022 at 1:48 PM Jonathan Ellis  wrote:
>
>> +10
>>
>> Could we post these on the blog as well to reach a wider audience?
>>
>> On Mon, Jan 3, 2022 at 3:16 PM Mick Semb Wever  wrote:
>>
>>>
>>>
>>> /wave Happy 2022 everyone! …
 …

 It's been incredibly encouraging to see how active the project has been
 in 2021 and I look forward to seeing how things evolve with some of the
 upcoming significant CEP's and features this year. Thanks everyone!
>>>
>>>
>>>
>>> These updates are really awesome Josh and also a big part of the
>>> project's new activity. Thanks for keeping at them!
>>>
>>
>>
>> --
>> Jonathan Ellis
>> co-founder, http://www.datastax.com
>> @spyced
>>
>

Re: Cassandra project biweekly status update 2022-01-03

[Patrick McFadin]

What Ellis said.

On Mon, Jan 3, 2022 at 1:48 PM Jonathan Ellis  wrote:

> +10
>
> Could we post these on the blog as well to reach a wider audience?
>
> On Mon, Jan 3, 2022 at 3:16 PM Mick Semb Wever  wrote:
>
>>
>>
>> /wave Happy 2022 everyone! …
>>> …
>>>
>>> It's been incredibly encouraging to see how active the project has been
>>> in 2021 and I look forward to seeing how things evolve with some of the
>>> upcoming significant CEP's and features this year. Thanks everyone!
>>
>>
>>
>> These updates are really awesome Josh and also a big part of the
>> project's new activity. Thanks for keeping at them!
>>
>
>
> --
> Jonathan Ellis
> co-founder, http://www.datastax.com
> @spyced
>

Re: Cassandra project biweekly status update 2022-01-03

[Jonathan Ellis]

+10

Could we post these on the blog as well to reach a wider audience?

On Mon, Jan 3, 2022 at 3:16 PM Mick Semb Wever  wrote:

>
>
> /wave Happy 2022 everyone! …
>> …
>>
>> It's been incredibly encouraging to see how active the project has been
>> in 2021 and I look forward to seeing how things evolve with some of the
>> upcoming significant CEP's and features this year. Thanks everyone!
>
>
>
> These updates are really awesome Josh and also a big part of the project's
> new activity. Thanks for keeping at them!
>


-- 
Jonathan Ellis
co-founder, http://www.datastax.com
@spyced

Re: Cassandra project biweekly status update 2022-01-03

[Mick Semb Wever]

/wave Happy 2022 everyone! …
> …
>
> It's been incredibly encouraging to see how active the project has been in
> 2021 and I look forward to seeing how things evolve with some of the
> upcoming significant CEP's and features this year. Thanks everyone!



These updates are really awesome Josh and also a big part of the project's
new activity. Thanks for keeping at them!

Re: Cassandra project biweekly status update 2022-01-03

[Joshua McKenzie]

Assuming you're talking about the list of tickets with "mentor is not
empty" in JIRA here:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20cassandra%20and%20mentor%20is%20not%20empty%20and%20resolution%20%3D%20unresolved

They're loosely related. The list of tickets I sent out above is ones we've
flagged as being appropriate for newcomers to the project but may or may
not yet have mentors associated with them (most likely not as they're
unassigned as per the filter). I expect the workflow to look something like:
1. Individual finds a ticket on a topic that interests them
2. Pings in #cassandra-dev to the @cassandra_mentors handle to find a
mentor to assist on the ticket in question
3. We add a mentor to that ticket and move forward

I'll add that to the biweekly emails going forward; I first saw that slack
handle in action seven days ago so it's fresh.

That help clarify?

~Josh


On Mon, Jan 3, 2022 at 2:57 PM Manish G 
wrote:

> There is already a list of tickets with mentors associated. Do these
> 'lhfs' also fall in same category?
>
> On Mon, Jan 3, 2022, 8:51 PM Joshua McKenzie  wrote:
>
>> /wave Happy 2022 everyone!
>>
>> [New contributors getting started]
>> There are two curated options for getting started if you're new to the
>> project and looking to get oriented: Failing tests, or starter tickets we
>> label "lhf" (low hanging fruit). Don't let either fool you - it's almost
>> always interesting work with more depth than expected at first glance. Yay
>> mature distributed infrastructure software! :)
>>
>> Query for failing tests:
>> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252
>> Query for unassigned starter tickets:
>> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=484=2162=2160
>>
>> We've bumped up a bit on open test failure tickets; have 26 unassigned to
>> choose from and we have just over 30 good starter tickets evenly split
>> between our next minor release and next major. Feel free to self-select
>> from any of the above lists or reach out on slack if you want some guidance
>> on where to get involved. 2022 is a good year to start getting involved in
>> some coding don't you think?
>>
>> [Dev list discussions in the past 14 days]
>> https://lists.apache.org/list?dev@cassandra.apache.org:lte=2w:
>>
>> We were slightly less chatty than usual over the past couple of weeks
>> which is to be expected. Still - some interesting things to discuss:
>>
>> - When should we cut our next major release (early signs of consensus)?
>> https://lists.apache.org/thread/lsr45h2n72m8fbz3xqby6lsm7lqr7vm8
>> - How should we version releases and snapshots (early signs of... not so
>> much consensus :D)
>> https://lists.apache.org/thread/zz3x1zl1lo8rkqpf0cl992y6fsy4r9gc
>>
>> And some various and sundry, mostly around me being irritated with
>> failing tests when I try to merge things and trying to figure out how to
>> kill this problem with fire. A grand and well established tradition on the
>> project stretching back years.
>>
>> [Tickets Closed in the past 14 days]
>>
>> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=484=2175
>>
>> Not surprisingly things were very slow on the close front (3 total,
>> minimal things). On the plus side, this means picking patches back up that
>> are works in flight here in Jan will require minimal, if any, rebasing. :)
>>
>> [Tickets that need attention]
>> Needs Reviewer:
>> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=484=CASSANDRA-16547=2259
>>
>> Down from 10 to 9 needing review on 4.0.2 and holding steady at 30 on
>> 4.1.0. I'm going to get a little bit more active in trying to track down or
>> provide review for things on this list; patches rotting (and people having
>> to drag things forward via repeated rebasing) due to lack of review is not
>> my personal favorite.
>>
>> [Test Failure Trendlines]
>> Butler: https://butler.cassandra.apache.org/#/
>> Stable branches are holding steady and trending slightly down which is
>> what we'd expect for where they are in their lifecycle and the holiday
>> season.
>> * 3.0:30 -> 28
>> * 3.11:   42 -> 40
>> * 4.0:10 -> 9
>> * trunk:  ... varied.
>>
>> We've been discussing in the #cassandra-dev slack about workflow and ways
>> to make the Butler <-> JIRA relationship a bit more turnkey and the
>> introduction of the Build Lead role. Should have some draft wikis up for
>> review on that shortly.
>>
>> It's been incredibly encouraging to see how active the project has been
>> in 2021 and I look forward to seeing how things evolve with some of the
>> upcoming significant CEP's and features this year. Thanks everyone!
>>
>> ~Josh
>>
>

Re: Cassandra project biweekly status update 2022-01-03

[Manish G]

There is already a list of tickets with mentors associated. Do these 'lhfs'
also fall in same category?

On Mon, Jan 3, 2022, 8:51 PM Joshua McKenzie  wrote:

> /wave Happy 2022 everyone!
>
> [New contributors getting started]
> There are two curated options for getting started if you're new to the
> project and looking to get oriented: Failing tests, or starter tickets we
> label "lhf" (low hanging fruit). Don't let either fool you - it's almost
> always interesting work with more depth than expected at first glance. Yay
> mature distributed infrastructure software! :)
>
> Query for failing tests:
> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496=2252
> Query for unassigned starter tickets:
> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=484=2162=2160
>
> We've bumped up a bit on open test failure tickets; have 26 unassigned to
> choose from and we have just over 30 good starter tickets evenly split
> between our next minor release and next major. Feel free to self-select
> from any of the above lists or reach out on slack if you want some guidance
> on where to get involved. 2022 is a good year to start getting involved in
> some coding don't you think?
>
> [Dev list discussions in the past 14 days]
> https://lists.apache.org/list?dev@cassandra.apache.org:lte=2w:
>
> We were slightly less chatty than usual over the past couple of weeks
> which is to be expected. Still - some interesting things to discuss:
>
> - When should we cut our next major release (early signs of consensus)?
> https://lists.apache.org/thread/lsr45h2n72m8fbz3xqby6lsm7lqr7vm8
> - How should we version releases and snapshots (early signs of... not so
> much consensus :D)
> https://lists.apache.org/thread/zz3x1zl1lo8rkqpf0cl992y6fsy4r9gc
>
> And some various and sundry, mostly around me being irritated with failing
> tests when I try to merge things and trying to figure out how to kill this
> problem with fire. A grand and well established tradition on the project
> stretching back years.
>
> [Tickets Closed in the past 14 days]
>
> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=484=2175
>
> Not surprisingly things were very slow on the close front (3 total,
> minimal things). On the plus side, this means picking patches back up that
> are works in flight here in Jan will require minimal, if any, rebasing. :)
>
> [Tickets that need attention]
> Needs Reviewer:
> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=484=CASSANDRA-16547=2259
>
> Down from 10 to 9 needing review on 4.0.2 and holding steady at 30 on
> 4.1.0. I'm going to get a little bit more active in trying to track down or
> provide review for things on this list; patches rotting (and people having
> to drag things forward via repeated rebasing) due to lack of review is not
> my personal favorite.
>
> [Test Failure Trendlines]
> Butler: https://butler.cassandra.apache.org/#/
> Stable branches are holding steady and trending slightly down which is
> what we'd expect for where they are in their lifecycle and the holiday
> season.
> * 3.0:30 -> 28
> * 3.11:   42 -> 40
> * 4.0:10 -> 9
> * trunk:  ... varied.
>
> We've been discussing in the #cassandra-dev slack about workflow and ways
> to make the Butler <-> JIRA relationship a bit more turnkey and the
> introduction of the Build Lead role. Should have some draft wikis up for
> review on that shortly.
>
> It's been incredibly encouraging to see how active the project has been in
> 2021 and I look forward to seeing how things evolve with some of the
> upcoming significant CEP's and features this year. Thanks everyone!
>
> ~Josh
>