Update release notes for 26.2

Author: oguzkocer

CLAUDE.md

@@ -6,7 +6,7 @@ This file provides guidance to Claude Code (claude.ai/code) when working with co
 
 ### Main Build Commands
 - `./gradlew assembleWordPressVanillaDebug` - Build debug APK for WordPress app
-- `./gradlew assembleJetpackVanillaDebug` - Build debug APK for Jetpack app  
+- `./gradlew assembleJetpackVanillaDebug` - Build debug APK for Jetpack app
 - `./gradlew installWordPressVanillaDebug` - Install debug APK to connected device
 - `./gradlew installJetpackVanillaDebug` - Install debug APK for Jetpack to device
 
@@ -38,7 +38,7 @@ This repository builds two apps from shared codebase:
 ├── WordPress/                 # Main app module
 ├── libs/
 │   ├── fluxc/                 # Networking and data layer (FluxC architecture)
-│   ├── login/                 # Shared login functionality  
+│   ├── login/                 # Shared login functionality
 │   ├── editor/                # Block editor integration
 │   ├── image-editor/          # Image editing functionality
 │   ├── analytics/             # Analytics and tracking
@@ -61,7 +61,7 @@ WordPress/src/main/java/org/wordpress/android/
 ├── ui/                        # UI layer organized by feature
 │   ├── posts/                # Post creation and management
 │   ├── reader/               # Content discovery and reading
-│   ├── stats/                # Site analytics and statistics  
+│   ├── stats/                # Site analytics and statistics
 │   ├── bloggingreminders/    # Posting reminders system
 │   ├── comments/             # Comment management
 │   ├── accounts/             # Authentication and signup
@@ -85,7 +85,7 @@ WordPress/src/main/java/org/wordpress/android/
 ### Code Quality Tools
 - Android Code Style Guidelines with project-specific Checkstyle and Detekt rules
 - **Checkstyle**: Java code style enforcement (`config/checkstyle.xml`)
-- **Detekt**: Kotlin code analysis (`config/detekt/detekt.yml`) 
+- **Detekt**: Kotlin code analysis (`config/detekt/detekt.yml`)
 - **Android Lint**: Built-in Android static analysis
 - **Line Length**: 120 characters max
 - **No FIXME**: Use TODO instead of FIXME in committed code
@@ -97,4 +97,71 @@ WordPress/src/main/java/org/wordpress/android/
 - Remote build cache available for faster builds (requires setup)
 - Fastlane used for release automation and testing
 - Secrets managed via `secrets.properties` file (not in repo)
-- Pre-commit hooks may modify files during commit
+- Pre-commit hooks may modify files during commit
+
+## Release Notes Compilation Process
+
+### Overview
+Process for compiling release notes for new versions, ensuring they meet Play Store character limits (under 500, preferably 350-400) and maintain the established playful tone.
+
+### Step-by-Step Process
+
+#### 1. Study Previous Release Notes Style
+Use `gh` to fetch releases and analyze professional editorialization patterns:
+- **Version 25.8**: Raw added in commits `8cd1b4cc268887b9e2de94fb19afc108b011f0da` & `93591923dd9a9c144729952ad0dfbc9306f69894`, editorialized in `8a7fc316cf0acfc2b88b1090e3ca148f2145fa92`
+- **Version 25.9**: Raw added in `b4a292cc9c9a30823bfdf8e770479a68362ed500`, editorialized in `dad8fa582856758999c43384ccbe55f34b6d2e17`
+- **Version 26.0**: Raw added in `a53234ea6b13adf18acac262ad985f94308191c6` & `63067fb7249cc860d44547bb0d1b8dee975dbe8e`, editorialized in `02854d67c42146e611f0f0dff9feb0fd48dc7fd8`
+
+Commands: `gh release view 25.8`, `gh release view 25.9`, `gh release view 26.0` (note: no 'v' prefix)
+
+#### 2. Verify Release Branch and Get Last Release Hash
+- Verify current branch follows naming: `release/x.y` (where x.y = last_release + 0.1)
+- Get commit hash for last release: `gh release view <last_version> --json tagName,targetCommitish`
+- Confirm current branch is properly ahead of last release tag
+
+#### 3. Identify Changes Since Last Release
+Compare current release branch against last release hash:
+```bash
+git log <last_release_hash>..HEAD --oneline --no-merges
+```
+Focus on user-facing changes from squash commit messages. **Important**: When commit messages are unclear or technical, always investigate further:
+- Use `gh pr view <PR_number>` to read PR titles and descriptions
+- Look for keywords indicating user-facing changes: "feat:", new functionality, UI changes, user experience
+- Be especially careful with feature rollouts that may have technical-sounding commit messages but represent new user functionality
+- When in doubt, investigate the PR rather than excluding potentially important features
+
+#### 4. Compile Raw Release Notes
+Create factual summary including:
+- Only user-facing changes (exclude CI, refactoring, technical debt)
+- Prioritize: New features → Improvements → Performance enhancements
+- Use positive language (avoid "bug fix", prefer "improved", "enhanced", "resolved")
+- Include rough character counts to gauge condensation needed
+- Mark changes as WordPress-specific, Jetpack-specific, or both
+
+#### 5. User Confirmation
+Present raw notes to user for:
+- Accuracy verification
+- WordPress vs Jetpack feature classification
+- Any missing or incorrect changes
+- Approval to proceed with editorialization
+
+#### 6. Editorialization
+Transform raw notes using established playful style:
+- Keep under 350 characters (accounting for translation expansion)
+- Use engaging, user-friendly language
+- Reference previous release note styles from step 1
+- Create separate versions for WordPress and Jetpack apps
+- Focus on user benefits and experience improvements
+
+#### 7. Update Release Notes Files
+Once user confirms the editorialized release notes, **replace** the contents of the following files (discard any existing content):
+- **WordPress release notes**: `WordPress/metadata/release_notes.txt`
+- **Jetpack release notes**: `WordPress/jetpack_metadata/release_notes.txt`
+
+Document any process refinements discovered during execution.
+
+### Content Guidelines
+- **Include**: New features, UI improvements, performance enhancements, user experience changes
+- **Exclude**: CI changes, code refactoring, dependency updates, internal technical changes
+- **Language**: Positive sentiment, avoid "fix" terminology, focus on improvements and enhancements
+- **Priority Order**: New features → Improvements → Performance → Other user-facing changes

WordPress/jetpack_metadata/release_notes.txt

@@ -0,0 +1,3 @@
+- Connect your self-hosted sites to Jetpack with our new streamlined flow—available right from Stats and Notifications.
+- We've added support for mentions in the editor—tag your friends and collaborators with ease.
+- Media selection just got more accessible for everyone.

WordPress/metadata/release_notes.txt

@@ -0,0 +1,2 @@
+- We've added support for mentions in the editor—tag your friends and collaborators with ease.
+- Media selection just got more accessible for everyone.