Feature request: tagging releases

[FedericoCeratto]

Hello and thanks for developing boxes.py
Would you consider tagging releases when the time is right?
It would help with packaging and redistributing boxes.py as a library or local application.

[florianfesti]

Sure. Currently the master branch is instantly deployed on the web instance. So we'd probably want some automation to build the releases, too.

Help for this is very welcome - especially for making the Inkscape part work out of the box.

What release cycles do you think would make sense? Any preferences for a particular versioning / tagging scheme?

[florianfesti]

May be just use the current master branch to see what is needed to make an release. I can tag a release if we have fixed everything for that.

[FedericoCeratto]

@florianfesti IMHO I would start with tagging the whole repository as 0.1.0 and let any distribution that wants to package ship it as an application or application+library or do their own build for the inkscape plugin if they want. Then if you'll ever feel the need to split it into component with independent versions you can do it before version 1.0.0