[prev in list] [next in list] [prev in thread] [next in thread] 

List:       koffice-devel
Subject:    Re: Bugs against the Essen branch
From:       Inge Wallin <inge () lysator ! liu ! se>
Date:       2010-09-23 12:09:10
Message-ID: 201009231409.11260.inge () lysator ! liu ! se
[Download RAW message or body]

On Thursday, September 23, 2010 12:47:09 Cyrille Berger wrote:
> On Thursday 23 September 2010, LukasT.dev@gmail.com wrote:
> > On Thursday 23 September 2010 11:59:33 zander@kde.org wrote:
> > > the
> > > question is why Nokia is forking off the main branch in the first
> > > place. The  main branch is stabilized for release and Nokia is
> > > intending to release too. So why the hell are we not using the same
> > > codebase?
> > 
> > Sorry, but I find this clear, at least for me. First they can do whatever
> > they want and what they need. They don't work on KOffice just for fun and
> > they need to deliver.
> 
> Yup, and this is totally acceptable.
> 
> However, it is true that using bugzilla for bugs tested against that branch
> does not work well. Unless the bugs are correctly flaged as LATER or INFO.

So, is this the consensus then?  To indeed add the bugs and use status LATER? 
INFO seems strange to me since the info is supposed to be in the bug already.

> As for the commits of patch that are not accepted by the community, there
> will be a review before merge. So it is unlikely they will be accepted
> later.

Of course.  Nobody has said anything else.  The branch is used for features 
that are in principle accepted but cannot go in yet due to feature freeze and 
patches that are not in a state yet to be accepted by the community. 
_______________________________________________
koffice-devel mailing list
koffice-devel@kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel
[prev in list] [next in list] [prev in thread] [next in thread]