It's a year and one release since rebranding rename of git packages and all everything... But tarball packages placed on the ofitial page are still named with kde- prefix. The page I ment: http://trinity.blackmag.net/releases/3.5.13.1/downloads.html.
On Tuesday 23 of October 2012 20:44:36 Fat-Zer wrote:
It's a year and one release since rebranding rename of git packages and all everything... But tarball packages placed on the ofitial page are still named with kde- prefix.
This is absolutely in order, because these are packages are for a 3.5.13 branch - ie before renaming kde => tde.
Slavek --
It's a year and one release since rebranding rename of git packages and all everything... But tarball packages placed on the ofitial page are still named with kde- prefix.The page I ment: http://trinity.blackmag.net/releases/3.5.13.1/downloads.html.
That is correct. Renaming efforts began after 3.5.13. As 3.5.13.1 is a bug fix patch set to 3.5.13, none of the renaming was back ported. :)
Darrell
2012/10/23 Darrell Anderson humanreadable@yahoo.com
That is correct. Renaming efforts began after 3.5.13. As 3.5.13.1 is a bug fix patch set to 3.5.13, none of the renaming was back ported. :)
Ok... bye the way, do you plan any version «rebranding»?
Sorry for offtoping in the tred and if this subject already was raised on the mail list what plans do you (i mean the Trinity project) have? The roadmap is really outdated...
Ok... bye the way, do you plan any version «rebranding»?
The next official release will be R14.0.0.
Rx.x.x will be the new version string.
Check the mail list archives for those conversations a long time ago. Basically, the 14 represents the 14th release in the KDE 3.5.x series, but represents our own version string to further provide a break from KDE.
Darrell
2012/10/23 Darrell Anderson humanreadable@yahoo.com
Ok... bye the way, do you plan any version «rebranding»?
The next official release will be R14.0.0.
Rx.x.x will be the new version string.
Check the mail list archives for those conversations a long time ago. Basically, the 14 represents the 14th release in the KDE 3.5.x series, but represents our own version string to further provide a break from KDE.
Darrell
Thanks... I'm really regret that I stopped reading the maillist a year ago...
And the last question: what will be with the Qt version? Now the tarball package is numbered with trinty version... but qmake -v returns "Qmake version: 1.07a (Qt 3.3.8d) 3.3.8d"
Thanks... I'm really regret that I stopped reading the maillist a year ago...
And the last question: what will be with the Qt version? Now the tarball package is numbered with trinty version... but qmake -v returns "Qmake version: 1.07a (Qt 3.3.8d) 3.3.8d"
Qt3 is maintained for historical reasons but builds are expected to be perfomed against TQt3. The current version is 3.5.0, implying, yes, ABI changes.
When built in TQt3, qmake is renamed to tqmake and returns the following:
Qmake version: 1.07a (TQt 3.5.0)
This is with the R14 development branch.
Darrell
2012/10/24 Darrell Anderson humanreadable@yahoo.com
Qt3 is maintained for historical reasons but builds are expected to be perfomed against TQt3. The current version is 3.5.0, implying, yes, ABI changes.
When built in TQt3, qmake is renamed to tqmake and returns the following:
Qmake version: 1.07a (TQt 3.5.0)
This is with the R14 development branch.
Darrell
And for dot the i's: after the release of R14 this numeration will be kept? it still will be numbered 3.5.x ?
And for dot the i's: after the release of R14 this numeration will be kept? it still will be numbered 3.5.x ?
I presume 3.5.x. Possibly some day with a serious ABI change the version might bump to 3.6.x. Currently only Tim modifies (T)Qt3 and would know best.
Darrell
-
Darrell Anderson -
Fat-Zer -
Slávek Banko