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
+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 e
/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 a
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 o
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
/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
+1 to 4.1 in May.
On Tue, Dec 14, 2021, 6:46 AM Mick Semb Wever wrote:
> > We cut 4.0 in May and released it in July. It is difficult to plan for a
> release date so we should probably agree on the cut date. One year after
> 4.0 that would make us cut the new branch in May.
>
>
> This makes sens
+1 to 4.1 in May.
On Mon, Jan 3, 2022 at 12:58 PM David Capwell wrote:
> 4.1 target of may works for me, we may want to remove a few things in
> Config.java if not wrapped up on time (thinking track warnings and
> guardrails, though that should be handled by then)
>
> > On Dec 14, 2021, at 5:02
4.1 target of may works for me, we may want to remove a few things in
Config.java if not wrapped up on time (thinking track warnings and guardrails,
though that should be handled by then)
> On Dec 14, 2021, at 5:02 AM, Paulo Motta wrote:
>
> +1 to cut 4.1 in May. It would be great to attain th
Just to be very clear.
I think that bumping the semantic version number because some arbitrary
time constraint has passed is a bad idea. Version numbers should be bumped
when dictated by the change to the code. It makes sense that if you have
released 3.2.0 then the next nightly snapshot would b
10 matches
Mail list logo
