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
Any chance of adding Cryptico? #2090
Comments
make a pull request? |
Yeah, a pull request would be great On Mon, Nov 11, 2013 at 7:38 AM, Andrew Wei notifications@github.comwrote:
|
This raises an interesting point - the current incarnation of Cryptico doesn't have a version number as such. How might this be resolved? It's the first time I've encountered it, so may be an edge case, but I'm curious to know. |
We could use a datestamp and commit hash to ensure we have a human readable Or, we could go even simpler and use the datestamp, and for multiple See json2 for an example of where we do this already: Using a datestamp does have interesting and complicated resolutions when On Tue, Jan 28, 2014 at 4:31 AM, Pete Cooper notifications@github.comwrote:
|
Would using Unix (epoch) time get around the timezone issue? I also found an instance today where a release was simply tagged as '0' where there was no clear version number. I'll see if I can find that for reference. Edit: found it - https://github.com/cdnjs/cdnjs/tree/master/ajax/libs/960gs/0 |
I think you're talking about 960gs with the I love the idea of using the UNIX timestamp. Let's use the unix timestamp On Tue, Jan 28, 2014 at 5:03 PM, Pete Cooper notifications@github.comwrote:
|
I'll take a look at this - likely Feb 5th or 6th, if time allows. |
Source: https://github.com/wwwtyro/cryptico/archive/master.zip Background: #2090 Converted file timestamp to Unix epoch, then prepended with 0.0.* to fit semver numbering. There is a possibility that this software will be released with 0.0.1 version at some stage, which will throw this numbering scheme out of whack.
Background: #2090 Contains deletions to fix Travis build, no risk as initial commit failed.
Done. @modusinternet: please advise if there are any issues with this implementation. @ryankirkman: please advise if the epoch + semver directory naming needs changing. |
Converted GitHub commit (here: node-js-libs/load.js@f8b9e2e 2e7b6dd53) timestamp of 2011-09-19 13:13:27 to epoch time 1316434407 - no indication that this is a 1.0.0 release, and epoch numbering should be used in this case (see #2090 for info).
Will you guys be adding or could you please add Cryptico to your CDN?
http://wwwtyro.github.io/cryptico/
The text was updated successfully, but these errors were encountered: