Group items tagged

"Every GitHub Page is run through Jekyll when you push content to a specially named branch within your repository. For User Pages, use the master branch in your username.github.io repository. "

In January of this year, @nvie published "A successful Git branching model", in which he explained how he keeps his Git repositories nice and tidy. In addition to that, he released git-flow; a bunch of Git extensions to make following this model extremely easy. I'm astounded that some people never heard of it before, so in this article I'll try to tell you why it can make you happy and cheerful all day.

SubScript, a way to extend common programming languages aimed to ease event handling and concurrency. Typical application areas are GUI controllers, text processing applications and discrete event simulations. SubScript is based on a mathematical concurrency theory named Algebra of Communicating Processes (ACP). ACP is a 30-year-old branch of mathematics, as solid as numeric algebra and as Boolean algebra. In fact, you can regard ACP as an extension to Boolean algebra with 'things that can happen'. These items are glued together with operations such alternative, sequential and parallel compositions. This way ACP combines the essence of grammar specification languages and notions of parallelism.

A collection of Git extensions to provide high-level repository operations for Vincent Driessen's branching model.

Está excelente. Y es bastante parecido a lo que estamos haciendo con macom.

In this post I present the development model that I've introduced for all of my projects (both at work and private) about a year ago, and which has turned out to be very successful.

Interesante para probar de ponerlo en práctica y ver qué resulta, ¿no?

En github funciona muy muy bien el mecanismo, lo vengo usando bastante. El análisis, comprensión y diálogo que se genera a partir de los pull requests (y los reviews implícitos que esto produce, sumado a que la herramienta es muy muy buena, permitiendo cosas como poder poner comentarios y responderlos directamente en las lineas de código) son sumamente beneficiosos, ágiles y los resultados son muy buenos. Nosotros, localmente, venimos trabajando de manera similar a lo que se propone (y se acostumbra en github), tenemos branches por temas y se hace review y refactoring de las mismas antes de mergear al tronco de avance. Obviamente en este caso se extrañan MUCHO las herramientas de comunicación que provee github y que NO tenemos localmente.