Hello! I need some advice on how to deal with releases with luarocks and git(hub).
I'd like to release a new version of tango (rocks tango-copas and tango-complete, with very nice new features! https://github.com/lipp/tango/tree/release/0.2 ). 1. The recent version is 0.1, which is tagged in my github repo (https://github.com/lipp/tango). The rockspec refers to branch='mutli-backend', which is no more (merged to master) instead i would like to refer to tag='0.1'. I think, it is necessary to release a rockspec 0.1-2 which refers to tag='0.1' and to post a (permanent?) link to the rockspec here. Right? 2. Next, I'd like to 'bump_version' (new rocks refering to tag='0.2') and merge my release branch to master and tag '0.2'. 3. I'd like to have a rockspec which always refers to the latest (stable) release (on master branch, i will stick to the "git flow" branching model (http://nvie.com/posts/a-successful-git-branching-model/)) I appreciate any help! Regards, Gerhard ------------------------------------------------------------------------------ Using storage to extend the benefits of virtualization and iSCSI Virtualization increases hardware utilization and delivers a new level of agility. Learn what those decisions are and how to modernize your storage and backup environments for virtualization. http://www.accelacomm.com/jaw/sfnl/114/51434361/ _______________________________________________ Luarocks-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/luarocks-developers
