search

uberVU / mozaic

JS Framework for building SPA
http://ubervu.github.com/mozaic/
26 stars 17 forks source link

Merge 0.3.2 into master. Why not? #50

Closed topliceanu closed 11 years ago

topliceanu commented 11 years ago

Why are we not merge 0.3.2(latest stable version) into master?

ovidiuch commented 11 years ago

We still haven't figured out the versioning pattern we want to adopt, so we chose not to merge anything into master until that is settled.

aismail commented 11 years ago

Actually we have settled - it's just that in order to avoid problems, we're waiting for the reports project to finish. Basically it's what all the big projects do - have releases via git tags and feature branches, and master is the current development mainline.

topliceanu commented 11 years ago

Basically it's what all the big projects do - have releases via git tags and feature branches, and master is the current development mainline.

Allow me to disagree, afaik, large projects use something similar to this which is totally opposite to what you're enforcing in mozaic :)

aismail commented 11 years ago

Dear Alex, I've read that document at least 3 times (the one you sent me). Can you give a couple of examples of projects?

topliceanu commented 11 years ago

I checked jquery.js, node.js, coffeescript and rails. You're right! they're all doing dev on master and a release is simply a tag on a commit. I wonder why nobody is using that method, it seems very clean. All clear now, 10x @aismail

aismail commented 11 years ago

It's not as clean as it looks like. And think about how it would play with our internal branch structure when we develop a project internally. Nightmarish already? :)