github release procedure

Johannes Pfau nospam at example.com
Sun Jan 6 02:34:15 PST 2013


Am Sun, 06 Jan 2013 00:18:16 +0100
schrieb "Rob T" <rob at ucora.com>:

> One quick note, is that we may want to change the title and 
> description,

Done.
http://wiki.dlang.org/Development_and_Release_Process

I also verified and corrected the git commands. They should now all work
as expected and can be used like a script.

Do you agree with the process as described on that page now? Would be
great to also get some feedback from other contributors of the original
wiki page.

I wonder whether a section should be added to the wiki explaining the
transition from current workflow to the new workflow. For the first
release we should do an additional merge from master into staging in
~4weeks as otherwise there won't be any new features in 2.062.

And I'd recommend merging staging into master, then deleting staging
and creating it again as we don't know whether staging already has
cherry picked commits etc?

If we want to maintain the current release we might have to use
cherry-picking this one time as I think there are already regression
fixes only pushed to master / staging which should be in the version
branch.


More information about the Digitalmars-d mailing list