t/patches.html (under "Creating a
> Patch") ... I'll reword to indicate this is a recommendation or suggestion.
>
> SFAIK there is nothing process-wise that mandates a particular branch naming
> structure, particularly for folks working in their own forked repo.
>
Hi Joel,
Thank you for bringing the question of improving CONTRIBUTING.md. I’ve read the
thread but not sure if there will be changes to the file. Thus, I will mention
that the following item caught my attention:
> 3) Create your feature branch, named with the JIRA id (CASSANDRA-12345)
>
This i
Hi,
I would like to note that I as contributor cannot add labels or do almost
nothing in my PRs to Apache Cassandra. So it completely relies on committers, I
guess.
In a case you decide to ask contributors/PR owners to label their PRs it will
be necessary to provide the functionality.
Best reg
hen they
are many and need to be placed on multiple lines. For me it takes less effort
to grasp arguments on separate lines than when several arguments are combined
on the same line. IMHO the root cause is having too many arguments, which is
common issue for non-OOP languages.
Best regards,
Rus
