[Lazarus] Release 1.0, part 3 / Why can't we do it both ways?

Helmut Hartl helmut.hartl at firmos.at
Thu Dec 3 17:55:58 CET 2009


Michael Joyner schrieb:
> Florian Klaempfl wrote:
>> Osvaldo Filho schrieb:
>>   
>>> Very good idea!
>>>     
>>
>> Feel free to start with it :)
>>
>>   
> What would be the best way to have this display to the end-user does
> one think?
> What kind of display in the splash logo and about boxes?
> What should the communication process be to the different distros?

We do it for our resellers that way, that we have a full  test
(Automated QA / Testcomplete) of one specific SVN release number.
In the build process our svn release number is stored in the binary as
resource string and can be retrieved.
Our customer(=reseller) uses special branding files, like themes, skins
and so on to produce his wanted output.

The support is in three layers enduser -> reseller(=our customer) -> us.
(3rd level)

If you want to apply that to the Lazarus model you would need a special
tagging and releasing layer (group/persons/individuals),
which do all the tests relieving the pressure from the development crew.
They need to communicate with the distros
and with the developers.

(The development crew usually want to develop and not to test and
release, as this is much (underestimated) work)

This model works quite good for us, but endusers often get scr*wed by
the reseller layer, cause they also don't
like to work more than they need. :-), on the other hand we can develop
in peace ...

BTW: We are a 2 men show ... :-)

Helmut

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus-ide.org/pipermail/lazarus/attachments/20091203/59eede9a/attachment-0004.html>


More information about the Lazarus mailing list