[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [orion-dev] Versioning and plugins
- From: Mark Macdonald <mamacdon@xxxxxxxxx>
- Date: Fri, 13 Apr 2012 19:15:19 -0400
- Delivered-to: firstname.lastname@example.org
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=WXMgHe/CCEogbr1N5BXh5SEVbOjgPh4tTfKc+sJ12mo=; b=PPIeeFP+JRnucm2LkzC55NQZZotyl9P2PQYt1o2V9COl2zD/Kf1TOyzb0cdfuzPhlm sFF01LEmK/N55TOKxw0hBWgFSqPtyJ68iDrZrbvxQ1LSw3In+Uka8Z8bG2agKg0i7gzx wQn8nkTdzp3OJ6ZyLQL4U8VIBC0fjAoou118bGyN9vQDLBdtOWjvx7tkN4zPybAfiJ1o QxGN7+WuFbXOE/j6MGdtz8rK1GnlCQia+h/or4RW6bZwZvhvkn3FydRIujsa8inelyON fReflayG9/7t6mpysORKw4nyxT4jqm7pLSpm6xrD+ZTbEFBClRQymYyZQ0DzENhL2A7o ym4w==
I don't think we've worked out a best solution, but here's what I'm doing:
For the plugins I maintain, I reserve 'master' for the bleeding edge (only guaranteed to work against Orion master). When I'm about to introduce a breaking change, I archive the old version at some other URL, and link it to the plugin catalog . This is nice because my master branch doesn't get filled up with old junk, and previous versions are still available on the web for people running older Orions.
With that in mind, you could use a 'gh-pages' branch to host your various versions:
# On branch gh-pages
This gives each version a distinct, stable URL that you can link to. Up until now I've been carelessly passing out bleeding-edge URLs to users, but this is a bad idea that can lead to all kinds of breakage, so I'm trying to move the catalog to version-stable URLs instead.