Planning for the October 2023 release

[raman-m]

@RaynaldM @ggnaegi

I would like to understand the current release (October'23) scope of features. We will have less features than previous September'23 release, but it is OK, because I was busy with docs release (#1755) for a 2 weeks.

Let's plan the rest of work.

@ggnaegi

• #1744 Avoid calls to 'Logger.Log' if LogLevel not enabled in appsettings.json #1745
• #1550 #1706 Addressing the QoS options ExceptionsAllowedBeforeBreaking issue #1753
• no time to deliver more

@RaynaldM

• #1712 Bump to Polly 8.0 #1714
• Something else?

@raman-m From my side

• #952 #1174 Merge query strings without duplicate values #1182 by @wast
• and a few PRs by @jlukawska like
  • #651 Merge custom JSON properties across multiple ocelot.X.json configuration files using Newtonsoft's JToken merge functionality #1183
  • and maybe #842 AuthenticationOptions in GlobalConfiguration #1215

Please send me a feedback ASAP.

[ggnaegi]

@raman-m ok, I understand for the request mapper improvement and the polling - the two PRs are big -, but maybe maybe this one could still fit in: #1769 "Bad error handling for 413 payload too large"?

[raman-m]

• #749 Bad error handling for IOException while reading incoming request body #1769

Hmm... The PR is linked to low priority bug. It is not reviewed at all... Have all tests? Need to update docs?

[raman-m]

Looks like you will have some time to polish it up, right?
Include in Nov'23 release?

[RaynaldM]

on my side, it is ok.
We're going to migrate to .net 8, I plan to migrate Ocelot to .net 8 in January (and I'll try to make it compatible with 6 and 7).

[raman-m]

I meant not future releases, I mean current October's release: the features we've merged to develop... 😄
If you've prepared some PRs as ready for review, as a candidate to merge, then It is definetly right time to show it to the team...

---

We're going to migrate to .net 8, I plan to migrate Ocelot to .net 8

Yes, we will... But .NET 8 will be released in a month officially, at the end of this November... It is impossible to do this migration in November's release, but it would be better to start migration as soon as possible. So, I believe we need to make migration and include this at least in December's release. But.... technically it is possible to make migration even for November's release.
We will discuss that... Now I'm focusing on current October's release trying to add more features, if possible.

[RaynaldM]

sorry for my bad english, I have said "I plan to migrate Ocelot to .net 8 in January"

[raman-m]

I've got it! ...in 2024

[ggnaegi]

.NET 8 will be released in 10 days, it's the new LTS version, we could try to push something before the end of the month and start the review process...

[ggnaegi]

@raman-m what about #1580?

[raman-m]

Linked PR #1666 has unit tests only. A few acceptance tests should be added.
Also, it seems, the docs must be reviewed and updated...
Ask the author? Maybe he will write acceptance tests, but he won't update docs... I explained him a lot how to move this PR forward...
I am afraid it is not ready for October's release... probably it will be included in November release.
More collaboration is required...

[raman-m]

Hi @ggnaegi !
Do you think that #1580 (#1666) is a good candidate for November release?

[ggnaegi]

@raman-m yes, it would be a good candidate for the release.

[raman-m]

Added it to Nov'23 release

[raman-m]

• Release 22.0 #1805