release 3.0.3

[lynxis]

The last release (3.0.2) is missing b3dc385 It would be great to do the 3.0.3 release with this fix so distributions can pick it up.

[GeraldJansen]

Under PR #656 the NEWS.md file shows that this is already included in the upcoming 3.0.3. I don't know what we can do to encourage @matthijskooijman to proceed with the release (beg, pray, cheer, ...). Only #663 was pending but it seems ready to go.

[matthijskooijman]

I don't know what we can do to encourage @matthijskooijman to proceed with the release

I'm not sure if I'm the only one who can do that, but doing the release is on my mind, I just haven't found the time yet (I'm buried in deadlines atm, which should be better in a week or two, but I'm not yet sure in what order my backlog will be processing once it does...). In any case, I haven't forgotten :-)

[lynxis]

I friendly reminder and ping for the next release.

[lynxis]

I friendly reminder and ping for the next release. @matthijskooijman

[rabin-io]

Can you please tag an release 3.0.3 ?

[ederag]

A breaking change such as #663 should not delay patch releases.

[steviehs]

I really would like to support a new release, meanwhile I had to manually apply b3dc385 as this was an annoying one :-)

[petrovo-as]

Does anyone else maintain and develop this project? I use the program every day. Thanks for the reply.

[matthijskooijman]

I'm still here :-)

When the previous maintainer resigned, four people volunteered to keep the project maintained, but then already with some reservations on available time. Of these, @mwilck, @DirkHoffmann and myself remain, but it seems available time and/or other responsibilities are getting in the way for all of us, meaning hamster is not moving much.

Having said that - I still use it myself daily and hamster development is still on my mind - I really hope to put some time in this again in the near future.

[GeraldJansen]

@aquaherd actually made the last merge, yay :-)
Any progress is much appreciated!

[petrovo-as]

Thank you for the quick reply. I just saw that no version was released in the last year. I've been looking for a time tracker for a long time and Hamster is amazing and simple. So I will send one more small problem that bothers me. :-)

[DirkHoffmann]

I never committed to doing release stuff (and previous validation, testing etc.). But if it helps, why not learn something new on github?
I may need some guidance though, @matthijskooijman.
(@GeraldJansen, I thought you had permissions to tag/release also. Am I wrong?)

I see there is a branch release-3.0.3, which diverged (2 commits ahead of master, 5 commits behind right now, but "only" release notes). Wouldn't it be appropriate to merge that first into master, @matthijskooijman?

[aquaherd]

I seem to have accidentally inherited merge rights, yes, but as your humble xfce4-hamster-plugin developer I do not know the hamster codebase good enough to even remotely assess what to merge and what not. Imagine I bring only rudimentary 2.7-ish python skills to the table.

If there was an established consent on what is to merge and what not, I would volunteer to merge even more and easily provide a tag once or twice a year.

[matthijskooijman]

@DirkHoffmann Cool! If you're going to push this forward, hopefully that will motivate me to invest a bit of time in this as well.

I see there is a branch release-3.0.3, which diverged (2 commits ahead of master, 5 commits behind right now, but "only" release notes). Wouldn't it be appropriate to merge that first into master, @matthijskooijman?

I would think it is better to just rebase that branch, maybe squash the commits in it together as well (and update it to include whatever new commits are in master now in the changelog). I created that branch mostly as a place to store a bit of release engineering work for later, I do not think the specific history of that branch is relevent and needs to be merged rather than rebased.

Furthermore, we should see if there are any other PRs ready to be merged (or important enough to be fixed and merged), but we should also probably be very conservative (i.e. not get caught up in fixing this and then ending up not releasing). I recall there were a few things I wanted to tackle, but frankly none of them is probably important enough to hold up the release.

One thing we should probably fix is #710, which I think prevents hamster from working at all on Python 3.11. I see there are (since just now) two PRs to fix this, but let's continue discussion about that in those PRs and the issue.