New release?

[ConiKost]

Are there any plans for a new release?

[haraldg]

I hope to have things cleaned up enough for a release by the end of (northern hemisphere) summer.

Also this probably will be the last release done by me. If anybody considers picking up the work: Now is a good time to get involved.

[ethandicks]

I am happy to pick this up going forward.

[haraldg]

I am happy to pick this up going forward.

Great! Then let's work on the upcoming release together!

[ethandicks]

Happy to learn the ropes.

[haraldg]

As far as I'm concerned, we are ready to start the release process. There are many things, that I would like to see fixed in the upcoming release, but it just won't happen from my side in any reasonable time frame. Better to go with what we have, I think.

@ethandicks would you like to create the release branch yourself? (At least this time I'm around for any questions. :-) )
A checklist/guide for preparing a release (candidate) is in:
https://github.com/lcdproc/lcdproc/blob/master/docs/release-checklist.md

[ethandicks]

I will review the process and see about kicking it off

[haraldg]

Any progress on this front? Do you need help with anything?

[ConiKost]

Seems one year passed without any activity..

[ethandicks]

I could probably use some handholding to get started. Some personal disasters a year ago (Dec and Jan) including no electricity for weeks totally derailed my work. Would love to get back on track.

…

-ethan

On Fri, Jan 21, 2022, 15:58 Harald Geyer ***@***.***> wrote: Any progress on this front? Do you need help with anything? — Reply to this email directly, view it on GitHub <#160 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAINHYX3M6GU7URIMZJDW63UXHCHVANCNFSM4QD7BIJA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[ConiKost]

Sorry to hear! Hope you will get well :-)
If you need some help, maybe I can help?

[haraldg]

@ethandicks sorry to hear about your misfortune last year. I hope 2023 is better to you!

The way I did the releases is documented in https://github.com/lcdproc/lcdproc/blob/master/docs/release-checklist.md but that is not set in stone. Mostly it is just about updating all the version and date strings.

Usually I first announced a release candidate on the mailing list before making the release official. We don't have the mailing list anymore, so not sure, how you will do that. Maybe just drop the release candidates or maybe announce them to the known package maintainers to get some feedback. It shouldn't matter all that much anymore: I guess, a strict release procedure was more important when we were using CVS. Nowadays we can move change sets between branches quite easily.

@ConiKost I think more hands to help with lcdproc are always welcome. I don't think release management is particularly difficult, but you would need to get git write access. (I don't have the privileges to grant this to you, I believe.) I'm not sure, what the rules for write access are. You are quite well established on github but not so much with lcdproc. Maybe the admins would want to see some more PRs from you first?

Also testing the release tar ball on all platforms you care about, would be very helpful. (See the discussion about release candidates above.)

[ConiKost]

Maybe the admins would want to see some more PRs from you first?

That's fine. My intention wasn't to get write access to Repo but more to help by filling PRs :-) I will see, what I can do for PRs for the release-checklist.md.

[ethandicks]

Reviewing issues here, I plan to kick off a new release in approximately 30 days. This will give me time to prepare for regression testing the drivers I usually test (largely Matrix Orbital, Crystalfontz, and jw002) and to give time to review any pull requests that should be in this release.