Because Ivan Yossi is currently too buzy to write up the Last Week In Krita segments, I set up this Etherpad so we can sort of crowd-source this job, and it may easily be chucked onto Krita.org by boudewijn or irina.

https://notes.kde.org/p/Last_Week_in_Krita

You need a KDE account to see and change it, but that should not be a problem if you are involved enough in development to make changes.

@TheraHedwig - thanks for posting that. Looking at the document, it looks like we can probably post the November 3-9 results. There was a post on Krita.org October 23 that outlined previous changes, so we probably don't need to go farther back than that.

Well, not necessarily everything needs to be documented, but we can give it a proper try.

As well, make sure to check back every few times to make sure names are spelled right, I am terrible at that

Anyway, it's up: https://krita.org/item/last-week-in-krita-week-45-3/

wow, looks like everyone has been busy! Thanks for posting that.

Hi there, just wondering. Its just bugfixing at the moment right? is it really possible to get 242 bugs fixed within a month? (I saw the release was supposed to be end of the month) It is my understanding that Krita has limited developers (fulltime).

How many more testbuilds would there be before official release?

Would it not be better just wait for layer styles to be implemented before official release? That we have an official release with all the kickstarter stuff AND a stable version to use, instead of getting a stable version, and then have a major feature added in a testbuild? I wouldn't mind waiting a bit longer, but I can only speak for myself.

Thanks, and Happy NewYear.

Well, it's because we have limited manpower -- right now, 2 full-time developers and a bunch of awesome part-time volunteers that we need to focus on fixing bugs for the release, instead of adding features! We won't fix all bugs, and in fact, some of those bugs have been around for quite a long time, which is kind of the nature of software development. We know that some parts of Krita really need a redesign. like the text tool, so we're not going to focus on those issues. My goal right now is to make custom shortcuts work reliably, that's the main thing for me: next is make sure that we don't have unfortunate fall-out from the multi-image work, then performance regressions...

Yes, that all makes sense.

Thanks for answering!

sorry for double-post..

Will the news section on krita.org have a comments section installed? I think the old site had one, but I can't remember.

No, because it's too much effort to moderate :/

Old site didn't have comments either.

So what is hoped to be done before and during Beta 3 release?

Do you guys have a system for how many bugs need to be cleared before official release?. I'm aware that obviously most crash bugs need be done, but in terms of normal bugs, how do you guys decide when its fine to push forward with the release?

It's an art, not a science Excluding Sketch and Gemini, we have 147 open bugs. That sounds like a lot, but it's not that bad, actually...

We have one critical, must-fix bug, with loading fill layers (https://bugs.kde.org/show_bug.cgi?id=343807).

There are seven open bugs set to 'crash'. However, they either happen under very obscure conditions (if you have a vector line and add an arrow head to it, then Krita crashes on closing if you didn't save your document, for instance: https://bugs.kde.org/show_bug.cgi?id=343719)

The resource manager is still a worry: Smjert is on the case, though, and he has the right ideas, so that might get fixed in time.

G'Mic continues to provoke crashes and other bugs, but there's little we can do about that. It's the danger of using research software, so people will have to be careful.

There are some bugs with the PSD file format that I'd like to solve, but that can wait for a .1 release or even later.

There are quite a few usability bugs with the transform tool -- I'd like Dmitry to look at those, and he does.

None of the remaining bugs are really showstoppers. -- there are parts of the ui that need more polish, tablets that need better support, weird interactions with drivers, desktop environments or other applications, some timing issues that lead to e.g. the history docker showing the wrong thumbnails.

In short, while would ask every Krita hacker to take some bugs and kill them, we're in an okay shape for the release. I've even started bringing back sketch and gemini, and might succeed there.

haha excuse my ignorance. Thanks for the update boudewjin. G'mic is doing a lot better from here, I don't get crashes, but a few error messages. The last beta announcement said there where 222 bugs, thats been knocked down quite a bit.

So congrats! and again thanks for detailed response.

Yes... I seem to have closed 174 bugs in the past 31 days, and Dmitry 25. But the bugs Dmitry works on are a lot harder, and I did a lot of triaging as well. It means Dmitry fixed a serious bug a day...

The problem with being a Beta tester is that the release day isn't as fun.

Aw, have you read all the release notes yet?