|
|
|
|
|
|
by withinboredom
852 days ago
|
|
|
Making 0.* special, doesn't actually fix the issue I'm describing, but just pushes it to 2.0. Example: now that 1.0 is released, I want to add two new massively breaking changes. The team opens two PRs. The first one merges and bumps the version to 2.0, then the next one merges, and it gets bumped to 3.0. That sounds ridiculous. |
|
|