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

Already on GitHub? Sign in to your account

tag demos to a specific release #7

Open
anutron opened this Issue Jul 26, 2011 · 3 comments

Comments

Projects
None yet
3 participants
Owner

anutron commented Jul 26, 2011

As new versions of Core and More role out, we need a way to know which demos work with what release. Can we please tag these, or perhaps work on a branch that references, a specific release?

Owner

arian commented Jul 26, 2011

I personally don't think we need to overcomplicate here. They should just work with the latest release. Maybe for 2.0 we'll have some delay to update everything, but we can handle that at that time (by adding a note "These are 1.x demos!!!" or something).

Owner

anutron commented Jul 26, 2011

As we add more of these demos they'll have to either a) hold up development
releases while we bring them up to date or b) lag. Part of what's making me
push for this is that I want to convert all the UI tests in More to use this
demo format. Maybe I'm trying to make those things (which are tests) into
something they really aren't (demos). But the thing is that they each are
useful as the other; the UI tests are good demos, and the demos are good UI
tests (though we are trying to move more towards specs for that stuff)...

On Tue, Jul 26, 2011 at 11:09 AM, arian <
reply@reply.github.com>wrote:

I personally don't think we need to overcomplicate here. They should just
work with the latest release. Maybe for 2.0 we'll have some delay to update
everything, but we can handle that at that time (by adding a note "These are
1.x demos!!!" or something).

Reply to this email directly or view it on GitHub:
#7 (comment)

Owner

ibolmo commented Jul 27, 2011

We could solve this by doing a submodule in the repo for the demos. Then when we tag, the demos are locked for that version.

We would need to update our viewers (website, etc.) so that they use git.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment