Plans for the next BleachBit

Also, yes I do release there is a watchlist on Launchpad that shows what's tagged for 1.12, but I think we should do my idea for the next update.

We can keep using Launchpad. It is very well organized and everything is where it needs to be.

I think new feature being added should be kept in major updates, such as 1.0, 2.0, 3.0, etc. That is how it is normally done.

Do I have the permissions to help manage the milestones on Launchpad?

I can't seem to edit the Milestones or Importance. I can only edit the Affects, Status, and Assigned To parts.

Ok, it is working now. I went ahead and switched some of them around and moved some from 1.12 to 20 and some from 2.0 to 1.12. I also changed some of the importances around, such as made some wishlists and such. I also made a few issues that have been open for a long time medium importances and some high, depending on how bad the bug was.

What do you think of the changes now?

Sure. I think when you subscribe to all it should send an email to notify you. I only organized a few and changed a few importances, as well. For future, I will put a comment, just incase, or inform you here, too.

Sure, go ahead and post the guidelines.

Hello Timofonic.

BleachBit actually does have a respo on GitHub already. Here is the link: https://github.com/az0/bleachbit

Fosshub is nice, but you are overlooking 1 thing about them. They are about anything that is free, not just open-source. I think a better alternative is Codeplex, since they focus on open-source only.

By the way Andrew, doesn't it say if I have changed the milestone of a bug when you look at the bug? When you do it, it shows that for me.

Also, I think we should remove some tickets that are no longer necessary, already been resolved, or have been closed already. For example, this ticket: https://bugs.launchpad.net/bleachbit/+bug/680552 That way we can shrink that list a little and make it easier to find a ticket when looking through the entire thing.

Also, I went ahead and commented on a few really old topics that haven't seen any activity in many years. What do you do with these? Do you want me to find more of them and leave a comment like "Old topic"?

Hey Andrew, do you have a steam account? If so, please add me and there are somethings I want to discuss further with you. Otherwise, come on Skype more often, lol.

Alright then I guess I will ask any questions here. I can't remember what I was going to ask, but if/when I do, I will ask them here.

Hey Andrew, would you mind if I opened a beta testing section of the forums. What I mean is there will be a section for beta testing where we can write our testing reports and report bugs during beta testing, and yes there sill will 1 issue per topic, just how you like it. I know we had a discussion be fore about this, but I think it would be more organized like this.

Would o like me to do it and show you what I mean. If you do not you can always destroy it. Would yo like me to do this on the new site to see if you like it?

Also, just letting you know, about a week ago I made a comment to this bug thread: https://bugs.launchpad.net/bleachbit/+bug/797995

Did you ever get a email notification for it?

Also, who is Roman Hornik? I notice he is subscribed to all bugs, is he someone who codes for BleachBit?

Also, have you been able to find a way to show milestones tagged next to each bug thread when you are viewing all the bugs?

What do you think about that? GitHub recently made some big changes to their website, so I am sure they are still recovering from the aftermath. I am sure eventually they will come around and not leave their users behind like that.

Maybe the milestone suggestion is something we could suggestion to the launchpad team to imply to their website? How would I do such a thing?

By the way, Andrew, if hosting cost of your new website gets too much, you can always move your project to Codeplex. It is free and it is almost like a combination of Sourceforge and Github.

Also, Andrew, have you found a way for me to sticky topics at all? I still am unable to do so.

Also, with the new testing forum topic, you can post your alpha builds there to get more early testers and feedback.

Yes, you are correct. We can now see the milestones when viewing all bugs. Maybe we can more easily go through some of those bug reports that do not have a milestone and see if they are still a good idea to BleachBit and remove the ones that aren't, you know to clean up the launchpad a bit.

Would you like me to do the clean-up? The only problem, though, is I would have no idea to determine which you still want to work on and which are no longer apply to BleachBit. If you want, I can move them all to, let's say, a empty milestone (like BleachBit 1.14) and from there I can move all the ones that don't have a milestone and you can go through them and decide what to do with them from there.

About the bug notification, I haven't been able to reproduce this. Are you still having this issue? Yesterday, I set one of the bug tickets to "Fix Released" on Launchpad as it was already included in BleachBit. Did you receive a notification for that or does it not notify you when statuses are changed?

