I'll be assisting James with tech/git/svn support for the release. 👋
First to clarify, James's point about ticket hygiene and traceability
stands, but I believe we're talking about PRs, not commits?
I see 458 commits from the last release to the tip of develop (presumably
where we'll branch for v1.11 today) using:
git log --oneline 1.10.0...develop | wc
(someone please correct me if that's the wrong query)
As for PRs, I'm seeing roughly 376 using this naive query:
git log 1.10.0...develop | grep FINERACT | wc
I don't recommend specifically limiting/restricting commits.
On Thu, Feb 27, 2025 at 8:01 PM James Dailey <jdai...@apache.org> wrote:
> All - Update: We are still working on this release. I anticipate looking
> for a stable checkpoint, which likely be Friday, Feb 28th at 9am PST.
>
> While I would like to have a better result, it appears that we are unable
> to use the time machine to go back and do the needful thing.
>
> We did not enforce a one ticket means one commit or one ticket means no
> more than four commits. Going forward, let's try to have the tickets
> reflect what the commit is doing.
>
> So, we have 35 tickets and 350 commits, which is not a good way to have
> traceability from tickets to commits, but at least all commits should have
> a reference (still verifying that), and we will work to provide "pretty
> good" release notes. We will also endeavor to have - this time around -
> the documentation to be generated for the release.
>
> So, please stay tuned.
>
> Again, please see below for the official notice of this upcoming
> release... I am the release manager.
>
