<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Graeme Geldenhuys wrote:
<blockquote
cite="mid:cfcebe780911290630k76ab563eu4ac9ad9dd03f1e0@mail.gmail.com"
type="cite">
<pre wrap="">2009/11/29 Marco van de Voort <a class="moz-txt-link-rfc2396E" href="mailto:marcov@stack.nl"><marcov@stack.nl></a>:
</pre>
<blockquote type="cite">
<pre wrap="">At least it will put this kind of nonsensical discussions to rest
(which is exactly why Patrick did this)
</pre>
</blockquote>
<pre wrap=""><!---->
That does actually make sense.
So maybe Lazarus should start releasing using "year.revision"
eg:
Next release: Lazarus 2010
If another release in the same year: Lazarus 2010.1
The following year: Lazarus 2011
I know of quite a lot of software that uses this version numbering
approach. And as you say, that might put an end to this discussion.
</pre>
</blockquote>
<font face="Aboriginal Sans">It would also eliminate any confusion as
what version of toolset you are using. If it wasn't for that Linux
Journal magazine getting me to actually try the IDE combined with a
very cheap Delphi 4 book, I wouldn't be here. I am a systems
administrator in need of a true RAD environment, and after learning
basic Object Pascal over the last two weeks or so, I think this type of
kit is sorely needed by many more than me, but things like version
numbers definitely count to people like me. When I see '0.9.XXX', my
first thought is, "YOUNG" project, not mature yet. If the team switches
to YEAR numbering, combined with a very clear blurb on the main web
site indicating how long the project has existed, along with a clearly
defined release schedule (changes between 'official' releases don't
have to be much, just improvements and bugfixes), you could definitely
attract more users from which, eventually, more developers will grow
from. You are not going to get more developers unless and until more
people begin to develop stuff using the Lazarus. They have to have a
reason to become a developer, providing them with a tool that they can
use to scratch their own itches, so to speak, is a way to begin having
people learn Object Pascal. Until people learn Object Pascal, there
will be no developers to pull in.<br>
<br>
</font><br>
<pre class="moz-signature" cols="72">--
LyX: <a class="moz-txt-link-freetext" href="http://www.lyx.org/">http://www.lyx.org/</a> OpenOffice: <a class="moz-txt-link-freetext" href="http://www.openoffice.org/">http://www.openoffice.org/</a>
Inkscape: <a class="moz-txt-link-freetext" href="http://www.inkscape.org/">http://www.inkscape.org/</a> Scribus: <a class="moz-txt-link-freetext" href="http://www.scribus.net/">http://www.scribus.net/</a>
GIMP: <a class="moz-txt-link-freetext" href="http://www.gimp.org/">http://www.gimp.org/</a> PDF: <a class="moz-txt-link-freetext" href="http://www.pdfforge.org/">http://www.pdfforge.org/</a>
</pre>
</body>
</html>