Why can't we do it both ways?
Leave the internal versioning system numbers as selected by the core developers alone.
Tag a specific version once or twice a year and call it "Release (%02d)YR.MN version Real Version#" ?
Mailing lists / lazarus / 2009-12
Release 1.0, part 3 / Why can't we do it both ways?
6 messages · 5 people · –
- Michael Joyner 2
- Florian Klaempfl 1
- Helmut Hartl 1
- Osvaldo Filho 1
- Rigel Rig 1
Reply by email Subscribe to this list Your subscription
Read-only archive. Use j and k to move between messages.
Very good idea!
2009/12/3 Michael Joyner :
Show quoted text 13 lines
Why can't we do it both ways?
Leave the internal versioning system numbers as selected by the core
developers alone.
Tag a specific version once or twice a year and call it "Release (%02d)YR.MN
version Real Version#" ?
--
_______________________________________________
Lazarus mailing list
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Very good idea!
Feel free to start with it :)
Show quoted text 9 lines
2009/12/3 Michael Joyner :
> Why can't we do it both ways?
>
> Leave the internal versioning system numbers as selected by the core
> developers alone.
> Tag a specific version once or twice a year and call it "Release (%02d)YR.MN
> version Real Version#" ?
>
Florian Klaempfl wrote 8 lines
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?
Show quoted text 17 lines
> 2009/12/3 Michael Joyner :
>
>> Why can't we do it both ways?
>>
>> Leave the internal versioning system numbers as selected by the core
>> developers alone.
>> Tag a specific version once or twice a year and call it "Release (%02d)YR.MN
>> version Real Version#" ?
>>
>>
--
_______________________________________________
Lazarus mailing list
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20091203/dfc8d347/attachment.html>
Show quoted text 13 lines
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.freepascal.org/pipermail/lazarus/attachments/20091203/59eede9a/attachment-0001.html>
Very good idea! If this is a stable version that is tested on a OS, no problems with installation and detailed installation instructions, with all working examples.
Show quoted text 18 lines
??: Michael Joyner
???????: [Lazarus] Release 1.0, part 3 / Why can't we do it both ways?
??: Lazarus mailing list
????????? ??: ?????????, 2009, ???????? 3 16:42:48 EET
Why can't we do it both ways?
Leave the internal versioning system numbers as selected by the core
developers alone.
Tag a specific version once or twice a year and call it "Release
(%02d)YR.MN version Real Version#" ?
--
_______________________________________________
Lazarus mailing list
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
----------------------------------------------------------------- ????? ???????? ?????? ?? Vesti.bg!
http://www.vesti.bg