[Kde-extra-gear] Farewell, so long, the four is coming ...

[Helio Chissini de Castro]

On Friday 20 April 2007, Achim Bohnet wrote:
> On Wednesday, 18. April 2007, Helio Chissini de Castro wrote:
> > Ok
> >
> > Let's put some deadline and that's will be the final decision.
> > I'm opening trunk of kde extragear to KDE 4 in exclusively state on day
> > after finish the official freeze of kdelibs. No discussion on this.
> > Someone needs take a position, and following a quote of one of commit of
> > dfaure's "things becoming confused on extragear."
> > So i'm taking position now.
> >
> > During this time, i planned a cleanup in applications as well, so i'll be
> > moving all current trunk for branches/extragear/kde3 and will let on
> > trunk only the apps effectively maintained, and new one's waiting to
> > enter on kde 4 life.
> >
> > What i need from you all you keg application developers:
> >
> > - Is there some special request, non related to your apps only, but for
> > whole module ?
>
> Let the cmake config of a module handle 'DO_NOT_COMPILE' on their own, and
> allow the cmake config of an app to fail if some requirements are missing.

- Noted

> I.e. it should be possible to checkout a module or only one application
> and the 'build mantra' cmake; make etc is in both cases the same.

- Noted too. There's interesting thing to investigate

>  o Where should what happen?  KDE4/KDE3 app developement (trunk),
> maintainance (stable) and releases be done.
>  o What's done by the extragear transition dude and what has to be done by
> the application developers.  Especially i18n stuff.

trunk/extragear - kde 4 extragear
branches/extragear/kde3 - kde 3 extragear
trunk/l10n - kde3 translations
trunk/l10n-kde4 - well, kde4 translations

I will ask sysadmin this weekend to put an acl on extragear tree to avoid 
commits, make the move, and done. People will just need do svn tree adjust.
Don't worry, i'll be making a huge warning on tree lists ( extragear, devel 
and core-devel ) today or tomorrow tops to give time for people commits 
stuff.

> An overview of the task in the life cycle of an application would be nice
> like. Not much text and explanations (if available refer to other pages).
> 	o playground -> extragear (don't forget i18n ;)
> 	o where is what, developement, stable, releases
> 	o how to create a release (inform kde-i18n-doc, release scripts,
> 	  uploading tarballs, announcements ...
> 	o ...

- Noted

> I've also the feeling that often functionality is duplicated in several
> e.g. apps. So a 'how-to' help enhancing KDE framework: eg/module/app/mylib/
> -> eg/lib/mylib -> kdelibs/mylib would be nice.  But I assume this needs
> some 'library-design' experts that mentor the transitions.

Maybe is time to do review on your apps and add libraries top extragear dir, 
then if after is suitable, on next release we will move it for kdelibs ( core 
people can pick easily the lib then )

[]'s

-- 
Helio Chissini de Castro
KDE Developer
Brasil/South America Primary Contact