Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider adding tags for the repo. #33

Closed
Piicksarn opened this issue Aug 8, 2015 · 2 comments
Closed

Consider adding tags for the repo. #33

Piicksarn opened this issue Aug 8, 2015 · 2 comments

Comments

@Piicksarn
Copy link

Hi~
Adding tags for repo could specify points in history and mark release points.
It's helpful for user to know the version and status of repository, and would enable wider distribution of the library, for example on CDNJS
Would you please consider on using tags?

Thanks for your great work!!
Piicksarn

@korroz
Copy link
Contributor

korroz commented Aug 8, 2015

This would indeed be useful.

Using npm version should make the tagging easy to manage as well.

I would consider what is being tagged though, before committing to version tags. This repo currently houses two distinct things, i.e. the nomnoml web application and the nomnoml library (the npm package). It is important to be clear exactly what is being tagged, so that for example changes that only affect the web application doesn't bump the version, but changes to the library part does.

Ideally these two parts should be separated, but that is currently not the case.

@skanaar
Copy link
Owner

skanaar commented Aug 10, 2015

I agree. This will probably happen as soon as the library leaves the prerelease-phase.

@skanaar skanaar closed this as completed Apr 9, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants