I think we should release 2.063.1, for these reasons:

- Regression bug 9122 is not actually fixed in 2.063 release although it's listed in fixed Phobos regressions

  Because current 2.063 release does not contain the fix for issue 10017.

https://github.com/D-Programming-Language/phobos/commit/9a7627776e7cffa999f30e5a7450fb7f044a12f7

  Actually that was the root cause of 9122, so it should have been
contained in 2.063 release.

- 2.063 release has some regressions which was discovered after releasing.

  Issue 10215 - [REG2.063] const causes wrong float calculation

    This is serious wrong-code bug. This bug does not exist in git master.
    To fix the bug, we just need to recreate release package.
    Read my comment:  http://d.puremagic.com/issues/show_bug.cgi?id=10215

  Issue 10212 - [REG2.061] Segfault in mismatching delegate literal types

    It's old regression bug, but should be fixed as soon as possible.
    Please review and merge
https://github.com/D-Programming-Language/dmd/pull/2101

  Issue 10197 - [REG2.063] Cannot cast overloaded template property result

    Already fixed in git master.

From now I'll push some trivial changes to 2.063 branch which I think these are necessary for 2.063.1.

And I'll remove 2.063.1 tags for a moment. I think tagging should be done after the release done, but it's not yet released.

Kenji Hara

1. We already have a 2.063.1 released. An update would be 2.063.2.

2. I'd prefer to wait a bit to collect any more regressions before rushing out with an update.

On 6/1/2013 11:25 AM, Kenji Hara wrote:
> I think we should release 2.063.1, for these reasons:
>
> - Regression bug 9122 is not actually fixed in 2.063 release although it's listed in fixed Phobos regressions
>
>   Because current 2.063 release does not contain the fix for issue 10017.
> https://github.com/D-Programming-Language/phobos/commit/9a7627776e7cffa999f30e5a7450fb7f044a12f7
>
>   Actually that was the root cause of 9122, so it should have been contained
> in 2.063 release.
>
> - 2.063 release has some regressions which was discovered after releasing.
>
>   Issue 10215 - [REG2.063] const causes wrong float calculation
>
>     This is serious wrong-code bug. This bug does not exist in git master.
>     To fix the bug, we just need to recreate release package.
>     Read my comment: http://d.puremagic.com/issues/show_bug.cgi?id=10215
>
>   Issue 10212 - [REG2.061] Segfault in mismatching delegate literal types
>
>     It's old regression bug, but should be fixed as soon as possible.
>     Please review and merge
> https://github.com/D-Programming-Language/dmd/pull/2101
>
>   Issue 10197 - [REG2.063] Cannot cast overloaded template property result
>
>     Already fixed in git master.
>
> From now I'll push some trivial changes to 2.063 branch which I think these are necessary for 2.063.1.
>
> And I'll remove 2.063.1 tags for a moment. I think tagging should be done after the release done, but it's not yet released.
>
> Kenji Hara
>
>
> _______________________________________________
> dmd-internals mailing list
> dmd-internals@puremagic.com
> http://lists.puremagic.com/mailman/listinfo/dmd-internals

On Sat, Jun 1, 2013 at 11:11 PM, Walter Bright <walter@digitalmars.com> wrote:
> 1. We already have a 2.063.1 released. An update would be 2.063.2.

Huh? Certainly "the" 2.063 release would be 2.063.0?

 — David
_______________________________________________
dmd-internals mailing list
dmd-internals@puremagic.com
http://lists.puremagic.com/mailman/listinfo/dmd-internals

2013/6/2 Walter Bright <walter@digitalmars.com>

>  1. We already have a 2.063.1 released. An update would be 2.063.2.
>

? Sorry, I might have some misunderstanding.
Currently we can access the "2.063" release package from here.

http://dlang.org/download.html http://downloads.dlang.org.s3-website-us-east-1.amazonaws.com/releases/2013/dmd.2.063.zip

Is this internally called by the name "2.063.1"?

We already have v2.063 tag in git repository, so I've thought that 2.063 is different from 2.063.1. Is that incorrect?


> 2. I'd prefer to wait a bit to collect any more regressions before rushing out with an update.
>

OK. Waiting next "fix-up" release a while seems reasonable. In my opinion, one or two weeks would be good. But a month is a bit long to me.

Kenji Hara

>
> On 6/1/2013 11:25 AM, Kenji Hara wrote:
>
>  I think we should release 2.063.1, for these reasons:
>
>  - Regression bug 9122 is not actually fixed in 2.063 release although
> it's listed in fixed Phobos regressions
>
>    Because current 2.063 release does not contain the fix for issue 10017.
>
> https://github.com/D-Programming-Language/phobos/commit/9a7627776e7cffa999f30e5a7450fb7f044a12f7
>
>    Actually that was the root cause of 9122, so it should have been
> contained in 2.063 release.
>
>  - 2.063 release has some regressions which was discovered after
> releasing.
>
>    Issue 10215 - [REG2.063] const causes wrong float calculation
>
>      This is serious wrong-code bug. This bug does not exist in git
> master.
>     To fix the bug, we just need to recreate release package.
>     Read my comment:  http://d.puremagic.com/issues/show_bug.cgi?id=10215
>
>    Issue 10212 - [REG2.061] Segfault in mismatching delegate literal types
>
>      It's old regression bug, but should be fixed as soon as possible.
>     Please review and merge
> https://github.com/D-Programming-Language/dmd/pull/2101
>
>    Issue 10197 - [REG2.063] Cannot cast overloaded template property
> result
>
>      Already fixed in git master.
>
>  From now I'll push some trivial changes to 2.063 branch which I think
> these are necessary for 2.063.1.
>
>  And I'll remove 2.063.1 tags for a moment. I think tagging should be
> done after the release done, but it's not yet released.
>
>  Kenji Hara
>
>
> _______________________________________________
> dmd-internals mailing listdmd-internals@puremagic.comhttp://lists.puremagic.com/mailman/listinfo/dmd-internals
>
>
>
> _______________________________________________
> dmd-internals mailing list
> dmd-internals@puremagic.com
> http://lists.puremagic.com/mailman/listinfo/dmd-internals
>

