= Defining Roadmaps What are the next steps required until the next MacPorts release(s)? After a lengty discussion, we identified the following work mode to track base tickets and where they are being released: * Base tickets are usually created without milestones. * When closing a ticket when a fix is pushed to master, set the milestone field to the milestone for the next feature release to indicate that is now fixed on master. * If the fix should be backported to a release branch, set the [query:status=closed&keywords=~needs-backport needs-backport] keyword. * When backporting to a release branch, set the ticket's milestone to the milestone for the next bugfix release. * If there are milestones missing, file a ticket against the trac component and request them. This documentation should be moved to the guide #56056. = Release Planning == MacPorts 2.4.3 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. [[TicketQuery(milestone=MacPorts 2.4.3)]] == MacPorts 2.4.4 [[TicketQuery(milestone=MacPorts 2.4.4)]] == MacPorts 2.5.0 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. [[TicketQuery(milestone=MacPorts 2.5.0)]] == MacPorts 2.6.0 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. [[TicketQuery(milestone=MacPorts 2.6.0)]] == MacPorts 2.7.0 [[TicketQuery(milestone=MacPorts 2.7.0)]] == Base tickets without a milestone [[TicketQuery(component=base&milestone=&status=assigned|new|reopened)]]