Ticket #1849 (closed defect: wontfix)
Opened 2013-04-30T10:48:43-05:00
Last modified 2014-05-01T16:21:38-05:00
Let bump-pom-scijava increase the major version number when appropriate
| Reported by: | dscho | Owned by: | dscho |
|---|---|---|---|
| Priority: | major | Milestone: | imagej2-unscheduled |
| Component: | Build System | Version: | |
| Severity: | serious | Keywords: | |
| Cc: | curtis | Blocked By: | |
| Blocking: |
Description
At the moment, bump-pom-scijava always increases the minor version number whenever anything changed in the pom. But when we increase a dependency's version number to a new major version number (breaking API as per http://semver.org/), we need to increase the major version number of pom-scijava, too.
Change History
comment:1 Changed 2014-05-01T16:21:38-05:00 by curtis
- Status changed from new to closed
- Resolution set to wontfix
Major version bumps like that need a lot of manual management no matter what. There is probably no amount of tooling that will fully get us past that. And we probably don't want it to do so, even if it could—major version bumps should be "hard to do" to an extent.
There is a more general issue tracking improvements to our release process at:
https://github.com/scijava/pom-scijava/issues/2