On 6/1/2013 2:49 PM, Kenji Hara wrote:
> 2013/6/2 Walter Bright <walter@digitalmars.com <mailto:walter@digitalmars.com>>
>
>     1. We already have a 2.063.1 released. An update would be 2.063.2.
>
>
> ? Sorry, I might have some misunderstanding.
> Currently we can access the "2.063" release package from here.
>
> http://dlang.org/download.html http://downloads.dlang.org.s3-website-us-east-1.amazonaws.com/releases/2013/dmd.2.063.zip
>
> Is this internally called by the name "2.063.1"?

Yes, and it is so tagged in github.

>
> We already have v2.063 tag in git repository, so I've thought that 2.063 is different from 2.063.1. Is that incorrect?

The v2.063 was an aborted 'release'. 2.063.1 is what was released. (The compiler & libraries are unchanged, what happened was the documentation was fixed.)

>     2. I'd prefer to wait a bit to collect any more regressions before rushing
>     out with an update.
>
>
> OK. Waiting next "fix-up" release a while seems reasonable. In my opinion, one or two weeks would be good. But a month is a bit long to me.
>

I agree.

> Kenji Hara
>
>
>     On 6/1/2013 11:25 AM, Kenji Hara wrote:
>>     I think we should release 2.063.1, for these reasons:
>>
>>     - Regression bug 9122 is not actually fixed in 2.063 release although
>>     it's listed in fixed Phobos regressions
>>
>>       Because current 2.063 release does not contain the fix for issue 10017.
>>     https://github.com/D-Programming-Language/phobos/commit/9a7627776e7cffa999f30e5a7450fb7f044a12f7
>>
>>       Actually that was the root cause of 9122, so it should have been
>>     contained in 2.063 release.
>>
>>     - 2.063 release has some regressions which was discovered after releasing.
>>
>>       Issue 10215 - [REG2.063] const causes wrong float calculation
>>
>>         This is serious wrong-code bug. This bug does not exist in git master.
>>         To fix the bug, we just need to recreate release package.
>>         Read my comment: http://d.puremagic.com/issues/show_bug.cgi?id=10215
>>
>>       Issue 10212 - [REG2.061] Segfault in mismatching delegate literal types
>>
>>         It's old regression bug, but should be fixed as soon as possible.
>>         Please review and merge
>>     https://github.com/D-Programming-Language/dmd/pull/2101
>>
>>       Issue 10197 - [REG2.063] Cannot cast overloaded template property result
>>
>>         Already fixed in git master.
>>
>>     From now I'll push some trivial changes to 2.063 branch which I think
>>     these are necessary for 2.063.1.
>>
>>     And I'll remove 2.063.1 tags for a moment. I think tagging should be done
>>     after the release done, but it's not yet released.
>>
>>     Kenji Hara
>>
>>
>>     _______________________________________________
>>     dmd-internals mailing list
>>     dmd-internals@puremagic.com  <mailto:dmd-internals@puremagic.com>
>>     http://lists.puremagic.com/mailman/listinfo/dmd-internals
>
>
>     _______________________________________________
>     dmd-internals mailing list
>     dmd-internals@puremagic.com <mailto:dmd-internals@puremagic.com>
>     http://lists.puremagic.com/mailman/listinfo/dmd-internals
>
>
>
>
> _______________________________________________
> dmd-internals mailing list
> dmd-internals@puremagic.com
> http://lists.puremagic.com/mailman/listinfo/dmd-internals

2013/6/2 Walter Bright <walter@digitalmars.com>

>
> On 6/1/2013 2:49 PM, Kenji Hara wrote:
>
> 2013/6/2 Walter Bright <walter@digitalmars.com>
>
>>  1. We already have a 2.063.1 released. An update would be 2.063.2.
>>
>
>  ? Sorry, I might have some misunderstanding.
> Currently we can access the "2.063" release package from here.
>
>  http://dlang.org/download.html
>
> http://downloads.dlang.org.s3-website-us-east-1.amazonaws.com/releases/2013/dmd.2.063.zip
>
>  Is this internally called by the name "2.063.1"?
>
> Yes, and it is so tagged in github.
>
>   We already have v2.063 tag in git repository, so I've thought that
> 2.063 is different from 2.063.1. Is that incorrect?
>
> The v2.063 was an aborted 'release'. 2.063.1 is what was released. (The compiler & libraries are unchanged, what happened was the documentation was fixed.)
>

OK. I restored v2.063.1 tags to each repos.

2. I'd prefer to wait a bit to collect any more regressions before rushing
>> out with an update.
>>
>
>  OK. Waiting next "fix-up" release a while seems reasonable. In my
> opinion, one or two weeks would be good. But a month is a bit long to me.
>
>    I agree.
>

Thanks.

Kenji Hara