<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 1/24/14, 8:47 AM, Andrew Edwards
wrote:<br>
</div>
<blockquote cite="mid:52E26EFB.6030109@gmail.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<div class="moz-cite-prefix">The branch will be renamed tonight in
preparation for building beta 2. I will make this change start
building beta 2 at 10:00PM EST (UTC -5) so please ensure the
auto tester is not using the release branch in order prevent any
complications when it is renamed. Also just to verify that I am
not causing any additional issues, the tags (aka version
numbers) for the release will be as follows:<br>
<br>
2.65.0-b2<br>
<br>
</div>
</blockquote>
I may not have been all there this morning when I wrote this
response. Here's what will be happening:<br>
<br>
1) The "release" branch will be renamed "2.65.0"<br>
2) The next tag will be "v2.65.0-b2"<br>
3) The beta 1 tag will NOT be renamed.<br>
<br>
The one question I have remaining is: Are there any issues with
removing the leading zero from the minor release number? Should it
be 2.065.0 instead?<br>
<br>
Hopefully, with the answer to the previous question, this puts an
end to all discussions pertaining to branching, tags, and naming
contentions so we can focus on the things that really matter.<br>
</body>
</html>