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 organized. You can search about git workflows to have a better idea of the different approaches (maybe these workflows are overkill for your problem). Sorry if I oversimplified your problem! El jue., 3 de nov. de 2016 a la(s) 14:02, Debabrata Ghosh < [email protected]> escribió: > 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 advanced analytical models is > iterative therefore any guidance around at what time we should commit the > code into Git will be quite useful for me. > > Thanks for your response in advance ! > > > Thanks, > > Debu > > -- > You received this message because you are subscribed to the Google Groups > "Git for human beings" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
