An Entity of Type: organisation, from Named Graph: http://dbpedia.org, within Data Space: dbpedia.org

Release early, release often (also known as ship early, ship often, or time-based releases, and sometimes abbreviated RERO) is a software development philosophy that emphasizes the importance of early and frequent releases in creating a tight feedback loop between developers and testers or users, contrary to a feature-based release strategy. Advocates argue that this allows the software development to progress faster, enables the user to help define what the software will become, better conforms to the users' requirements for the software,and ultimately results in higher quality software. The development philosophy attempts to eliminate the risk of creating software that no one will use.

Property Value
dbo:abstract
  • Release early, release often (auf deutsch: Veröffentliche früh, veröffentliche häufig) ist ein Leitsatz in der Softwareentwicklung, nach dem die häufige Verbreitung minimaler Softwareänderungen anzustreben ist. Zu vermeiden sei hingegen die seltene Veröffentlichung komplexer Funktionsumfänge. Geprägt wurde der Leitsatz von Eric S. Raymond in seinem Essay Die Kathedrale und der Basar im Jahre 1997. Release early, release often war zunächst auf Open Source beschränkt, aber es wird auch proprietäre Software nach dem Konzept entwickelt. Allgemein findet das Konzept in agilen Vorgehensmodellen wie Extreme Programming und Scrum Anwendung. Raymonds Richtlinie enthält zusätzlich den Nebensatz And listen to your customers, auf deutsch Und höre auf deine Kunden. (de)
  • Release early, release often (abreviado RERO, en castellano: publicar temprano, publicar a menudo) es una filosofía de desarrollo de software que subraya la importancia de la publicaciones (release) tempranas y frecuente para crear un circuito de retroalimentación rápida entre, por un lado, los desarrolladores y, por el otro lado, los usuarios. Esta filosofía se opone a la estrategia tradicional de difusión basada en proporcionar nuevas características (feature-based). Los partidarios de la filosofía RERO sostienen que permite un desarrollo más rápido, mejora la implicación de los usuarios en la creación del software y favorece el cumplimiento de las expectativas de los usuarios, conduciendo a un software de mejor calidad: El software de código abierto, en el fondo, es un método para maximizar la eficiencia y la rapidez con la que se puede crear la siguiente versión. RERO es el mantra, es decir, abre el código para que millones de ojos pueden desmenuzarlo y ayudar a crear una nueva versión más rápidamente. Andrew Leonard​ Esta práctica se describe como "publicar temprano, publicar a menudo". La comunidad cree que esta práctica conduce a software de mejor calidad, gracias a la revisión por pares y la gran base de usuarios que utilizan el software, acceden al código fuente, informan de bugs, y que contribuyen correcciones. Ibrahim Haddad​ (es)
  • Release early, release often (abrégé en RERO, en français : publiez tôt, publiez souvent) est une philosophie de développement logiciel qui souligne l'importance de diffusions (release) précoces et fréquentes pour créer une boucle de rétroaction rapide entre les développeurs d'une part et les testeurs et les utilisateurs d'autre part. Elle s'oppose à la stratégie traditionnelle de diffusion basée sur les nouvelles fonctionnalités (feature-based). (fr)
  • Release early, release often (also known as ship early, ship often, or time-based releases, and sometimes abbreviated RERO) is a software development philosophy that emphasizes the importance of early and frequent releases in creating a tight feedback loop between developers and testers or users, contrary to a feature-based release strategy. Advocates argue that this allows the software development to progress faster, enables the user to help define what the software will become, better conforms to the users' requirements for the software,and ultimately results in higher quality software. The development philosophy attempts to eliminate the risk of creating software that no one will use. This philosophy was popularized by Eric S. Raymond in his 1997 essay The Cathedral and the Bazaar, where Raymond stated "Release early. Release often. And listen to your customers". This philosophy was originally applied to the development of the Linux kernel and other open-source software, but has also been applied to closed source, commercial software development. The alternative to the release early, release often philosophy is aiming to provide only polished, bug-free releases. Advocates of RERO question that this would in fact result in higher-quality releases. (en)
dbo:wikiPageExternalLink
dbo:wikiPageID
  • 24845611 (xsd:integer)
dbo:wikiPageLength
  • 4939 (xsd:nonNegativeInteger)
dbo:wikiPageRevisionID
  • 1118148962 (xsd:integer)
dbo:wikiPageWikiLink
dbp:wikiPageUsesTemplate
dcterms:subject
gold:hypernym
rdf:type
rdfs:comment
  • Release early, release often (abrégé en RERO, en français : publiez tôt, publiez souvent) est une philosophie de développement logiciel qui souligne l'importance de diffusions (release) précoces et fréquentes pour créer une boucle de rétroaction rapide entre les développeurs d'une part et les testeurs et les utilisateurs d'autre part. Elle s'oppose à la stratégie traditionnelle de diffusion basée sur les nouvelles fonctionnalités (feature-based). (fr)
  • Release early, release often (auf deutsch: Veröffentliche früh, veröffentliche häufig) ist ein Leitsatz in der Softwareentwicklung, nach dem die häufige Verbreitung minimaler Softwareänderungen anzustreben ist. Zu vermeiden sei hingegen die seltene Veröffentlichung komplexer Funktionsumfänge. Geprägt wurde der Leitsatz von Eric S. Raymond in seinem Essay Die Kathedrale und der Basar im Jahre 1997. Raymonds Richtlinie enthält zusätzlich den Nebensatz And listen to your customers, auf deutsch Und höre auf deine Kunden. (de)
  • Release early, release often (abreviado RERO, en castellano: publicar temprano, publicar a menudo) es una filosofía de desarrollo de software que subraya la importancia de la publicaciones (release) tempranas y frecuente para crear un circuito de retroalimentación rápida entre, por un lado, los desarrolladores y, por el otro lado, los usuarios. Esta filosofía se opone a la estrategia tradicional de difusión basada en proporcionar nuevas características (feature-based). (es)
  • Release early, release often (also known as ship early, ship often, or time-based releases, and sometimes abbreviated RERO) is a software development philosophy that emphasizes the importance of early and frequent releases in creating a tight feedback loop between developers and testers or users, contrary to a feature-based release strategy. Advocates argue that this allows the software development to progress faster, enables the user to help define what the software will become, better conforms to the users' requirements for the software,and ultimately results in higher quality software. The development philosophy attempts to eliminate the risk of creating software that no one will use. (en)
rdfs:label
  • Release early, release often (de)
  • Release early, release often (es)
  • Release early, release often (fr)
  • Release early, release often (en)
owl:sameAs
prov:wasDerivedFrom
foaf:isPrimaryTopicOf
is dbo:wikiPageDisambiguates of
is dbo:wikiPageRedirects of
is dbo:wikiPageWikiLink of
is foaf:primaryTopic of
Powered by OpenLink Virtuoso    This material is Open Knowledge     W3C Semantic Web Technology     This material is Open Knowledge    Valid XHTML + RDFa
This content was extracted from Wikipedia and is licensed under the Creative Commons Attribution-ShareAlike 3.0 Unported License