Add release process skeleton

[alexbaden]

@vlad-penkin @Garra1980 anything to add?

[Garra1980]

Some words for conda-forge releases maybe?

[vlad-penkin]

I suggest to add two steps

5. Create GH release with source code archive
6. Build and publish updated conda-forge packages

[leshikus]

I cannot see from the document how decision is made when release is created. If I have to do something about the release, I need to get some signal. Even better to have a release schedule, this will make things much more ordered. E.g. we shipping things once per month.

5. Create GH release with source code archive

Let me note that automatic releases on GitHub do not work with submodules. Also IMHO the conda forge docs try to promote modularity to use a source release of one project (e.g. omniscidb) to build another project (e.g. HDK). We may consider to create omniscidb package on coda-forge to meet these requirements.

[aregm]

Hey @leshikus I’m using Zenhub in GitHub, click this link to join my workspace and see other features available in GitHub or download the Zenhub extension and sign up with your GitHub account.
Posted using Zenhub

[alexbaden]

I suggest to add two steps

5. Create GH release with source code archive
6. Build and publish updated conda-forge packages

Added, thanks!

I cannot see from the document how decision is made when release is created. If I have to do something about the release, I need to get some signal. Even better to have a release schedule, this will make things much more ordered. E.g. we shipping things once per month.

5. Create GH release with source code archive

Let me note that automatic releases on GitHub do not work with submodules. Also IMHO the conda forge docs try to promote modularity to use a source release of one project (e.g. omniscidb) to build another project (e.g. HDK). We may consider to create omniscidb package on coda-forge to meet these requirements.

Currently the decision is made based on some combination of upstream requests (mostly from modin), issues tagged into release that are completed, and rough schedule -- every 6-8 weeks or so. No one factor will determine release -- we will make the decision collectively. We want to have one conda-forge package for simplicity, so if we need to change repo organization to support that we can.

[leshikus]

LGTM

[vlad-penkin]

LGTM