You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Ekaterina Dimitrova (Jira)" <ji...@apache.org> on 2021/05/03 18:17:00 UTC
[jira] [Commented] (CASSANDRA-16647) Update how_to_commit
documentation after cassandra-4.0 branch
[ https://issues.apache.org/jira/browse/CASSANDRA-16647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17338543#comment-17338543 ]
Ekaterina Dimitrova commented on CASSANDRA-16647:
-------------------------------------------------
LGTM
What I am thinking is maybe to stress on this sentence, like a warning or something - "If the patch is for an older branch, and doesn't impact later branches (such as trunk), *we still need to merge up.*" WDYT?
Also, in theory we can add how the author could be changed if the patch came from someone else. But that is not mandatory to land here or in any ticket. Just a random thought
> Update how_to_commit documentation after cassandra-4.0 branch
> -------------------------------------------------------------
>
> Key: CASSANDRA-16647
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16647
> Project: Cassandra
> Issue Type: Sub-task
> Components: Documentation/Website
> Reporter: Michael Semb Wever
> Assignee: Michael Semb Wever
> Priority: Normal
> Fix For: 4.0-rc
>
>
> - 3.11: https://github.com/apache/cassandra/compare/trunk...thelastpickle:mck/16642/3.11 (also backports CASSANDRA-16626)
> - cassandra-4.0: https://github.com/apache/cassandra/compare/trunk...thelastpickle:mck/16642/4.0
> - trunk: https://github.com/apache/cassandra/compare/trunk...thelastpickle:mck/16642/trunk
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org