There is no merge-then-review. The work has been reviewed. This is identical to
how reviews work as normal.
If it helps your mental model, consider this a convenient atomic merge of many
Jira that have independently met the standard project procedural requirements,
as that is what it is.
Squas
But it's not merge-than-review, because they've already been reviewed,
before being merged to the feature branch, by committers (actually PMC
members)?
You want code that's been written by one PMC member and reviewed by 2 other
PMC members to be put up for review by some random 4th party? For
>
> The sooner it’s in trunk, the more eyes it will draw, IMO, if you are
> right about most contributors not having paid attention to a feature branch.
>
We all agree we want the feature branch incrementally merged sooner rather
than later.
IMHO any merge to trunk, and any rebase and squash of n
New failures from Build Lead Week 4:
*** CASSANDRA-18188 - Test failure in
upgrade_tests.cql_tests.cls.test_limit_ranges
- trunk
- AttributeError: module 'py' has no attribute 'io'
*** CASSANDRA-18189 - Test failure in
cqlsh_tests.test_cqlsh_copy.TestCqlshCopy.test_bulk_round_trip_with_timeouts
-
Hello everyone,
You can find the changes here:
https://issues.apache.org/jira/browse/CASSANDRA-17925
While preparing the code style configuration for the Eclipse IDE, I
discovered that there was no easy way to have complex grouping options
for the set of packages. So we need to add extra blank li
Super happy to see this happening. :-)
Le sam. 21 janv. 2023 à 00:08, Mick Semb Wever a écrit :
>
> I'll add the both of you, and anyone else that speaks up.
>
> To clarify, being a moderator to the mailing list is only about
> accepting/rejecting posts being sent from recipients that have not (
