Sozialwissenschaftler messen Stärke sozialer Netzwerke

heise online Newsticker - 25. Oktober 2017 - 10:30
Wie eng ist unser Beziehungsnetz? Harvard-Forscher suchen nach topologischen Mustern.

Archos Diamond Omega: Randloses Smartphone mit zwei Dual-Kameras

heise online Newsticker - 25. Oktober 2017 - 10:00
Das in Deutschland nicht erhältliche Nubia Z17S kommt über eine Partnerschaft mit Archos hierzulande als Diamond Omega in den Handel.

5 Jahre iPad mini: Apples unerwünschtes Tablet

heise online Newsticker - 25. Oktober 2017 - 10:00
Um kleinere Tablets zu bedienen, müsse man sich die Finger abschmirgeln, wetterte Apple-Gründer Steve Jobs noch 2010. Zwei Jahre später stellte Apple dennoch ein iPad mini vor – in Reaktion auf die Konkurrenz.

Nach dem LiMux-Aus: München ernennt neuen IT-Referenten

heise online Newsticker - 25. Oktober 2017 - 10:00
Der Münchner Stadtrat hat den Informatiker Thomas Bönig zum Leiter des neuen IT-Referats gewählt. Der 55-Jährige soll die kommunale Informations- und Kommunikationstechnik neu organisieren. Heikelster Punkt: Die Rückmigration zu Microsoft.

Entwickler: Google Play Store gleicht App-Kosten an Apple an

heise online Newsticker - 25. Oktober 2017 - 10:00
Für Entwickler senkt Google künftig die Gebühren auf in-App Abonnements im Play Store und gleicht sich damit Apple an.

MSI Cubi 3 Silent: 4K-fähige Mini-PCs ohne Lüfter

heise online Newsticker - 25. Oktober 2017 - 9:30
MSI stellt zwei neue Mini-PCs vor, die 4K-Bildschirme ansteuern und dank Kaby-Lake-U-Prozessoren ausreichend Leistung für Büroarbeiten bieten.

US-Lebensversicherer verkauft Apple Watch für 25 Dollar – bei genügend Training

heise online Newsticker - 25. Oktober 2017 - 9:00
10 Millionen Versicherte können Apples neue Computer-Uhr nun für 25 Dollar erhalten, wenn sie ihre Fitnessdaten dafür preisgeben. Wer zu wenig trainiert, muss draufzahlen.

2-Schritt-Verifizierung: Google macht Prompt zum Standard

heise online Newsticker - 25. Oktober 2017 - 8:00
Bisher stellten SMS die Default-Einstellung für Googles Verifizierung in zwei Schritten dar. Sie werden jetzt vom so genannten Prompt abgelöst, der ganz ohne Bestätigungscodes auskommt.

EU-Grundrechtsagentur fordert bessere Geheimdienstkontrolle

heise online Newsticker - 25. Oktober 2017 - 8:00
Nach den Snowden-Enthüllungen haben einige EU-Staaten die Gesetze für ihre Geheimdienste reformiert. Der Rechtsrahmen bleibe trotzdem oft vage, solide Schutzmaßnahmen und eine wirksame Aufsicht fehlten, kritisiert die Grundrechtsagentur.

Open Source Summit 2017: Die neue CDLA und drei neue Guides

heise online Newsticker - 25. Oktober 2017 - 8:00
Wie sollen Unternehmen mit frei verfügbaren Daten umgehen? Die auf dem Open Surce Summit vorgestellte CDLA soll hierfür Richtlinien vorgeben. Zum Beispiel kann sie verlangen, dass auch verarbeitete Daten wieder frei verfügbar sein müssen.

Google DLP-API schützt sensible Daten in der Cloud

heise online Newsticker - 25. Oktober 2017 - 8:00
Mit neuen Funktionen kann Google Cloud DLP-API über 50 Arten sensibler Daten erkennen und in Echtzeit de-identifizieren oder maskieren, unabhängig davon, wie sie gespeichert sind. Die Beta bekam nun weitere Möglichkeiten zum Schutz vertraulicher Daten.

iPhone-Design-Verletzung: Samsung bekommt neuen Prozess über Schadenszahlung

