Make this repo public about unsee HOT 19 CLOSED

We're done with PRs I think, I'll open the repo and setup travis

from unsee.

Repo is public so closing

from unsee.

I guess there's one issue - we should tag a release

from unsee.

Created first milestone, if there's anything else we need please raise a ticket and attach it to this milestone.

from unsee.

I'm happy to open this once the PRs are all merged. Your suggestions are all fine - using Travis is no problem, we already use it for many other Cloudflare repos.

from unsee.

No more outstanding PRs, is everyone happy with making this repo public now? This will allow me to tag a release and complete at least first 2 points in this ticket (docker image isn't critical).

from unsee.

LGTM 👍

from unsee.

@mattbostock any objections?

from unsee.

No objections from me. Just one question - are we going to use the timestamp format for release tags?

IMHO it'd be more useful to use semantic versioning for a public project.

from unsee.

Also, minor nit, but we should definitely add a screenshot to the README. Maybe using the sample data you created?

from unsee.

I'm happy with both version schemes, @jamesog you're needed to get a quorum
I'll add a screenshot but let me add more mocked alerts, it would look kinda sad with the current set

from unsee.

Should we use v prefix for release tags and milestones? I think that v1.0 is more obvious as a tag name than 1.0, same for milestones.

from unsee.

Yep, I'd prefix with v.

You have your quorum. Let the code be free.

from unsee.

I also agree with 'v' - I believe that's what GitHub uses by default if you create a tag manually.

from unsee.

I'm thinking that, rather than v1.0, we make the first version be v0.0.1. That'll allow for changes (without worrying about backwards compatibility) while the code settles a bit.

Using SemVer, there's a big difference between pre-1.0.0 and 1.0.0 onwards:
http://semver.org/#spec-item-4

from unsee.

v0.1.0 it is, v0.0.1 sounds like a stub of a project, I think we're past that phase

from unsee.

🎉

from unsee.

Made a PR for travis - #17
I'm going to ignore docker for now and get back to it later (will raise an internal ticket for myself)

from unsee.

will deploy a new build internally and if all goes well we'll tag a release

from unsee.