Remember, any committer can add an agenda item. Typically, short announcements or news items go in the "Announcements" section at the beginning. Longer items or issues requiring discussion should go in the "Other business" section at end.

In brief, while you are doing ONLY maintenance (so maintenance and "next major release"
are exactly the same code) you can develop in only HEAD, but just be sure to release to the branched map files.
You can merge (or "compare") HEAD map files with branched map files, so they have the exact same version tags
in both map files ... that is, there is no need to "release" twice (should have exact same version and qualifier in both builds,
if code is really exactly the same).

Remember to bump service field version ... normally +1, if destined for WTP 3.2.1, +100 only required if doing service for next major release, that will not be in a service release.

Once maintenance and "next major release" code streams start to differ, we have agreed, in the
past, that code in the same map file, should all be branched together, at the same time, and comments in the map file updated.
This makes it easier for others to "load up" an environment for what ever stream they are working on,
where as if done bundle by bundle, no one can easily figure that out what's what.