heise online Newsticker - 25. Oktober 2017 - 8:00
Apple muss in einem neuen Verfahren rechtfertigen, warum Samsung 400 Millionen Dollar für die Verletzung mehrerer iPhone-Geschmacksmuster – darunter ein rechteckiges Gerät mit abgerundeten Ecken – zahlen musste.

Kaspersky wirbt mit "Transparenzinitiative" um Vertrauen

heise online Newsticker - 25. Oktober 2017 - 7:30
In den USA haben sich Regierung und Geheimdienste auf den russischen Antiviren-Spezialist Kaspersky eingeschossen und verbannen die Software aus Russland systematisch von den Behördenrechnern.

Toshiba rechnet erneut mit dickem Verlust

heise online Newsticker - 25. Oktober 2017 - 4:00
Wegen Verzögerungen beim Verkauf seiner Chipsparte revidiert Toshiba seine Prognose für das laufende Geschäftsjahr.

marvil07.net: A release plan for contributed drupal extensions

Planet Drupal - 25. Oktober 2017 - 3:51

tl;dr: Review the plan at the end directly.

Software has a changing nature; Drupal and its extensions are not the exception.
To be useful for a most of the users, those need to be on full releases, not only on the version control system; indeed the problem is not new and there is even a well-known phrase for one of its solutions: release early, release often
Therefore it is important to have a release plan.
Following after some context and reasoning, I propose a couple of practical guidelines on release schedule for contributed drupal extensions that I intend to use: release weekly until stable, then once a month following core shedule.

On the changing nature of software

Software inherently tends to change, there are exceptions like embedded systems or really purpose-specific software.
Even really solid software like GNU core utils project, started on 1992, which provides tools that I consider among the most mature in the software space used daily, has 253 commits and three point releases in the last 12 months[1].

How much a software change depends on many factors.
I would hypothesize that the most relevant factors are the age of the project, the environment around it, and the amount of people behind it.
In this way, new projects change more than well established projects, and projects around dynamic environments which is also influenced by the amount of people around it, will also change more than the ones in environments with less participants or less technology changes.

How changing are contributed drupal extensions?

Drupal contributed extensions are naturally mainly influenced by drupal core, so let us examine a bit how changing is Drupal core.
It is definitely on a dynamic environment, and I will argue that each major release can be considered a new project, making it really changing.

On the dynamic side, even if web standards changes slowly, and for good reasons, technologies around web tools are still constantly changing.
The stack has changed a lot over the years, and even if some tools like apache and mysql/mariadb are still around, other parts of the stack has been changing a lot, especially around client side javascript.

Drupal core project code history is now 17 years old, which seems like enough time to get into a stable state, especially if you are not yet part of the drupal community.
But the drupal project has a history on rewriting the way its internal works, which has been argued as one of the reasons why drupal can keep up with the changing environment around web technologies.
It may be also a consequence of its amazingly collaborative community.
And because of this rewriting between major versions, at least internally, each major release can be considered a new project, especially with 8.x.x.
A hint about it may be reflected in the fact that major contributors across different drupal core versions are mainly different; only a few one are as active across releases.

In consequence, drupal core is still a highly changing project, and in the same way its extensions inherit part of that changing nature; but a contributed drupal extension is not really only influenced by core.
Given the amazingly high number of written extensions, it is only natural to start depending on other software pieces and make its maintenance more effective.
For instance, currently there are 13432 and 4069, D7 and D8 compatible modules respectively.

In this way, one of the factors that will clearly influence a contributed extension is their dependencies, both inside and outside the drupal, and how changing they are.

Another factor is the amount of people behind it, not only developers, but also users reporting bugs.
For drupal contributed extensions this vary a lot, but it is usually not that big.

For all this, contributed drupal extensions are usually in a changing environment.

Commits are not releases: release early, release often

As a contributed module developer myself, I will start by mea culpa.
Sometimes I wrongly assume that when a change is inside git the work is done, but that may be only true for people willing to take the extra effort to get the changes from git, or assume the consecuences of using a development release.
Commits are a developer tool inside the used version control system, but not necessarily something that is visible/usable for all.

