Stopping release of kdewebdev for Applications 16.08

Albert Astals Cid aacid at kde.org
Tue Oct 25 21:40:12 UTC 2016


El dilluns, 17 d’octubre de 2016, a les 20:31:50 CEST, Nicolás Alvarez va 
escriure:
> 2016-10-06 19:44 GMT-03:00 Albert Astals Cid <aacid at kde.org>:
> > El dimecres, 5 d’octubre de 2016, a les 22:06:22 CEST, Ben Cooksley va
> > 
> > escriure:
> >> On Wed, Oct 5, 2016 at 10:46 AM, Luigi Toscano <luigi.toscano at tiscali.it>
> > 
> > wrote:
> >> > Albert Astals Cid ha scritto:
> >> >> El dimecres, 13 de juliol de 2016, a les 1:27:21 CEST, Albert Astals
> >> >> Cid
> >> >> va
> >> >> 
> >> >> escriure:
> >> >>> El divendres, 8 de juliol de 2016, a les 11:50:44 CEST, Andreas
> >> >>> Sturmlechner>>>
> >> >>> 
> >> >>> va escriure:
> >> >>>> On Friday, 8 July 2016 at 11:11, Luigi Toscano wrote:
> >> >>>>> On Friday 08 of July 2016 11:03:05 Andreas Sturmlechner wrote:
> >> >>>>>> None of them were ported yet, in fact they haven't seen commits in
> >> >>>>>> years.
> >> >>>>>> They should probably be converted to git, still, but imo no need
> >> >>>>>> to
> >> >>>>>> keep
> >> >>>>>> it releasing.
> >> >>>>> 
> >> >>>>> Some of them could be probably dropped, but also isn't it possible
> >> >>>>> that
> >> >>>>> they slipped out of the radar because not on git? Would it be
> >> >>>>> possible
> >> >>>>> to
> >> >>>>> have them converted first and see if this changes?
> >> >>>> 
> >> >>>> kommander and kfilereplace are not actually webdev related, so could
> >> >>>> be
> >> >>>> moved into other categories (kdeutils?) if not dropped.
> >> >>>> 
> >> >>>> Not sure how many people still do image maps (so chances this will
> >> >>>> be
> >> >>>> picked up again are slim), and klinkstatus still depends on
> >> >>>> kdepimlibs-4
> >> >>>> to build.
> >> >>> 
> >> >>> Let's move them to git first and then decide if we want to drop them
> >> >>> or
> >> >>> not.
> >> >>> 
> >> >>> Given the freeze for KDE Applications 16.08 is like in 2 days i would
> >> >>> not
> >> >>> rush for now, let's all make a note for 2.5 months and decide if we
> >> >>> want
> >> >>> to
> >> >>> release them for KDE Applications 16.12.
> >> >> 
> >> >> So it's 2.5 months later now.
> >> >> 
> >> >> I would like to get them moved to git if possible, get them released
> >> >> for
> >> >> KDE Applications 16.12 and tell people they need to start caring about
> >> >> them if they don't want to see them dropped for 17.04
> >> >> 
> >> >> Now the question is, how do we get them into git?
> >> > 
> >> > I think that sysadmins have (or had) a system dedicated to SVN-to-git
> >> > conversion, and also the examples of the old conversions. There are
> >> > some
> >> > instructions here:
> >> > https://techbase.kde.org/Projects/MoveToGit/UsingSvn2Git
> >> 
> >> We had such a system - all such machines have since been shutdown though.
> >> I think Nicolas has a container on one of our machines which he does
> >> the occasional conversion which gets requested in, but it has been a
> >> long time since that was last used if I recall correctly.
> > 
> > Any way i can get that 65G svn file somehow or we can't port anything else
> > from svn to git?
> > 
> > Or Nicolás can I convince you to git-ify kdewebdev?
> 
> It's done! Please review:
> kde:scratch/nalvarez/kdewebdev-kfilereplace
> kde:scratch/nalvarez/kdewebdev-kimagemapeditor
> kde:scratch/nalvarez/kdewebdev-klinkstatus
> kde:scratch/nalvarez/kdewebdev-kommander

I don't think much changes happened but the branches from
https://websvn.kde.org/branches/Applications/
are missing (i.e. you only have the KDE/XXX ones), would it be much work to 
get them in?

Cheers,
  Albert

> 
> The history seems to be complete, but I haven't tested if the latest
> master compiles etc. I think they rely on the global
> kdewebdev/CMakeLists.txt and don't build standalone.
> 
> I also need to know where to push the final git repos. Should I create
> a kdewebdev module in repo-metadata? And what needs to be done with
> i18n for a svn->git move?




More information about the release-team mailing list