search

FluxML / Zygote.jl

21st century AD
https://fluxml.ai/Zygote.jl/
Other
1.49k stars 211 forks source link

Start using the Continous Delivery convention of always be releasing #488

Open oxinabox opened 4 years ago

oxinabox commented 4 years ago

I would like to start following the continous delivery practice outlined in

https://white.ucc.asn.au/2019/09/28/Continuous-Delivery-For-Julia-Packages.html

Which basically is: If there is not a -DEV suffix on the version in in the Project.toml then every PR must either add that or bump the version number and have a release tagged after merging.

This would avoid #487 etc

oxinabox commented 4 years ago

can use https://github.com/bcbi/VersionVigilante.jl to help make sure it's done

DhairyaLGandhi commented 4 years ago

To avoid breakages with dependencies updating rapidly (esp with Zygote's scope), even ones we control like nnlib, I'd say doing this makes sense with a more structured CI. Probably time to hook up the model zoo bot and take it live both for Flux and Zygote?

oxinabox commented 4 years ago

Its generally fairly easy to identify if a change is breaking. And frequent releases makes it much easier to find out and then revert/fix.

I find the idea of the Model Zookeeper to be orthogonal, but I am in favor of it.