Tag Archives: MariaDB Server
On the 3rd of July, two weeks ago, I created a poll to ask about the future of feature development branches in MariaDB Server. Specifically, whether we should switch to a rolling model which is more familiar to users of services such as GitHub.
The votes we received gave a very clear result. Today I will share the conclusions we drew, as well as setting expectations for what will happen next.
Recap: what is this “main” branch all about?
In a rolling model, there is one main branch of the tree that all the feature commits go into (typically called “main”), and this is then forked when it is time to prepare a major release.
…
Continue reading “MariaDB Server GitHub branches: Moving to “main””
Many countries in the world right now are hosting elections, in fact, my own country’s election is tomorrow. MariaDB Foundation is also asking for you to make one more vote on our own kind of referendum.
We have recently had a request by a member of the community to change how we use GitHub, in a way that, in-theory, will make things easier for community contributors. I’ll explain the current situation, the proposal and then the poll.
Current situation
At the moment, if you want to develop a new feature for MariaDB Server, it needs to be developed against the latest version branch, which is the default branch when you view on GitHub.
…
Continue reading “MariaDB Server GitHub branches: Have your say”
Coding standards are often as hotly debated as vim vs emacs and other developer arguments. Viewers of the show Silicon Valley will all know the “tabs vs spaces” scene and how passionate people can be about it. Whilst I do personally have a preference (I’m not sharing it here), I feel it is much more important that people stick to one standard for a code base.
Standards Story
Several months ago a new community developer for MariaDB Server sent me a message asking where to find our coding standards document. After a bit of searching I realised we did not have one, and if we want to onboard new developers we definitely should have one.
…