|WARNING| [v2] version: 26.11.0-rc0

[dpdklab at iol.unh.edu]

Test-Label: ai-code-review
Test-Status: WARNING
https://dpdk.org/patch/166874

_AI Code Review_

=== Patch Review: series.patch (via Claude) ===
Review date: 2026-07-23

# DPDK Patch Review

## Summary

This patch starts a new DPDK release cycle (26.11.0-rc0) by updating version numbers, ABI version, and creating empty release notes. It also bumps symbol version compatibility markers from version 26 to version 27 in ethdev and net/mlx5 as a temporary measure before removing the compatibility entirely in subsequent commits.

## Review Findings

### Correctness Issues

None found. This is a straightforward version bump patch with no functional code changes.

### Style and Process

#### **Warning: Release notes file naming inconsistency**

The release notes file is named `release_26_11.rst` but the version in `VERSION` is `26.11.0-rc0`. While DPDK typically uses underscore-separated version numbers in documentation filenames, verify this matches the established pattern for release notes. Previous releases in the index show `release_26_07`, `release_26_03`, `release_25_11`, so the naming appears consistent with the pattern.

#### **Info: Symbol version bump justification**

The commit message states: "Note: we need to bump the version for symbol compat in ethdev and net/mlx5 temporarily. Next commits will drop this compat entirely."

This is acceptable as a transitional state. The symbol version bumps from 26 to 27 in:
- `drivers/net/mlx5/mlx5_driver_event.c` (2 functions)
- `drivers/net/mlx5/mlx5_flow.c` (2 functions)  
- `lib/ethdev/rte_flow.c` (1 function)

are consistent with the ABI version change from 26.2 to 27.0. The temporary nature is clearly documented.

### Documentation

**Info: Empty release notes sections**

The newly created `doc/guides/rel_notes/release_26_11.rst` contains only template comments and no actual content. This is acceptable for an initial release cycle start commit. The comments provide clear guidance for future contributors on how to populate each section.

**Verification needed: Release notes index order**

The release notes are added to the index in chronological order:
```rst
release_26_11
release_26_07
release_26_03
release_25_11
```

This appears correct for a new development cycle.

### Build System Changes

**Info: CI configuration updates**

The `.github/workflows/build.yml` changes are appropriate:
- `REF_GIT_TAG` changed from `v26.03` to `none` - correct for disabling ABI compatibility checks at the start of a new cycle
- Removed `abi+` from the checks string - consistent with the commit message stating "CI ABI checks are disabled because compatibility is not preserved"

### ABI and API

**Info: ABI exceptions cleared**

The `devtools/libabigail.abignore` file has its temporary exceptions removed (the `rte_eth_rxseg_capa` struct suppression). This is correct at the start of a major ABI version bump where compatibility is not preserved.

**Info: ABI version increment**

The ABI version change from `26.2` to `27.0` follows DPDK versioning policy:
- Major version incremented (26 - 27)
- Minor version reset to 0
- This signifies a major ABI break, which is expected at the start of a new development cycle

## Conclusion

**No errors found.** This patch correctly implements the mechanical changes needed to start a new DPDK release cycle. The version bumps, empty release notes template, disabled ABI checks, and temporary symbol version updates are all appropriate for this context. The commit message clearly explains the temporary nature of the symbol version changes and indicates they will be removed in subsequent commits.