Update CHANGELOG to mark v2.3.0 as released

[0xbrw]

Summary of Changes

Mark 2.3.0 as released

[t-nelson]

is 2.3 still supposed to point to edge?

[steviez]

In previous release, it seems we landed the "update changelog" PR prior to branching. Ie, #6424 came in after we cut v2.3 if I'm not mistaken.

So, I think just BP'ing 6424 would keep us consistent with past releases

[t-nelson]

yeah wasn't sure if BPing master update was right path or just deleting the channel indications

[steviez]

Yeah, I could see just deleting the channel indications as v2.3 does go from beta to stable at some point, and keeping it noted here is just another thing to remember to update get out of date.

[t-nelson]

@willhickey any guidance here?

[steviez]

@0xbrw - Per the discussion in above thread and some other discussion, we are going to follow this path:

• Historically, the change to increment versions has landed prior to branches being cut
  • For this go around, it was Update CHANGELOG.md for v3.0 #6424
  • That PR also removes the "Unreleased" item from the latest branch (2.3 in this case)
• This go around, that ordering was NOT kept so v2.3 branch was created before 6424 landed
• So, we're going to BP 6424 in order to keep the commit mapping as close as possible
  • Arguably overkill in this situation, but it is more proper and also more in line with how we do "actual code" backports
  • That backport is here: v2.3: Update CHANGELOG.md for v3.0 (backport of #6424) #6736

I'm going to close this PR out as we should have it all patched up once the BP PR lands; thanks for catching this !