Dolphin Frameworks version

Frank Reininghaus frank78ac at googlemail.com
Wed Jun 4 21:05:58 BST 2014


Hi,

2014-06-03 13:13 GMT+02:00 Todd:
> On 3 Jun 2014 09:33, "Frank Reininghaus" wrote:
>>
>> Hi,
>>
>> since people have started to find bugs in the frameworks branch, we
>> should probably create a new version at bugs.kde.org (currently, all
>> these bugs have the version 'unspecified').
>>
>> We have been using the version of kdelibs, i.e., KDE_VERSION_STRING,
>> for some time, but I think that this does not make much sense for the
>> frameworks branch because the release schedules of the frameworks
>> libraries and the applications will not be in sync. Moreover, a
>> version like "5.0.0" would make people believe that the Qt5/KF5-based
>> Dolphin is a stable product which is ready for end-users, but that is
>> currently not the case.
>>
>> I propose to use a version like 4.80, which makes it clear that it's
>> unstable, and which is greater than all previous Dolphin versions. If
>> there are better ideas, please reply to this message :-) If that is
>> not the case, I'll change the version in the code and create the
>> version at bugs.kde.org in the next few days.
>>
>> Thanks and best regards,
>> Frank
>
> Overall I think it is a good idea.
>
> My only suggestion would be to start with a lower number, 60 maybe, so you
> have some additional room to play with.  I probably would wait to move to
> the 80+ range until there is a formal alpha or beta release schedule.
>
> Starting with a lower number will give you some room just in case you decide
> to have more fine-grained numbering.  If you start with 80 now, it would be
> harder later to decide to do weekly snapshots, for example.  Not that you
> necessarily would do that, my point is just that a lower starting number
> gives you more flexibility to change your plans later.

yes, that makes sense! Thanks for the suggestion.

I've changed the version in the frameworks branch to 4.60 and added
that version in bugs.kde.org.

Best regards,
Frank




More information about the kfm-devel mailing list