Ticket #1842 (closed task: wontfix)
Change version of MC 4.7.0 to 5.0 to signify the changes
| Reported by: | birdie | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | adm | Version: | master |
| Keywords: | major version release | Cc: | |
| Blocked By: | Blocking: | ||
| Branch state: | no branch | Votes for changeset: |
Description
We've all been using mc 4.x.x for the last 12 years, I believe with the amount of changes taking place in a post 4.6.2 time frame you may give your product a major boost in a version number.
BTW, old versions of MC can be found here:
Change History
comment:2 Changed 15 years ago by slavazanko
- Keywords major version release added
- Type changed from defect to task
- Component changed from mc-core to adm
- Milestone changed from 4.7 to Future Releases
Yep, exactly. change of major number in version will make sence after huge changes into project, like as: adding plugins support; rework of vfs-stuff; big refactoring etc.
Now we have changes for increment minor number of version... but IMHO these don't enought for change major version.
Note: See
TracTickets for help on using
tickets.
IMO does not make any sense to do this for 4.7.0 release. I think it might be a good idea after the VFS rewrite and refactoring are completed, but so far, there've been much work under the hood, but it's just another release with major changes and possibly many stabilization cuts (4.7.1, 4.7.2) etc. coming shortly.