| | 1 | = Defining Roadmaps |
| | 2 | What are the next steps required until the next MacPorts release(s)? |
| | 3 | |
| | 4 | After a lengty discussion, we identified the following work mode to track base tickets and where they are being released: |
| | 5 | * Base tickets are usually created without milestones. |
| | 6 | * When closing a ticket when a fix is pushed to master, set the "MacPorts Future" milestone to indicate that is now fixed on master. |
| | 7 | * If the fix should be backported to a release branch, set the [query:status=closed&keywords=~needs-backport needs-backport] keyword. |
| | 8 | * When backporting to a release branch, set the ticket's milestone to the milestone for the next bugfix release. |
| | 9 | * If there are milestones missing, file a ticket against the trac component and request them. |
| | 10 | |
| | 11 | = Release Planning |
| | 12 | == MacPorts 2.4.3 |
| | 13 | We identified a need for a bugfix release from the 2.4.x branch, because trace mode is currently broken in 2.4.2 on High Sierra. The ticket for that is #55575. There was an email from Ryan a while ago that requested backporting a number of fixes as well. We created #56018 to track this. |
| | 14 | |
| | 15 | [[TicketQuery(milestone=MacPorts 2.4.3)]] |
| | 16 | |
| | 17 | == MacPorts 2.5.0 |
| | 18 | There are a number of features that we want to get done before the next major version release. We mostly picked branches with some code that don't need a lot of work to merged into master and simple tickets for this milestone. We did not want to set any far-reached goals for 2.5.0. |
| | 19 | |
| | 20 | [[TicketQuery(milestone=MacPorts 2.5.0)]] |
| | 21 | |
| | 22 | == MacPorts 2.6.0 |
| | 23 | We identified a number of features that we think should be the next step after 2.5.0 and added them to the 2.6.0 milestone. |
| | 24 | |
| | 25 | [[TicketQuery(milestone=MacPorts 2.6.0)]] |
