background preloader

A successful Git branching model »

A successful Git branching model »
Note of reflection (March 5, 2020)This model was conceived in 2010, now more than 10 years ago, and not very long after Git itself came into being. In those 10 years, git-flow (the branching model laid out in this article) has become hugely popular in many a software team to the point where people have started treating it like a standard of sorts — but unfortunately also as a dogma or panacea.During those 10 years, Git itself has taken the world by a storm, and the most popular type of software that is being developed with Git is shifting more towards web apps — at least in my filter bubble. Web apps are typically continuously delivered, not rolled back, and you don't have to support multiple versions of the software running in the wild.This is not the class of software that I had in mind when I wrote the blog post 10 years ago. Why git? ¶ For a thorough discussion on the pros and cons of Git compared to centralized source code control systems, see the web. The main branches ¶ develop

Related:  New ConceptsEHDevOps

How to Build Continuous Integration for Embedded Software - Jumper Blog Researches of SW R&D teams show significant improvements in all R&D and operation metrics when proper continuous integration and delivery processes were implemented (take a look at this case study). We thought it would be highly beneficial to demonstrate how to apply these practices to embedded SW teams. Applying continuous integration and delivery for embedded SW development is not an easy task as you have a physical device with many constraints when it comes to rapid testing. However, the gained benefits outweigh the effort. For more info about CI advantages and considerations when it comes to embedded SW check out this post. In this post, I’ll outline a guideline for building such a process for embedded SW development.

What is the Architecture Review Board (ARB)? - IS&T Contributions - Hermes Purpose The Architecture Review Board (ARB) serves as a governance body ensuring IT initiatives align with Ecosystem Architecture and ultimately align with MIT IT goals, strategies, and objectives. The ARB’s purpose is to improve the quality of IS&T Products. The Architecture Review Board (ARB) defines appropriate IT strategies and ensures development alignment with those strategies. Understanding Git Conceptually Introduction This is a tutorial on the Git version control system. Git is quickly becoming one of the most popular version control systems in use. There are plenty of tutorials on Git already.

What’s Hot in 2013: Our Picks 2012 was a fantastic year for new technologies, products, and frameworks in our industry. That said, 2013 is looking to be even better! Recently, I asked our Nettuts+ writing staff to compile a list of the technologies that they'll be keeping a close eye on. Now these aren't necessarily brand new, but we expect them to spike in popularity this year!

The Tools We Work With — Varnish version trunk documentation "Only amateurs were limited by their tools" is an old wisdom, and the world is littered with art and architecture that very much proves this point. But as amazing as the Aquaeduct of Segovia is, tools are the reason why it looks nowhere near as fantastic as the Sydney Opera House. Concrete has been known since antiquity, but steel-reinforced concrete and massive numerical calculations of stress-distribution, is the tools that makes the difference between using concrete as a filler material between stones, and as gravity-defying curved but perfectly safe load-bearing wall. My tool for writing Varnish is the C-language which in many ways is unique amongst all of the computer programming languages for having no ambitions. The C language was invented as a portable assembler language, it doesn't do objects and garbage-collection, it does numbers and pointers, just like your CPU. Compared to the high ambitions, then as now, of new programming languages, that was almost ridiculous unambitious.

How To Automate Device Drivers Testing In IoT Embedded Software Projects BSP (Board Support Package) and device drivers are the heart of every embedded software project. To start working with sensors or peripherals on your device you must have some sort of device drivers to begin with. Depending on your personal taste, coding drivers and designing hardware abstraction layers is a task that people either love or hate. Mastering the sequences of SPI or I2C information flow for example requires delicacy and mastery. Writing the code that interacts with hardware requires reading through long data sheets, carefully combining byte after byte to make the thing work and usually after it works the R&D team will avoid any changes to this code. Writing tests that cover this part is particularly tricky.

The Three Infrastructure Mistakes Your Company Must Not Make When Avi Freedman was getting ready to graduate Temple University in 1992, there was no way to buy internet service in Philadelphia. Literally. If you wanted to send someone money to get a dial-up account, there was nobody to send it to. But Freedman had already been running public access Unix machines and letting people he knew log into them.

A Visual Git Reference If the images do not work, you can try the Non-SVG version of this page. SVG images have been disabled. (Re-enable SVG) This page gives brief, visual reference for the most common commands in git. Once you know a bit about how git works, this site may solidify your understanding. If you're interested in how this site was created, see my GitHub repository. Signup » Are You A Human Basic For the CAPTCHA hater. Free! Unlimited PlayThrus Libraries & plugins galore! About Jarvis - GitHub Update: We're on Hack a Day. If you found this interesting, check out our website. Intro Jarvis is the system we have designed to control the door at our hackerspace. The system has four main parts: Moving from manual to automated testing in embedded software - Jumper Blog Automated Testing in Embedded Software – Why? Automated testing in embedded software has many benefits. When implemented in your organization it can: Reduce the number of bugs discovered late in the development cycle.Help you refactor your code with confidence.Reduce recovery time for post-production failures.Improve time to market and build a more productive R&D cycle.Increase features delivery and drives business initiatives.

Related:  Développement informatiqueMisc ToolsUsefulGitgitgitgithubvm248ProgrammingTutorials