As in many occasions, the problem is not new, and I find a pretty good answer for it on "The Cathedral and the Bazaar" chapter 2: Release early, release often.
It mainly propose that to be able to tackle enough bugs to make the software usable, the amount of releases needs to be as fast as the pace of the development, even at the cost of some stability.
I definitely recommend reading it fully for more context, and a lot more inspiring insights for any open source developer.

How often is often? A release strategy plan

Granted, the answer is not a recipe, and it makes sense it is that way because it really depends on the project.
On the following lines I will propose an specific release strategy for drupal contributed extensions.

Drupal core already has a release plan, it is really detailed, so please review it if you have not done it yet.
Minor releases are approximately available every six months, but security and bugfix releases for a given minor version branch are available monthly, on third and first Wednesday respectively.

Security releases for drupal contributed extensions are published in coordination with the security team, so there is no need to plan them here, they also happen on Wednesdays.

Making it simple to remember can help maintainers stick to it, so I will also be using Wednesdays as well as the weekday for releases.

The plan

I propose the following for each supported major branch in contributed extensions:

  • release alpha/beta/rc weekly on Wednesdays, until a stable is ready
  • release bugfix releases once stable has been reached in the same schedule than core, i.e. the first Wednesday of the month;

Looking back, it seems obvious and really simple, but if it is not documented somewhere, I will probably forget about it.
Hopefully someone else finds this useful, or even better wants to do the same.
Having a more predictable schedule always help to make better planning decisions.

I will start this week using this two guidelines and release a new version in the modules I maintain and there are pending changes to be released.

Auto-notify maintainers

Notifications may help us maintainers to stick to this, but I guess the plan itself was relevant enough keep the focus of this post.
I may be exploring some solutions around it in the future.

[1] To reproduce statistics you can retrieve the main repository from https://git.savannah.gnu.org/cgit/coreutils.git and then run a couple of commands:
git log --oneline --all --since="1 year ago" | wc -l git log --oneline --all --since="1 year ago" --decorate | grep tag

Etiquetas:

Agiledrop.com Blog: AGILEDROP: First days on board with A-team

Planet Drupal - 25. Oktober 2017 - 3:05
When new developers arrive in our team, our mission is to help them as much as we can in every aspect of adaption to the new job environment, so they can show their potential and shine in their best light. First days at a new job are really important. Based on first impressions developers form the picture about their new coworkers and about the company itself, and that can have an impact on long-term. We pay great attention to the first days with us, so we prepared a brief insight in first work days at our company. First day We show the new developer around, show the desk and her… READ MORE

Agiledrop.com Blog: AGILEDROP: Why should agencies partner with companies rather than hire freelancers?

Planet Drupal - 25. Oktober 2017 - 1:38
Digital agencies sometimes get in a position when they have more work their internal team can handle. For many outsourcing is not an option, as they still wish to keep the project in the house, but are open to working with external developers. Agencies can hire freelancers or work with teams like AGILEDROP. In this post, I will highlight some of the advantages of working with a team that agencies often overlooked when making a decision. No more job posts and screening interviews Hiring a freelancer is practically the same as hiring a full-time employee. First you have to write a job ad and… READ MORE

Umfrage zu Elektroautos: 5 Prozent erwägen Kauf eines E-Autos

heise online Newsticker - 24. Oktober 2017 - 19:00
Als nächstes Auto kommt für 5 Prozent der Teilnehmer einer Umfrage ein rein elektrisch betriebenes in Frage. Wichtig für die Kaufentscheidung ist vor allem der Anschaffungspreis und die Reichweite.

Manifesto: City of Drupal: thoughts on DrupalCon Vienna 2017

Planet Drupal - 24. Oktober 2017 - 18:51
It seems like a long time ago now… Well. It was…. At the time of writing, it’s three weeks since I was at DrupalCon. I could argue I’ve been taking time for reflection, but actually we’ve been super busy and so I’m just getting round to penning my thoughts and memories of my week in. Continue reading...

Sexuelle Übergriffe: Frauen beschuldigen einflussreichen US-Technikblogger Robert Scoble

heise online Newsticker - 24. Oktober 2017 - 18:30
Die US-Journalistin Quinn Norton schildert sexuelle Übergriffe der amerikanischen Technikblogger-Größe Robert Scoble, woraufhin sich weitere Betroffene melden.