[1.34] Release Branch
FYI, we now have a RC_1_34_0 branch. Please focus on resolving the remaining issues on this branch. Thanks Thomas -- Thomas Witt witt@acm.org
Thomas Witt ha escrito:
FYI,
we now have a RC_1_34_0 branch. Please focus on resolving the remaining issues on this branch.
Thanks
Thomas
Two questions: * Which is the preferred protocol to commit changes to the RC branch? 1: commit to the trunk, then merge to RC_1_34_0 branch, following the instructions on http://boost.org/more/release_procedures.htm#Developers 2: commit directly to RC_1_34_0, the release manager will eventually merge back to trunk when the release is done. Although #1 is the documented procedure, at least in the 1.33.x we were doing #2 instead. I think a clarification would be very helpful. * Is there already an URL where we can browse regression test results for RC_1_34_0? Thank you, Joaquín M López Muñoz Telefónica, Investigación y Desarrollo
Joaquín Mª López Muñoz <joaquin@tid.es> writes:
Thomas Witt ha escrito:
FYI,
we now have a RC_1_34_0 branch. Please focus on resolving the remaining issues on this branch.
Thanks
Thomas
Two questions:
* Which is the preferred protocol to commit changes to the RC branch? 1: commit to the trunk, then merge to RC_1_34_0 branch, following the instructions on http://boost.org/more/release_procedures.htm#Developers 2: commit directly to RC_1_34_0, the release manager will eventually merge back to trunk when the release is done. Although #1 is the documented procedure, at least in the 1.33.x we were doing #2 instead. I think a clarification would be very helpful.
I have always done #1. If anyone was doing #2 it was not because of any agreed-upon plan to do so. -- Dave Abrahams Boost Consulting www.boost-consulting.com
David Abrahams wrote:
Joaquín Mª López Muñoz <joaquin@tid.es> writes:
Thomas Witt ha escrito:
FYI,
we now have a RC_1_34_0 branch. Please focus on resolving the remaining issues on this branch.
Thanks
Thomas Two questions:
* Which is the preferred protocol to commit changes to the RC branch? 1: commit to the trunk, then merge to RC_1_34_0 branch, following the instructions on http://boost.org/more/release_procedures.htm#Developers 2: commit directly to RC_1_34_0, the release manager will eventually merge back to trunk when the release is done. Although #1 is the documented procedure, at least in the 1.33.x we were doing #2 instead. I think a clarification would be very helpful.
I have always done #1. If anyone was doing #2 it was not because of any agreed-upon plan to do so.
I would say #1 is the preferred way. Thomas -- Thomas Witt witt@acm.org
participants (4)
-
David Abrahams -
Jim Douglas -
Joaquín Mª López Muñoz -
Thomas Witt