On 2016-11-12 17:39, Ryan Schmidt wrote: > Many of the changes in 2.3.5 are to deal with the GitHub transition, so I > would be in favor of releasing this change now as well.
https://github.com/macports/macports-base/blob/release-2.3/ChangeLog That would be only the warning on 'port sync' for users of SyncingWithSVN and the 'port lint' warning for the $Id$ tag. We should get these out quickly now, so users will be notified that they need to change their sources.conf. > Perhaps it should more properly be called 2.4, but since our master is in no > fix state to be branched for 2.4 at this time and we are still figuring out > our release process on GitHub, it might be simpler to do this next release > from the 2.3 branch and call it 2.3.5. The new ReleaseProcess should be ready now, except for the details of attaching distfiles to tags/releases on GitHub. master is definitely not in a state to be released, but the roadmap should be discussed separately. Changing the maintainers would be the only breaking change we would add. If we say this absolutely requires a new 2.x release, we could also branch release-2.4 from release-2.3 and call the next release 2.4.0. For the multi-valued maintainers itself, I still do not like its verbosity in 'port info', but I am also out of new ideas how to improve it. As the internal Portfile representation is now set and I am not aware of any third-party software that would be affected by the maintainers change, I would also be fine with including it in 2.3.5. Rainer
