[dmd-beta] Preparation for 2.65

Brad Anderson eco at gnuk.net
Mon Jan 13 08:51:48 PST 2014


I must admit, I didn't read carefully enough in my haste.  That would
indeed work.


On Mon, Jan 13, 2014 at 9:20 AM, David Nadlinger <code at klickverbot.at>wrote:

> On Mon, Jan 13, 2014 at 7:10 AM, Brad Anderson <eco at gnuk.net> wrote:
> > One problem is that with the
> > current approach it's impossible to do a bugfix only release without
> > freezing all feature development (i.e. cherry-picking is forbidden but
> all
> > commits must still go to master) which is unacceptable and was the
> original
> > reason why a Release Process was created.
>
> What are you referring to as the "current approach" here? The way
> things have been done in the past, or the proposal at
> http://wiki.dlang.org/Release_Process?
>
> I'm pretty sure the latter actually addresses this problem as well: A
> fix that addresses regression or critical bug is merged into the
> oldest release branch it should end up on, and then merged
> subsequently into all newer release branches and master
> (http://wiki.dlang.org/Release_Process#Regression_fix).
>
> David
> _______________________________________________
> dmd-beta mailing list
> dmd-beta at puremagic.com
> http://lists.puremagic.com/mailman/listinfo/dmd-beta
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.puremagic.com/pipermail/dmd-beta/attachments/20140113/e4330efc/attachment-0001.html>


More information about the dmd-beta mailing list