Is the release branch closed for changes for 1.46.0? If it is, may I have permission to merge change [68291] - which fixes two spelling errors in the parameter library docs? https://svn.boost.org/trac/boost/ticket/4983 -- Marshall Marshall Clow Idio Software <mailto:mclow.lists@gmail.com> A.D. 1517: Martin Luther nails his 95 Theses to the church door and is promptly moderated down to (-1, Flamebait). -- Yu Suzuki
On 1/19/2011 10:35 PM, Marshall Clow wrote:
Is the release branch closed for changes for 1.46.0?
If it is, may I have permission to merge change [68291] - which fixes two spelling errors in the parameter library docs? https://svn.boost.org/trac/boost/ticket/4983
Yes, we're frozen, but that's only for source, tests, tools, and build files. I don't think you need to ask permission to merge doc fixes ever. Just don't break the doc build, please. :-) -- Eric Niebler BoostPro Computing http://www.boostpro.com
On Wed, Jan 19, 2011 at 11:12 AM, Eric Niebler <eric@boostpro.com> wrote:
On 1/19/2011 10:35 PM, Marshall Clow wrote:
Is the release branch closed for changes for 1.46.0?
If it is, may I have permission to merge change [68291] - which fixes two spelling errors in the parameter library docs? https://svn.boost.org/trac/boost/ticket/4983
Yes, we're frozen, but that's only for source, tests, tools, and build files. I don't think you need to ask permission to merge doc fixes ever. Just don't break the doc build, please. :-)
Right, although when I'm actively building release candidates there needs to be an absolute freeze. Otherwise we could have problems like Unix and Windows release files differing by other than just line endings. --Beman
On Wed, Jan 19, 2011 at 6:06 PM, Beman Dawes <bdawes@acm.org> wrote:
Right, although when I'm actively building release candidates there needs to be an absolute freeze. Otherwise we could have problems like Unix and Windows release files differing by other than just line endings.
The simplest way to avoid that is to specify which revision use. /$
On Wed, Jan 19, 2011 at 3:56 PM, Henrik Sundberg <storangen@gmail.com>wrote:
On Wed, Jan 19, 2011 at 6:06 PM, Beman Dawes <bdawes@acm.org> wrote:
Right, although when I'm actively building release candidates there needs to be an absolute freeze. Otherwise we could have problems like Unix and Windows release files differing by other than just line endings.
The simplest way to avoid that is to specify which revision use.
/$
Good suggestion. I'll take a stab at updating the scripts. Thanks, --Beman
participants (4)
-
Beman Dawes -
Eric Niebler -
Henrik Sundberg -
Marshall Clow