Lionel Dyck writes:
Hi Lionel,
> We are having a discussion about best practices with Git. Specifically
> in the area of when a project reaches a milestone – say Version 2.0 –
> should we just tag that level and leave it at that, should we create a
> branch for it,
In essence, you should
We are having a discussion about best practices with Git. Specifically in
the area of when a project reaches a milestone – say Version 2.0 – should
we just tag that level and leave it at that, should we create a branch for
it, or should we make a copy outside of Git for those files so that we
- Original Message -
I need certain best practices / guidance around how to
effectively version control advance analytical models written in Python / Spark
on Git. The advanced analytical models are a bit different to the normal Java
code. As the training of the
Well I think that in the end it's just code, maybe the difference it's that
this code changes very often.
Just make a commit every time you achieve something (or some task is
completed). If you are worried about having different versions of a same
model, you can use branches to keep them
Hi,
Greetings !
I need certain best practices / guidance around how to
effectively version control advance analytical models written in Python /
Spark on Git. The advanced analytical models are a bit different to the
normal Java code. As the training of the
Hi Owen,
The suggestion from Dale Worley is correct. There is a third case:
3) the derived files are difficult to derive without special knowledge
or procedures. In which case, documentation is only sometimes the
superior method.
Mark, sf_x
On Thu, Jan 22, 2015 at 1:19 AM, Gergely Polonkai
What's the best practice for derived files in a git repo?
By derived files I mean .min.js and coffee *.js files concatenated into the
project .js file, and the docs created out of the source files (docco,
jsdoc, ..).
I ask because its been suggested to minimize these, and put them in a
Owen Densmore o...@backspaces.net writes:
What's the best practice for derived files in a git repo?
Don't put them in the repository.
There are only two cases: (1) The version of the derived file in the
repo is correct relative the files that it's derived from. In that
case, the derived file
Hello,
I'm new to git and I used svn before.
I would like to know what are the best pratices when one generates an
executable to be able to retreive sources related to the executable.
With svn. It was automatic. I had a file, when updated, that get
automatically the svn-revision number and other
