<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: OSGi.does.not.like.5 token versions</title>
	<atom:link href="http://www.lunar-ocean.com/blog/osgidoesnotlike5-token-versions/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.lunar-ocean.com/blog/osgidoesnotlike5-token-versions/</link>
	<description>Always one character away from perfetcion</description>
	<pubDate>Wed, 19 Nov 2008 22:18:49 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Antoine Toulme</title>
		<link>http://www.lunar-ocean.com/blog/osgidoesnotlike5-token-versions/#comment-23</link>
		<dc:creator>Antoine Toulme</dc:creator>
		<pubDate>Mon, 25 Jun 2007 17:26:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.lunar-ocean.com/blog/osgidoesnotlike5-token-versions/#comment-23</guid>
		<description>Thanks guys, I will keep that in mind for the next builds. For now keeping a build number a la SWT makes more sense to us. In time we'll switch gently.</description>
		<content:encoded><![CDATA[<p>Thanks guys, I will keep that in mind for the next builds. For now keeping a build number a la SWT makes more sense to us. In time we&#8217;ll switch gently.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick Boldt</title>
		<link>http://www.lunar-ocean.com/blog/osgidoesnotlike5-token-versions/#comment-22</link>
		<dc:creator>Nick Boldt</dc:creator>
		<pubDate>Mon, 25 Jun 2007 17:15:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.lunar-ocean.com/blog/osgidoesnotlike5-token-versions/#comment-22</guid>
		<description>Agreed -- use something alphabetic for the 4th part. However, nothing stops you from doing something like 1.0.0.v200706251234, which not only adds more information (a datestamp) than 1.0.0.foo, but also guarantees that integration builds in a branch will be able to install on top of older ones (and the Update Manager wizard will respect that too).

I think all the bugs around use of "_" in qualifiers have been squashed by now, but just in case I recommend avoiding the use of underscores in favour of dashes, thus: 1.0.0.v200706251234-something-else-useful-here.</description>
		<content:encoded><![CDATA[<p>Agreed &#8212; use something alphabetic for the 4th part. However, nothing stops you from doing something like 1.0.0.v200706251234, which not only adds more information (a datestamp) than 1.0.0.foo, but also guarantees that integration builds in a branch will be able to install on top of older ones (and the Update Manager wizard will respect that too).</p>
<p>I think all the bugs around use of &#8220;_&#8221; in qualifiers have been squashed by now, but just in case I recommend avoiding the use of underscores in favour of dashes, thus: 1.0.0.v200706251234-something-else-useful-here.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex Blewitt</title>
		<link>http://www.lunar-ocean.com/blog/osgidoesnotlike5-token-versions/#comment-21</link>
		<dc:creator>Alex Blewitt</dc:creator>
		<pubDate>Sat, 23 Jun 2007 19:53:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.lunar-ocean.com/blog/osgidoesnotlike5-token-versions/#comment-21</guid>
		<description>Note that OSGi only supports 3 numeric identifiers; the 4th one is textual. So if you have 1.2.3.10, that's less than 1.2.3.4. 

Bottom line: only use 3 numeric identifiers, and start the 4th with an alphabetic, even if you're going to include numeric/date version information there to make it clear it's not numeric.

alex.</description>
		<content:encoded><![CDATA[<p>Note that OSGi only supports 3 numeric identifiers; the 4th one is textual. So if you have 1.2.3.10, that&#8217;s less than 1.2.3.4. </p>
<p>Bottom line: only use 3 numeric identifiers, and start the 4th with an alphabetic, even if you&#8217;re going to include numeric/date version information there to make it clear it&#8217;s not numeric.</p>
<p>alex.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Antoine Toulme</title>
		<link>http://www.lunar-ocean.com/blog/osgidoesnotlike5-token-versions/#comment-20</link>
		<dc:creator>Antoine Toulme</dc:creator>
		<pubDate>Sat, 23 Jun 2007 19:10:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.lunar-ocean.com/blog/osgidoesnotlike5-token-versions/#comment-20</guid>
		<description>oh thanks, I was still hanging to this one:

http://dev.eclipse.org/mhonarc/lists/equinox-dev/msg00301.html</description>
		<content:encoded><![CDATA[<p>oh thanks, I was still hanging to this one:</p>
<p><a href="http://dev.eclipse.org/mhonarc/lists/equinox-dev/msg00301.html" rel="nofollow">http://dev.eclipse.org/mhonarc/lists/equinox-dev/msg00301.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Aniszczyk</title>
		<link>http://www.lunar-ocean.com/blog/osgidoesnotlike5-token-versions/#comment-18</link>
		<dc:creator>Chris Aniszczyk</dc:creator>
		<pubDate>Sat, 23 Jun 2007 18:37:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.lunar-ocean.com/blog/osgidoesnotlike5-token-versions/#comment-18</guid>
		<description>Eclipse has guidelines for version numbering that I can recommend for you: http://wiki.eclipse.org/index.php/Version_Numbering</description>
		<content:encoded><![CDATA[<p>Eclipse has guidelines for version numbering that I can recommend for you: <a href="http://wiki.eclipse.org/index.php/Version_Numbering" rel="nofollow">http://wiki.eclipse.org/index.php/Version_Numbering</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
