[Cs-dev] Reminder: code frozen Wednesday
Date | 2013-10-15 16:56 |
From | john ffitch |
Subject | [Cs-dev] Reminder: code frozen Wednesday |
We have cleared a number of small bugs and improved the manual. I still intend freezing the code tomorrow (late) to allow time for package creation and such. If you have outstanding changes either commit or wait. btw we now have a soak-test suite and a regression test set. Currently all passes. ==John ffitch ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk _______________________________________________ Csound-devel mailing list Csound-devel@lists.sourceforge.net |
Date | 2013-10-15 18:12 |
From | Andres Cabrera |
Subject | Re: [Cs-dev] Reminder: code frozen Wednesday |
Attachments | None None |
Hi, What you can do now for code freezes is merge develop into master, to release from master, while people can just keep working on develop without interfering with the release.This is the advantage of the gitflow model. Andrés On Tue, Oct 15, 2013 at 8:56 AM, john ffitch <jpff@codemist.co.uk> wrote: We have cleared a number of small bugs and improved the manual. I |
Date | 2013-10-15 18:16 |
From | Steven Yi |
Subject | Re: [Cs-dev] Reminder: code frozen Wednesday |
Oh no, it should not be this yet. With git-flow we should create a release branch and do any last minute changes there (version numbers, installer file tweaks, etc.). When we've done the release, we can merge then back to master and develop using "git-flow release finish [version]". On Tue, Oct 15, 2013 at 1:12 PM, Andres Cabrera |
Date | 2013-10-15 18:35 |
From | Andres Cabrera |
Subject | Re: [Cs-dev] Reminder: code frozen Wednesday |
Attachments | None None |
Ah, yes, thanks for the clarification. Cheers,Andrés On Tue, Oct 15, 2013 at 10:16 AM, Steven Yi <stevenyi@gmail.com> wrote: Oh no, it should not be this yet. With git-flow we should create a |