case 4690 - version bump and confirmation of choices for net10-port
This commit is contained in:
@@ -9,7 +9,7 @@ under "Deferred", not into the branch.
|
||||
| Starting point | AyaNova 8.2.4: ASP.NET Core 8, EF Core 8 |
|
||||
| Target | `net10.0`, every back-end package at its current release |
|
||||
| Front end | Minimal or no change. Rebuild only if needed (open question) |
|
||||
| Branch | `net10-port` in `raven` (and `raven-client` only if the client changes) |
|
||||
| Branch | `net10-port` in `raven` (and `raven-client` and `raven-test-integration` and `raven-launcher`) |
|
||||
| Baseline tag | `net8-baseline`, on the last commit before the port |
|
||||
| Release version | Not yet decided (open question) |
|
||||
|
||||
@@ -104,7 +104,7 @@ them. Items touching those three areas carry more weight here than they did in S
|
||||
|
||||
These are bugs, not port mechanics, so each is a separate commit that can be reverted alone.
|
||||
Sockeye included its equivalents in the port branch. John decides per item whether they go
|
||||
in this branch or a follow-up release.
|
||||
in this branch or a follow-up release. UPDATE: John has decided these all go in this branch and some more additional cases in the case database that are urgent, exact cases TBD.
|
||||
|
||||
- [ ] **Case 4676: data-list SQL injection — priority.** The numeric and role filters in `DataListSqlFilterCriteriaBuilder` built SQL from input. In AyaNova any authenticated user who can open a data list could reach them. Port the Sockeye fix
|
||||
- [ ] **`DbUtil.AdminConnectionString`.** If it is `_dbConnectionString.Replace(_dbName, "postgres")`, any customer whose role name, password or host contains the database name as text gets a mangled admin connection, and the boot check authenticates as the wrong user. Fix: `new NpgsqlConnectionStringBuilder(cs) { Database = "postgres" }.ConnectionString`
|
||||
@@ -159,10 +159,10 @@ suite is waiting on (case 4653, case 4654, the contract issue).
|
||||
|
||||
## Open questions
|
||||
|
||||
- Release version number (Sockeye's port was released as 8.1.0)
|
||||
- `raven-launcher` (.NET 8, self-contained): move to .NET 10 in the same release?
|
||||
- `raven-test-integration`: move to `net10.0` (separate commit) or leave on `net8.0`? It only talks HTTP to the server
|
||||
- Does the client need a rebuild in this pass, or can its current output be carried across?
|
||||
- Release version number (Sockeye's port was released as 8.1.0) Answer: 8.3.0 will be the version
|
||||
- `raven-launcher` (.NET 8, self-contained): move to .NET 10 in the same release? Answer: Yes
|
||||
- `raven-test-integration`: move to `net10.0` (separate commit) or leave on `net8.0`? It only talks HTTP to the server Answer: Move to net10.0 for consistency
|
||||
- Does the client need a rebuild in this pass, or can its current output be carried across? Answer: yes it will have minor changes as well as version number to 8.3.0
|
||||
- Section 3: which fixes go in this branch, which in a follow-up
|
||||
- How the .NET 10 runtime gets onto Ubuntu 24.04 hosts
|
||||
|
||||
|
||||
Reference in New Issue
Block a user