| ID: | 195 |
| From: | ge...@igor2.repo.hu |
| Date: | Mon, 5 Dec 2016 15:05:46 +0100 (CET) |
| Subject: | Re: Layer rewrite new (was: Re: [pcb-rnd] gerber output names have |
| in-reply-to: | 194 from James Battat <jb...@wellesley.edu> |
| replies: | 197 from James Battat <jb...@wellesley.edu> , 198 from John Griessen <jo...@cibolo.com> |
This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-1357785425-1480946746=:7286 Content-Type: TEXT/PLAIN; charset=UTF-8; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE Hello James, On Mon, 5 Dec 2016, James Battat wrote: >Thanks for the update on this.=C2=A0 If the fix will take time, can you re= commend >an svn rev number that is before this bug, I need to send Gerbers out toda= y. >=C2=A0 Also from now on I should be more careful when updating to HEAD.=C2= =A0 Do you >have a recommended way to have both a known good copy and HEAD available i= n >my machine? Our release policy is: - we try to make releases rock solid, so if you use an official release,=20 that should have no major bug or regression compared to the last one - relases are collected in svn in the /tags directory (as recommended by=20 the svn book); you could do an "svn ls svn://repo.hu/pcb-rnd/tags" to see= =20 what versions we have and check out one - /trunk is always the latest "development snapshot:, might be unstable or= =20 buggy and may have temporary regressions; although I try to carry out even= =20 largish refactorings in a series of working intermediate commits, the code= =20 base is so huge that I sometime miss newly introduced bugs (like this=20 gerber layer name thing). I am working on improving the automated test=20 system to make it easier to catch these (user help needed on this!) - I try to maintain predefined, public release timeline so users can=20 follow the process and know what to expect from trunk/; I try to do=20 restrict myself to do the refactoring/cleaning in the first 1/3 of a=20 development cycle and keep the last 1/3 for minor bugfixes so we have time= =20 to test out the changes before we release. You can find the timeline at=20 http://repo.hu/projects/pcb-rnd under the timeline menu. A good strategy for dual-version is to install the last release (either=20 from svn tags or from a tarball release) and keep trunk/ uninstalled. You= =20 can always run trunk from source (./pcb-rnd from trunk/src) to test the=20 latest/greatest feature while if you start pcb-rnd from anywhere else you= =20 get the latest stable. It's also a good idea to configure the trunk/=20 version with --debug while keep the stable version in production settings,= =20 for speed - debug slows polygons a lot. HTH, Igor2 --0-1357785425-1480946746=:7286--
Reply subtree:
195 Re: Layer rewrite new (was: Re: [pcb-rnd] gerber output names have from ge...@igor2.repo.hu
197 Re: Layer rewrite new (was: Re: [pcb-rnd] gerber output names have changed after svn up) from James Battat <jb...@wellesley.edu>
201 Re: Layer rewrite new (was: Re: [pcb-rnd] gerber output names have from ge...@igor2.repo.hu
198 [pcb-rnd] Re: Layer rewrite new from John Griessen <jo...@cibolo.com>