-
-
Notifications
You must be signed in to change notification settings - Fork 12
Contributors
Not a contributor? Releases Documentation
Releases are done as canvas boards in the projects tab are completed. Lathe #Unstable is used as THE development branch. Version control is a very important part of contributing, as Lathe is consistently updated. With that being said, all pull requests need to be on the Unstable branch. As a maintainer, I used to work around master pushes in one way or another, but I'm not doing it anymore, as it generates a ridiculous amount of commit work for me on the repositories back-end. So DON'T forget to switch your tree.
Post 0.1.0, the centralized package Lathe (stats, preprocess, and models) will remain untouched. Features will be developed separately from the main package, leaving the base consistent and untampered, most seperate features will be merged into stats, validate, and preprocess. Its important that this is followed to keep LTS's seperate, and to make merge deprecation a lot easier for smaller features. So for example, before there was Lathe.models.Pipeline, there was Lathe.pipelines.Pipeline, contained entirely in a seperate file, and manually merged into Lathe along with its prediction function, reworked into the dispatch.
Thank you all for your forks, stars, and pull requests.