напиÑане Thu, 09 Jul 2015 00:22:03 +0300, Burkhard Lück <lueck at hube-lueck.de>:
> Am Mittwoch, 8. Juli 2015, 20:09:34 schrieb Yuri Chornoivan: >> напиÑане Wed, 08 Jul 2015 19:56:03 +0300, Burkhard Lück >> >> > >> > our pages on techbase (Projects/Documentation + KDE4_(health_table) >> are >> > still >> > about kde4, with the kde4 modules kdebase-workspace, kdebase-runtime >> etc. >> > >> > From my pov it is time to track KF5 (Frameworks, Workspace) instead of >> > the >> > corresponding kde4 modules, so we should have Frameworks + Workspace + >> > application modules + extragear modules + playground modules. >> > >> >> Having too much pages for every numbered release just makes the thing >> more >> complicated that it should, imho. > > You got me wrong or probably I did not explain it very well, sorry. I > don't > want to have more pages. > >> Can we just mark the KF5-based releases >> somehow? May it be that just a multiplication sign (*) will be enough >> for >> KF5? >> > I believe this will lead to great confusion, there are too many kf5 > docbooks > which moved to another repo. > > * I am pretty sure there will be no kde4 docbook updates for code which > is > already kf5 - any docbook update will happen for the kf5 version in this > case > > * we tracked always the devel status in the health table to have an > overview > of the status, see what was outdated and what could be backported, > therefore > we need to track kf5 here > > * we have ~ 50 kf5 docbooks (frameworks + ~35 kcm docbooks + a few app > docbooks), too many to mix this with the kde4 status into one table > > What I have in mind is to delete everything in kdelibs/kde-runtime/kde- > baseapps which is no longer in kf5 and move the rest into the proper kf5 > modules frameworks, workspace etc. > >> I can do anything needed. >> > Thanks for stepping up Ok. I understand. Will be done during the next few days. Best regards, Yuri
