Rules to be approved as part of KDE Frameworks

[Aaron J. Seigo]

On Monday, June 6, 2011 19:41:15 Maksim Orlovich wrote:
> >  * all new features will be developed using the recommended git
> >  workflow
> > 
> > (pending publication; Cornelius is working on that one);
> > 
> > Those rules might seem like a strong departure from what we're used to.
> > On the other hand, if you look at them closely, they are merely making
> > explicit changes to our habits which already happened a while ago
> > during the Qt 3 to Qt 4 port
> 
> These two things don't really go well together now, do they?

a documented git workflow is new, but needed. ditto with the tier/type 
concepts. 

the other items are as described in the second paragraph, however.

is this problematic for you in some way? if so, can you clarify what that 
problem is so that we may understand and be able to address it?

-- 
Aaron J. Seigo
humru othro a kohnu se
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

KDE core developer sponsored by Qt Development Frameworks
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20110607/602e1bb1/attachment.sig>