[prev in list] [next in list] [prev in thread] [next in thread]
List: kdevelop-devel
Subject: Re: Creation of kdevplatform module
From: Alexander Neundorf <neundorf () kde ! org>
Date: 2007-05-03 2:26:14
Message-ID: 200705022226.15185.neundorf () kde ! org
[Download RAW message or body]
On Wednesday 02 May 2007 11:33, Matt Rogers wrote:
> On May 2, 2007, at 8:05 AM, Allen Winter wrote:
...
> > IF we were to do this.. then
> > + The new module should be in place by 8 May.
> > + The libs code should follow typical kdelibs coding policies and
> > licensing
> > requirements by the first beta release (25 June). And kdevelop
> > and quanta
> > should be using it.
>
> Is following kdelibs coding policies a requirement? KDevelop has its
> own coding style. Why can't we just follow that? What happens if it
> won't be ready for KDE 4.0 (which it won't be)?
IMO kdevelop is a project with releases independent from KDE (as koffice) and
as such can have its own policies, in coding style, release management and
others.
Bye
Alex
_______________________________________________
KDevelop-devel mailing list
KDevelop-devel@kdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic