Re: Merging CEP-15 to trunk

[Benedict]

These tickets have all met the standard integration requirements, so I’m just unclear what “higher pre-commit gateway” you are referring to. I think the existing epics are probably more natural tickets to reference in the merge, eg 17091 and 17092. On 20 Jan 2023, at 11:04, Mick Semb Wever <m...@apache.org> wrote:  On Tue, 17 Jan 2023 at 10:29, Benedict <bened...@apache.org> wrote: but the pre-commit gateway here is higher than the previous tickets being worked on Which tickets, and why? All tickets resolved in the feature branch to which you are now bringing from feature branch into trunk.  A quick scan I see… 17103, 17109, 18041, 18056, 18057, 18087, 17719, 18154, 18142, 18142. All these tickets are resolved but have not been merged to trunk, and they have no fixVersion. Assuming that it won't be a merge as-is (e.g. ninja-fixes will get squashed), i think a task ticket for the clean up of the feature branch and merge of it to trunk warrants a separate ticket. Such a ticket also helps with the admin (linking to the tickets the merge is bringing in).