Tagging project version
SBoudrias opened this issue · 4 comments
Hi, I was wondering if you could tag x18n versions release in order to allow easier use throughout packages managers. The commands would be fairly easy
git tag -a x.x.x -m "Version x.x.x"
git push --tags
Sure, I've tagged v1.0.0
right now. I usually tag my releases, but for some reason I always tagged v1.0.0
when I started working on v1.1.0
, which doesn't really make sense. I guess I'll start earlier now. :)
By the way, what package manager are you using?
Right now Bower with grunt-bower-task to clean up "garbage files". But I'm still not 100% happy with it, it's hard to find a good package manager without flaws right now.
Hm, you can use x18n with bower right now? I thought bower required a component.json file?
Anyways, you might want to check out component, it's pretty awesome. Right now x18n doesn't work with it, because of the event system dependency, but I'll fix that soon.
Yeah, ideally you setup deps and main file in component.json
for Bower, but it also use straight git
to fetch package. That's a pretty good thing as managing multiple packages manager is quite a job for a project maintainer. I guess the idea is to keep it as simple as possible, git + tags seems like the way to go at this level.
I'll get a closer look at component.