{"id":1286,"date":"2007-07-03T16:28:49","date_gmt":"2007-07-03T14:28:49","guid":{"rendered":"http:\/\/vizZzion.org\/blog\/2007\/07\/releasing\/"},"modified":"2007-07-03T16:28:49","modified_gmt":"2007-07-03T14:28:49","slug":"releasing","status":"publish","type":"post","link":"https:\/\/vizZzion.org\/blog\/2007\/07\/releasing\/","title":{"rendered":"releasing."},"content":{"rendered":"<blockquote><p>\n        Father&#8230;ooh&#8230;oh&#8230;oh&#8230;<br \/>\n        I see the world, feel the chill<br \/>\n        Which way to go, windowsill<br \/>\n        I see the worlds on a rocking horse of time<br \/>\n        I see the verse in the rain<br \/>\n        Ohh&#8230;ohh&#8230;ohh&#8230;ohh&#8230;\n\t<\/p><\/blockquote>\n<p>\t<em>Pearl Jam &#8211; &#8220;Release&#8221;<\/em><\/p>\n<p \/>\n \t Mark Shuttleworth talked about what he thinks is a sensible<br \/>\n\t release rhythm. While you probably all know his proposal, here&#8217;s what I&#8217;m thinking about<br \/>\n\t releasing every six months (or in regular intervals anyway) and synchronising our releases with<br \/>\n\t the release of other Free Software communities.<\/p>\n<p \/>\n\t Right now, we can say very little about KDE4. We will have to see how KDE4 pans out. My expectation is that it&#8217;ll<br \/>\n\t prove to be a reliable and stable platform that will suffer from little regressions after 4.0 is out. That means that<br \/>\n\t we should be able to put out a snapshot every so often and use some weeks (6, 8 maybe?) to stabilise it. Time-based<br \/>\n\t releases are possible in this scenario, but we should ask ourselves if we want to release on a regular basis (and in some cases<br \/>\n\t postpone shipping some new feature because it would&#8217;ve needed three more weeks to finish and polish).<\/p>\n<p>\t On the other hand, KDE3 releases were very reliable. If I recall correctly, we only slipped once or twice slightly due to a<br \/>\n\t security problem (which would affect time-bases releases in the same way). So practically, we <strong>have<\/strong> time-based<br \/>\n\t releases for some time already.<\/p>\n<p>\t What we can do to make it easier for vendors to ship the next version of our software is making it clear what needs to be done<br \/>\n\t before a release. That would mean: <em>&#8220;Here&#8217;s a list with what the next release will look like, if you want to make it happen<br \/>\n\t earlier, help us hacking&#8221;<\/em> This could be as easy as recording this in bugzilla, marking it as &#8220;showstopper&#8221; or &#8220;required<br \/>\n\t for x.y.z&#8221; and then make the query showing those entries easily accessible through, for example, a direct link.<\/p>\n<p \/>\n\t As to a <em>pulse<\/em> and having Free Software communities release at the same point in time would<br \/>\n\t &#8212; from a marketing point of view &#8212;<br \/>\n\t be a very bad idea. It would mean two things: Press coverage for Free Software only once in a while,<br \/>\n\t and smaller projects being snowed<br \/>\n\t under by those that are doing better PR work. I&#8217;m actually wondering why this is brought up by Mark since Canonical&#8217;s<br \/>\n\t umbrella branding fails miserably in this respect &#8212; measured by the press coverage that a Kubuntu release has got during the<br \/>\n\t last cycles.<\/p>\n<p \/>\n","protected":false},"excerpt":{"rendered":"<p>Father&#8230;ooh&#8230;oh&#8230;oh&#8230; I see the world, feel the chill Which way to go, windowsill I see the worlds on a rocking horse of time I see the verse in the rain Ohh&#8230;ohh&#8230;ohh&#8230;ohh&#8230; Pearl Jam &#8211; &#8220;Release&#8221; Mark Shuttleworth talked about what he thinks is a sensible release rhythm. While you probably all know his proposal, here&#8217;s&hellip; <a class=\"more-link\" href=\"https:\/\/vizZzion.org\/blog\/2007\/07\/releasing\/\">Continue reading <span class=\"screen-reader-text\">releasing.<\/span> <span class=\"meta-nav\" aria-hidden=\"true\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[29],"tags":[],"class_list":["post-1286","post","type-post","status-publish","format-standard","hentry","category-kde"],"_links":{"self":[{"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/posts\/1286","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/comments?post=1286"}],"version-history":[{"count":0,"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/posts\/1286\/revisions"}],"wp:attachment":[{"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/media?parent=1286"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/categories?post=1286"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/tags?post=1286"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}