Hey Andrew. I just noticed some bug threads that you had marked incomplete for a long time had never expired. This one for example: https://bugs.launchpad.net/bleachbit/+bug/786166 Any idea why it had never expired?

Also, are you having issues with Launchpad at all? It seems to be running really slow for me and if I open multiple tabs on Launchpad, it will severe instability and sometimes freezes my browser (but not my pc).

Now launchpad is running fine. Before it was running super slow, but they must have fixed it or updated their servers.

Currently, I am cleaning the launchpad a bit. IF you notice any bugs I have marked for incomplete that you wish to continue working on, feel free to change them.

Ah I figured out the issue why that one bug was not expiring. Apparently, you cannot have any milestone or assignee attached to it, otherwise it will not expire. Doesn't seem to matter if you have an importance, though.

Alright. I have finished going through all the unmarked reports on launchpad. There were only a few left a comment on because I wasn't for sure what to do with them. All other I either put a milestone on or marked them as incomplete for expiration.

You will probably have a lot of notifications in your email, assuming that they are working fine for you now.

Hey Andrew.

I noticed when you removed 1.14 milestone from launchpad, it moved all of 1.14 bugs to 2.0 and all previous 2.0 bugs to 2.2. Did you intend for this to happen? Because a lot of new feature/whishlist items were moved to 2.2, which I thought 2.0 would be a major update so all the wishlist items should be there?

It's a nice thought, however, lots of people still view major updates, like 1.0, 2.0, 3.0, etc, as major updates. Most of the major updating is in 2.2 now. That might confuse some people, as well, especially since you follow a 1.0, 1.2, 1.4, number scheme.

I understand that 1.10 vs 1.1 is confusing, so maybe avoiding those number schemes is a good idea.

Major updates always take a lot of time. If it isn't in 2.0, it will just be in another version. If you need more time, their is no rush. BleachBit is only a small time cleaning utility, so it doesn't need to update often. If BleachBit was something like Firefox or a full-time AV, then I would say releasing more often is a better approach.

Some feature requests I moved to 2.0 due to importance and demand from users. For example, support for cleaning multiple drives seems to have suggested quite a few times over the past years from users, especially ones wanting to clean non C: drives. I also moved stuff like "select all" option for cleaning entries, cleaning recycling bin user folders, adding a stop button, choosing number of hours for temp files, and support for specialdetect= for winapp2 seem to be relatively important and all have been suggested/reported more then 1 time by users. Of course, I understand that they all have been reported by users.

If it does get too much of a hassle, you can always spread them out into minor versions.

Frequent bug fixes are important, but major versions, like 2.0, should be more of a take your time type thing. The thumbnail cache is a issue in 1.12, yes, but it isn't a big issue. The thumbnail cache regenerates, so a temporary workaround is to just skip over that entry and it shouldn't be too much of a lose (since they regenerate). Of course, it should be fixed in 2.0, none the less.

This is my opinion of course, but a lot of the tickets for 2.2 should really be in 2.0 and 2.0 should be in 2.2. In my opinion, 2.0 should have most of wishlist/feature improvement tickets, as well as high reported bugs only. All other bugs should just be in minor updates (2.2, 2.4, etc).

Of course, I understand you are the only developer for BleachBit and do not get paid for this, so stuff like this is hard to keep up with. This is what I am use to with other software that follow your type of numbering scheme. If you chose to do things differently, then I will be alright with that, too.

So I just realized that I actually don't get any email notifications for the question section on launchpad, specifically here: https://answers.launchpad.net/bleachbit I don't see a way to subscribe either. Is there a way to do so on your end?

Also, I was thinking about cleaning that up a little, like deleting some of those answered/solved questions and some of thew really old ones, but it doesn't seem like I am able to do that either. Would you mind giving me the permissions to do so? Also, I can't edit statuses, either, for the question section.

Also, have you thought about using a static analysis tool for BleachBit. It might not solve most of the issues reported on launchpad, but it never hurts to use it every once in a while. The best one for Python I know of is Pylint here: https://github.com/PyCQA/pylint/

I still can't edit statuses.

Anyways, I don't see an actual way to close them. Is there a way to set answered/solved questions to expire overtime or auto-delete, like you did with the bug tickets?

No I don't. I see it for everywhere else, just not for status. Weird huh.