On Thursday 27 of August 2009 21:50:44 Aaron J. Seigo wrote:
> they were in 4.3.0. they aren't blockers then, they aren't blockers now.
> it's more important to get fixes that -have- been made and do timely
> releases than wait for fixes that have yet to be made.
Well, both bugs were reported a
On Thursday 27 August 2009, Maciej Mrozowski wrote:
> There are a few bugs apparently still present in 4.3 branch, do you think
> they are worth being blockers?
they were in 4.3.0. they aren't blockers then, they aren't blockers now. it's
more important to get fixes that -have- been made and do t
On Thursday 27 August 2009 20:41:17 Maciej Mrozowski wrote:
>
> (apart from that, one minor issue with Notes plasmoid not being able to
> revert font color to 'Use theme color')
>
I looked at the code and it's a //TODO so it's not been implemented. I hardly
call that a blocker anyway. Can you i
About KDE 4.3.1 tagging.
There are a few bugs apparently still present in 4.3 branch, do you think they
are worth being blockers?
https://bugs.kde.org/show_bug.cgi?id=202722
https://bugs.kde.org/show_bug.cgi?id=204605
Also there is some kdevelop crash that may have its origins in kdelibs
https:
Am Donnerstag 27 August 2009 10:12:22 schrieb Tom Albers:
> No, the normal packaging to release cycle is ~5 days. Only if we apply that
> normal cycle to rc's the rc's would not get any useful testing, as their
> interval is set to two weeks. So the RC's follow a package-and-release
> cycle, with m
At Thursday 27 August 2009 01:00, you wrote:
> Am Mittwoch 26 August 2009 22:23:33 schrieb Tom Albers:
> > This schedule will become final next saterday, unless someone objects.
>
> What is the reason for having about one week between tagging and release of
> the beta versions but only one day fo