<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=windows-1252"
http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Michael Joyner schrieb:
<blockquote cite="mid:4B17E19B.80809@ewc.edu" type="cite">
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
Florian Klaempfl wrote:
<blockquote cite="mid:4B17D7FD.7060807@freepascal.org" type="cite">
<pre wrap="">Osvaldo Filho schrieb:
</pre>
<blockquote type="cite">
<pre wrap="">Very good idea!
</pre>
</blockquote>
<pre wrap=""><!---->
Feel free to start with it :)
</pre>
</blockquote>
What would be the best way to have this display to the end-user does
one think?<br>
What kind of display in the splash logo and about boxes?<br>
What should the communication process be to the different distros?</blockquote>
<br>
We do it for our resellers that way, that we have a full test
(Automated QA / Testcomplete) of one specific SVN release number.<br>
In the build process our svn release number is stored in the binary as
resource string and can be retrieved.<br>
Our customer(=reseller) uses special branding files, like themes, skins
and so on to produce his wanted output.<br>
<br>
The support is in three layers enduser -> reseller(=our customer)
-> us. (3rd level)<br>
<br>
If you want to apply that to the Lazarus model you would need a special
tagging and releasing layer (group/persons/individuals),<br>
which do all the tests relieving the pressure from the development
crew. They need to communicate with the distros <br>
and with the developers. <br>
<br>
(The development crew usually want to develop and not to test and
release, as this is much (underestimated) work)<br>
<br>
This model works quite good for us, but endusers often get scr*wed by
the reseller layer, cause they also don't<br>
like to work more than they need. :-), on the other hand we can develop
in peace ...<br>
<br>
BTW: We are a 2 men show ... :-)<br>
<br>
Helmut<br>
<br>
</body>
</html>