Development seems to be at a bit of a standstill, so maybe it'd be worth taking what's been submitted and pushing it out as a beta.

Maybe a tad silly since it hasn't been that long since the last release, and we haven't put together a lot of what we semi-promised to do before the next release, but...

On the other hand, nearly every time someone suggests that it might be
time for a release activity picks back up, so maybe that'll be what this
email does too. :)
_______________________________________________
dmd-internals mailing list
dmd-internals@puremagic.com
http://lists.puremagic.com/mailman/listinfo/dmd-internals

I think this pull request will speak for itself: https://github.com/D-Programming-Language/druntime/pull/293

In all seriousness, I have no real opinion on putting out a release. My only input is: Whenever we do it, let's do it properly with branching this time. Stalling the pull request queue even MORE just because of a release is not acceptable.

On Fri, Aug 31, 2012 at 12:28 AM, Brad Roberts <braddr@puremagic.com> wrote:
> Development seems to be at a bit of a standstill, so maybe it'd be worth taking what's been submitted and pushing it out as a beta.
>
> Maybe a tad silly since it hasn't been that long since the last release, and we haven't put together a lot of what we semi-promised to do before the next release, but...
>
> On the other hand, nearly every time someone suggests that it might be
> time for a release activity picks back up, so maybe that'll be what this
> email does too. :)
> _______________________________________________
> dmd-internals mailing list
> 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

On Thursday, August 30, 2012 15:28:26 Brad Roberts wrote:
> Development seems to be at a bit of a standstill, so maybe it'd be worth taking what's been submitted and pushing it out as a beta.
> 
> Maybe a tad silly since it hasn't been that long since the last release, and we haven't put together a lot of what we semi-promised to do before the next release, but...
> 
> On the other hand, nearly every time someone suggests that it might be time for a release activity picks back up, so maybe that'll be what this email does too. :)

It hasn't even been a month since the last release and activity has been low enough that I really don't see any point in doing another release right now - especially since the beta stuff _isn't_ properly automated yet, so it seems to take a fair bit of Walter's time to deal with it. That and we need to iron out how we're going to deal with branching and the beta, since it definitely looks like we should be moving to a model where we branch for betas. If we actually take the time to sort that out for the next beta like we should, then that means that the beta will take that much more work (though it will mean less work for future betas - particularly if the release process is properly automated like Andrei keeps asking for). So, it seems completely counter- productive to do a beta right now.

But maybe it'll actually encourage more activity like you say. :)

I'd be doing more, but things have gotten very busy at work of late, forcing me to work extra hours and whatnot. That and too much of what I've been doing of late keeps requiring that other stuff that I've been doing be merged into Phobos before I can create pull requests for it, so the whole pull cycle slows things down. But at least I'm getting _some_ stuff done...

It does seem like activity on both the mailing lists and Phobos has trailed off of late though. But many of the recent pull requests have been coming from new contributors, so in spite of the low pull request creation rate, we're at least getting new folks contributing.

- Jonathan M Davis
_______________________________________________
phobos mailing list
phobos@puremagic.com
http://lists.puremagic.com/mailman/listinfo/phobos

On Aug 31, 2012, at 12:37 AM, Alex Rønne Petersen <xtzgzorex@gmail.com> wrote:

> I think this pull request will speak for itself: https://github.com/D-Programming-Language/druntime/pull/293
>
> In all seriousness, I have no real opinion on putting out a release. My only input is: Whenever we do it, let's do it properly with branching this time. Stalling the pull request queue even MORE just because of a release is not acceptable.

I completely agree.

--
/Jacob Carlborg

On Aug 31, 2012, at 12:38 AM, Jonathan M Davis <jmdavisProg@gmx.com> wrote:

> It hasn't even been a month since the last release and activity has been low
> enough that I really don't see any point in doing another release right now -
> especially since the beta stuff _isn't_ properly automated yet, so it seems to
> take a fair bit of Walter's time to deal with it. That and we need to iron out
> how we're going to deal with branching and the beta, since it definitely looks
> like we should be moving to a model where we branch for betas. If we actually 
> take the time to sort that out for the next beta like we should, then that
> means that the beta will take that much more work (though it will mean less
> work for future betas - particularly if the release process is properly
> automated like Andrei keeps asking for). So, it seems completely counter-
> productive to do a beta right now.

Does it? If we want to change the release process isn't it better to have as few changes as possible. We could have made a dry-release (i.e. without changes) just after the 2.060 release just to test the new process.

I think it would be better to figure out how we want the release process to look like as soon as possible and not wait until we have enough changes for a proper release.

The first thing we should have done after the 2.060 release was to figure out a new release process. Then when we're actual want to make a real release we already have the new process figured out and it won't be a problem.

A release with the new process should be made as soon as possible.

--
/Jacob Carlborg

On Fri, 31 Aug 2012 00:37:44 +0200, Alex Rønne Petersen <xtzgzorex@gmail.com> wrote:

> I think this pull request will speak for itself:
> https://github.com/D-Programming-Language/druntime/pull/293
>
> In all seriousness, I have no real opinion on putting out a release.
> My only input is: Whenever we do it, let's do it properly with
> branching this time. Stalling the pull request queue even MORE just
> because of a release is not acceptable.
>
Right, we should really sort this out before the next release.
_______________________________________________
dmd-internals mailing list
dmd-internals@puremagic.com
http://lists.puremagic.com/mailman/listinfo/dmd-internals

On 9/3/12 11:09 PM, Martin Nowak wrote:
> On Fri, 31 Aug 2012 00:37:44 +0200, Alex Rønne Petersen
> <xtzgzorex@gmail.com> wrote:
>> In all seriousness, I have no real opinion on putting out a release.
>> My only input is: Whenever we do it, let's do it properly with
>> branching this time. Stalling the pull request queue even MORE just
>> because of a release is not acceptable.
>>
> Right, we should really sort this out before the next release.

Yeppers. BTW, we could use d-programming-language.org as a warmup. Right now we're having the following problem: some fixes are intended to be pushed immediately (e.g. typos), whereas others are to be done at the next release.

Could a git conoisseur document the procedure on the wiki so we have it?


Thanks,

Andrei

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