Comment 32 for bug 1744832

i am familiar with the make tool chain.  my use of git has been very
cursory to-date

On 06/10/2018 02:27 PM, Chad Parker wrote:
> when you switch branches, it's often a good idea to
>
> make clean
> configure
> make
>
> the first gets rid of all of the previously compiled objects. This
> ensures that there will be no hold-over from the last branch. The second
> and third I assume you're familiar with.
>
> You don't actually have to do the "make install", of course, you can if
> you want to. You can run pcb directly from the source tree by executing
> the script
>
> src/pcbtest.sh
>
> When your testing a branch, this is the approach I recommend. Branches
> by their nature are not always production ready and can be unstable.
> Here's how I would describe things:
>
> branches: used to fix bugs and develop new features. Could be unstable, not recommended for actual work
> "master": stable, but not guaranteed to be bug free (we try, but it's hard to test all possible use cases). May be used for work if you need a new feature, or particular bug fix.
> releases: stable, recommended for work.
>