@tpaviot , I suggest a single point of download, which we point to on the conda badge, which is @rainman110 / DLR site.

Shall we keep doing so or make a separate "official" pythonocc conda account?
We can use that new account to collaborate on, since more users an share an account

So far, it's ok for me to point to @rainman110 /DLR site. We'll see in the future, if ever DLR site is not maintained anymore. Unless @rainman110 wants to move to an official pythonocc repository, I prefer, for now, keep working this way.

OK, I think that's the way to go, we'll speak about a pythonocc account for 0.17.1, if we feel there's a need for it at all ( I'm happy for now ) ?

@tpaviot, @jf--- I am currently building the release. Linux and Win are already done. Mac takes longer due to the rpath fixing.
It would be great, to have some automatic build process for the releases such that I don't have to do this manually on different machines. I think, we should also have an official pythonocc anaconda account for future releases. This way, you are independent from DLR specific patches and changes and also it just looks better 😄

@rainman110 good point...

TL;DR

• Use CI for CD ( cont. delivery ) -- lets not repeat the effort
• A commit to master is a new release

What about the following outlook:

• a commit to master triggers a travisci build, using conda
• whenever all tests pass, I think we should use conda upload to push the resulting package to the anaconda site
• these builds should go to a separate channel, say, a dev channel
• whenever we want to release a specific package, just change the channel from dev -> main
• then run conda update pythonocc-core --channel dev
• this is why automatic versioning is important
  • in addition to Major, Minor, Patch, you'd have another attribute, SHA1, referring to the git commit
  • eg, 0.16.3.6f5280 / 6f52808

now, currently, this would cover linux. we can have osx #187 for travis too.
do the same thing with appveyor for windows

@rainman110 , many thanks for the 0.16.3 builds
awesome, thanks... 🍹 🏆

@jf--- Yes, this is absolutely the way to do it.

To sum up what remains to do:

• OS X builds with travis
• Make app-veyor functioning for the windows builds (last time i checked it was not working)
• Use git SHA as version id. We need to add the SHA to the conda recipe and the CMakeLists.txt as well.

@rainman110 Great... that we share the outlook...
let me move this conversation to a new issue, we've been discussing this idea a nr of times in various places...