2.6.0 tag is set on...

[C. Boemann]

On Monday 04 February 2013 19:58:13 Inge Wallin wrote:
> On Monday, February 04, 2013 19:41:34 C. Boemann wrote:
> > On Monday 04 February 2013 19:12:22 Inge Wallin wrote:
> > > On Monday, February 04, 2013 19:04:41 Inge Wallin wrote:
> > > > On Monday, February 04, 2013 18:29:45 C. Boemann wrote:
> > > > 
> > > > But there is something you are missing: If there was such an
> > > > important bug and you didn't feel comfortable reenabling at that
> > > > time we could instead have requested a move of the tagging one day
> > > > forward. That would have given time to test the fix better and even
> > > > re-fix it if more problems had been discovered.
> > > > 
> > > > This is what would have happened if you had discovered a similarly
> > > > important bug in an area that you were responsible for. And in fact
> > > > almost anywhere in Calligra, I'm willing to bet.
> > > 
> > > I realized afterwards that this could be seen as an accusation against
> > > boemann.  This is not what I mean, and I'm sorry for being unclear.
> > > 
> > > What I actually meant was that we had crashes before which then led to
> > > delays, shorter or longer. It wasn't meant to single out anybody.
> > > _______________________________________________
> > > calligra-devel mailing list
> > > calligra-devel at kde.org
> > > https://mail.kde.org/mailman/listinfo/calligra-devel
> > 
> > Well accusation or not, I'd plead guilty. I don't care enough for missing
> > this feature to request a postponement. But yes that would have been the
> > right thing to do, and I apologize. As we both know It was late when the
> > fix was there and in the morning at 10 Cyrille was already at work. I
> > really had the best of intentions to pick up on it at that time, and as
> > you said would probably have protested louder had it it been one of the
> > things I had helped develop.
> > 
> > So I'm sorry
> 
> Ok, let's put this one down to experience then.  I must admit that the bug
> is pretty serious and has to be fixed.
> 
> The reason for my strong reaction is that I have put so much energy into
> this and also feelings so I was very disappointed when found out what had
> happened. In afterthought it's sad but probably not a disaster.  And as
> boud points out, disabling it now, fixing it for real and then release it
> after 2 weeks is going to show that we care about quality. The other way
> around is not good.
> 
And besides you get to fanfare about Author two times in a row ;
)