<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">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>
Obviously, this is another chance but mandatory to resolve issues
with upgrading from installer packages on FreeBSD and Debian OSes.<br>
<br>
Following are the changes I've cherry-picked into the release
branch since beta 1. <br>
<br>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
DMD<br>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
[REG2.061] Issue 11980 - startaddress pragma broken (pull request
#3142)<br>
Issue 11974 - ICE(cast.c) Segfault with invalid assignment (pull
request #3141)<br>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
[REG2.065a] Issue 11966 - inout(const(char))[] doesn't convert to
inout(char)[] (pull request #3138)<br>
fix Issue 11956 - dmd doesn't lookup /etc/dmd.conf (pull
request #3128)<br>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
Issue 11968 - ICE(expression.c) Crash when deleting __FILE__ (pull
request #3139)<br>
Issue 11944 - ICE(expression.c) Assertion `f' failed. (pull
request #3125)<br>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
fix Issue 11922 - [REG2.065a] ICE on nonexistent identifier in
templated auto method (pull request #3094)<br>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
[REG2.065a] Issue 11924 - inout Variadic Template Parameters (pull
request #3097)<br>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
[REG2.065a] Issue 11896 - isVirtualMethod related GitHub HEAD
regression (pull request #3104)<br>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
[REG2.065a] Issue 11930 - Alias this not considered in is(T
unused: U) matching (pull request #3105)<br>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
[REG2.065a] Issue 11931 - Linkers "Symbol Undefined" again with
dmd HEAD when -g specified (pull request #3107)<br>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
[REG2.065a] Issue 11941 - Errors when appending to aggregate
member array in CTFE (pull request #3112)<br>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
[REG2.065a] Issue 11967 - ICE(parse.c) Parser crash (pull request
#3137)<br>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
[REG2.064] Issue 11965 - Segfault on garbage (pull request #3136)<br>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
[REG2.065a] Issue 11963 - ICE(parse.c) Parser crash (pull request
#3135)<br>
<br>
Druntime<br>
None<br>
<br>
Phobos<br>
Remove duplicate ArchiveMember.madeVersion() property.<br>
<br>
Installer<br>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
Build the installer GUI for D2 on OS X (pull request #44)<br>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
add "dustmite" binary on deb/rpm packages (pull request #43)<br>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
don't zip .git* and .DS_Store files (pull request #42)<br>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
fix expanding zip files created on Windows (pull request #41)<br>
cleanup leftover from merge conflict (pull request #40)<br>
<br>
dlang.org<br>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
fix chmgen after renaming phobos.html => index.htm (pull
request #480)<br>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
Revert changelog.dd encoding to UTF-8 (pull request #478)<br>
Changelog: add notes about std.uni.byGrapheme and
std.range.only (pull request #477)<br>
2.065 changelog (pull request #476)<br>
<br>
tools<br>
None<br>
<br>
If important you are expected to be included are not on the list,
please identify them so I can adjust accordingly.<br>
<br>
<br>
On 1/23/14, 11:03 PM, Brad Roberts wrote:<br>
</div>
<blockquote cite="mid:52E1E608.6070508@puremagic.com" type="cite">On
1/23/14 2:17 PM, Brad Anderson wrote: <br>
<blockquote type="cite">On Thu, Jan 23, 2014 at 2:55 PM, Andrew
Edwards <<a class="moz-txt-link-abbreviated" href="mailto:edwards.ac@gmail.com">edwards.ac@gmail.com</a>
<a class="moz-txt-link-rfc2396E" href="mailto:edwards.ac@gmail.com"><mailto:edwards.ac@gmail.com></a>>
<br>
wrote:
<br>
<br>
On 1/23/14, 2:01 PM, Walter Bright wrote:
<br>
<br>
I agree, I don't know what's wrong with what we had
before:
<br>
<br>
1. All pull requests get merged to master
<br>
2. Create 2.065 branch
<br>
3. Cherry-pick from master to 2.065 as required
<br>
4. Tag 2.065.whatever as releases get done on that
branch
<br>
<br>
Easy, simple. All these other procedures seem like
massive over-engineering to me.
<br>
<br>
Good to go... I for one did not see either of you weigh in
on the proposal when Brad Roberts
<br>
<br>
<br>
Brad Anderson :P
<br>
<br>
made it
<br>
(<a class="moz-txt-link-freetext" href="http://forum.dlang.org/post/__CAFU1Uzpm4DBADOxMjcJ_Guj1=__T8BQ4nPb5OEbADNbUQDD2ijuQ@__mail.gmail.com">http://forum.dlang.org/post/__CAFU1Uzpm4DBADOxMjcJ_Guj1=__T8BQ4nPb5OEbADNbUQDD2ijuQ@__mail.gmail.com</a><br>
<a class="moz-txt-link-rfc2396E" href="http://forum.dlang.org/post/CAFU1Uzpm4DBADOxMjcJ_Guj1=T8BQ4nPb5OEbADNbUQDD2ijuQ@mail.gmail.com"><http://forum.dlang.org/post/CAFU1Uzpm4DBADOxMjcJ_Guj1=T8BQ4nPb5OEbADNbUQDD2ijuQ@mail.gmail.com></a>).<br>
I decided to use it because, compared to the alternative of
trying to convince volunteers to do
<br>
something they do not want to, it would be much simpler for
me to follow this scheme.
<br>
<br>
<br>
I wish I would have thought to email Brad directly (sorry, Brad)
to make sure he saw it and could
<br>
weigh in. Especially since apart from you he's really the only
other person that needs to change
<br>
anything to adopt this workflow.
<br>
<br>
<br>
To me there is no difference between the two processes,
except the "we've always done it this
<br>
way syndrome". Fixes are generated from release tags into a
hotfix branch. Once the fix is
<br>
released, we merge it back into master, remove the branch
and move on. I am preparing both
<br>
releases and hotpicks so I don't see any extra work being
generated for the devs.
<br>
<br>
The only chance I see on your parts is the need to change
the tester scripts to point search for
<br>
and test "hotfix" and "release" branches if they exist. I'm
not the person doing that so I might
<br>
have an overly simplified view of your processes but I
really don't see the big deal.
<br>
<br>
<br>
If Brad Roberts decides it's too hard for whatever reason we
should be able to just change the
<br>
workflow over to use a versioned branch name and dropping the
step where the branch is deleted. Then
<br>
the hotfix process would just checkout the versioned branch (and
skip the delete as well). I like
<br>
the tag and delete method better but we can't sacrifice the
autotester for that.
<br>
</blockquote>
<br>
The problem is that as specified, _every_ fix requires also
setting up builds in the auto-tester (regardless of who does it).
That should be once per maintained version. Deleting and
recreating is a waste of everyone's time. <br>
<br>
It's not just me that's affected. Anyone who wants to test
releases as they're being built has to carefully track what branch
to use when, which is tedious and a waste of time. <br>
<br>
Also, what if we decide to patch two past releases, does that
happen serially, using the release branch name for each of the
versions one at a time? Also stupid and a waste of time. <br>
<br>
Should I continue or is it obvious now? <br>
<br>
_______________________________________________ <br>
dmd-beta mailing list <br>
<a class="moz-txt-link-abbreviated" href="mailto:dmd-beta@puremagic.com">dmd-beta@puremagic.com</a> <br>
<a class="moz-txt-link-freetext" href="http://lists.puremagic.com/mailman/listinfo/dmd-beta">http://lists.puremagic.com/mailman/listinfo/dmd-beta</a> <br>
</blockquote>
<br>
</body>
</html>