[Cs-dev] use of bug tracker
| Date | 2013-11-08 10:52 |
| From | Victor Lazzarini |
| Subject | [Cs-dev] use of bug tracker |
I am wondering whether we should use the bug tracker for things in the develop branch or not. To me that could lead to confusion because code that is there is not quite finished. Victor ------------------------------------------------------------------------------ November Webinars for C, C++, Fortran Developers Accelerate application performance with scalable programming models. Explore techniques for threading, error checking, porting, and tuning. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk _______________________________________________ Csound-devel mailing list Csound-devel@lists.sourceforge.net |
| Date | 2013-11-08 11:52 |
| From | Michael Gogins |
| Subject | Re: [Cs-dev] use of bug tracker |
| Attachments | None None |
Of course we should use the bug tracker for things in the develop branch. It is a central point for sharing information between developers, better than email. Most projects where I have looked for bug reports seem to have bug reports on development branches. I have also been thinking, I am going to post builds of the Windows installer whenever significant new features appear in the code base, clearly marked as "beta" or "alpha" or something, so that I get more feedback about problems before trying to finish a release.
For this purpose, maybe we need a different folder structure on SourceForge. Regards, Mike ----------------------------------------------------- Michael GoginsIrreducible Productions http://michaelgogins.tumblr.com Michael dot Gogins at gmail dot com On Fri, Nov 8, 2013 at 5:52 AM, Victor Lazzarini <Victor.Lazzarini@nuim.ie> wrote: I am wondering whether we should use the bug tracker for things in the develop branch or not. To me that could |