# RC Versioning Standard

## Golden Rule

**ALWAYS start from rc.0**

## Versioning Convention

### First RC Release
- ✅ Correct: `0.3.14-rc.0`
- ❌ Wrong: `0.3.14-rc.1` (never start with rc.1)

### Subsequent RC Releases (after test failure)
- First RC fails → `0.3.14-rc.1`
- Second RC fails → `0.3.14-rc.2`
- Third RC fails → `0.3.14-rc.3`
- ... and so on

## Examples

### Scenario 1: Success on First RC
```
0.3.14-rc.0 → Test → ✅ PASS → Merge to develop
```

### Scenario 2: First RC Fails
```
0.3.14-rc.0 → Test → ❌ FAIL (bug-00000021)
  → Exclude bug-00000021
  → 0.3.14-rc.1 → Test → ✅ PASS → Merge to develop
```

### Scenario 3: Multiple Failures
```
0.3.14-rc.0 → ❌ FAIL (bug-00000021, bug-00000027)
  → Exclude both
  → 0.3.14-rc.1 → ❌ FAIL (bug-00000031)
    → Exclude bug-00000031
    → 0.3.14-rc.2 → ✅ PASS → Merge to develop
```

## Branch Naming

- RC branch: `release/{version}-rc.{N}`
- Examples:
  - `release/0.3.14-rc.0`
  - `release/0.3.14-rc.1`
  - `release/0.3.14-rc.2`

## Common Mistakes

❌ **DON'T:**
- Start with rc.1 (should be rc.0)
- Skip rc numbers (rc.0 → rc.2)
- Use different versioning schemes

✅ **DO:**
- Always start with rc.0
- Increment sequentially (rc.0 → rc.1 → rc.2)
- Use consistent naming across all tools and agents