New blog domain: kula.blog

By K -
It's still work in progress but new posts will be published on  https://kula.blog/ Thanks to 11ty base blog RSS is working from the start so it should be easy to add to your reader if you still use any :) If now then I hope you can sign up to the newsletter where I'll be publishing new posts and interesting articles to it from time to time. Please use  kula.blog  from now on.
Post a Comment

DevOps - SVN Workflow

By K -
Flickr
I've read about DevOps  a wikipedia and one aspect of it is not clear for me. How in Flickr they use Subversion? At this presentation: http://www.slideshare.net/jallspaw/10-deploys-per-day-dev-and-ops-cooperation-at-flickr
page: 38 - Always ship trunk
page: 40 - Example of "branching in code"
And there is Trunk for development, release branch to support etc. But how it looks like in Flickr? There is at page 38 "Always ship trunk" so developers must work on branches most of the time? Or first commit is with 'branching if's" in code?
Personally I doesn't like a if's for branching idea...

Chrome
Recently I read about similar approach in Google Chrome Release Cycle in which workflow are embedded   configuration options to do branching in code.
1: Everyone works on trunk, then they create stable branch and work on dev and to stabilize branch and ship all scheduled functions.
2: They work on trunk, has 3 channels, trunk, beta and stable to work and are using branching in code to minimize merges.
But Chrome is a big project and it is still app. For now I think that for smaller projects 3 lines are to much, and I still think that I prefer SVN branches that branches in code...

Standard
At least I found it quite popular and used in couple of books as a 'good practice'.
Despite Chrome, standard SVN repository structure is like : http://ariejan.net/2006/11/24/svn-how-to-structure-your-repository/.
This is great, but existing site development is much more like at Flickr, small changes but often to make users feels that site from day to day has new features or at least team is fixing bugs fast :-]

Combine them

Now I think about approach similar to both of them( Chrome(1) flow + Flickr + Standard).
1: Everyone commits to trunk
2: There is stable branch that changes are merged to when ready
3: Big changes creates new stable branch(release 2.0)

And when I think about changes:
1-2 is about small tweaks and bugfixes like in Flickr
3 is about bigger changes, eg change of database to NoSQL, new website design or at least something to have opportunity to clean-up stable branch and merge it with trunk :)

Maybe I am reinventing the wheel, please comment and let me now what you think about it :)

Comments

Post a Comment

Comments:

Popular posts from this blog

How to simulate slow connection (developer proxy in Node.js)

By K -
Image
Update: If you use Chrome then you can use "Throttling" so simulate slow network for all your assets. This should be easier than proxy. Toggle device mode   Choose Network type. Refresh the page https://developer.chrome.com/devtools/docs/device-mode  Proxy: For some time I wanted to use some proxy for development and testing of eg. slow internet connection, but it was hard to find something useful and free. I know there is Charles but buy it to use it at most one in a month is not for me. I started thinking about Node.js, maybe I can write proxy for me? But fortunately I found one. https://github.com/nodejitsu/node-http-proxy With this module I can write really short code to create slow server: var http = require('http'), httpProxy = require('http-proxy'); httpProxy.createServer(function (req, res, proxy) { var buffer = httpProxy.buffer(req); setTimeout(function () { proxy.proxyRequest(req, res, { host:...
Read more

Safari Mobile CSS VW and VH units bug.

By K -
Image
Recently we have created new version of mobil.aftenposten.no but soon after serving it to some users we spot this tweet:  https://twitter.com/Al3x4nd3rR/status/452047498111369216 . Basically titles were missing.... Then it started our effort to reproduce this bug. ... It was nightmare! First how to reproduce it: Open  http://krzychukula.github.io/vw_bfcache/  in Mobile Safari.  Click "Go to another page" link Leave phone for 60 seconds (longer is better) Click back button If you were lucky you should see some missing paragraphs and missing green boxes. How it looks: Bug: This one uses vw and vh for font-size. Both are 0 so we can see only 2 from 8 paragraphs. Those two are using only em for font-size. I was curious if it's only for font-size so I have added another test. I have added two boxes with width and height set in vw and vh with green background color. They parents have red background for contrast.  ...
Read more