Please make new release

[kloczek]

I think that it would be good to flush currently committed changes and make new release :)

[davetapley]

bump @robdennis @jhermann

[robdennis]

Hi, I confess I don’t actually remember _how_ to make a release these days since I’ve taken a step back from open source development. Does @jhermann or the other maintainers feel like they have the right creds/access?

…

On Tue, Nov 16, 2021 at 5:30 PM Dave Tapley ***@***.***> wrote: *bump* @robdennis <https://github.com/robdennis> @jhermann <https://github.com/jhermann> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#213 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAC4YQWEIAMSULTHWUTGLMTUMLLPFANCNFSM5EGDKZ2Q> . 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>.

[sheromon]

I'm not sure how helpful I'd be, but I'm interested in this. I've been using configobj for... years now (?), and it's been very helpful to me.

[dvzrv]

More than a year has passed since this issue has been raised and more than two years have passed since the last commit to this repository has been merged. Given the amount of issues and open PRs I guess it is safe to assume, that configobj is abandonware at this point.

@robdennis @jhermann have you tried reaching out to people for trying to find a more active maintainer for this project? Maybe someone is up for it :)

[anoduck]

(I apologize for the customary "dude!" in this statement)

but...

Dude!
I have finally taken the leap into learning python and have incorporated configobj into all of my "serious" projects. It beats the socks off of configparser. I came here for clarification over the class "Validator", and saw this issue. As previous said, it is the best for configuration parsing IMHO, it needs another release.

Do we need to raise funds or have a candlelight vigil or something?

I will second @sheromon if there needs to be a vote or something. 😃

[robdennis]

Hi folks.

In a bit of good news, I'm now working with code that depends on configobj, so supporting went from "find time at home" to something I can spend some time on during the workday.

That being said, I think the project would benefit from someone able to be more responsive to issues being opened, and is more familiar with what an open source project looks like in 2022.

I'll attempt to reach out to @sheromon and see if they're still willing to take on maintenance.

As of now, I think the release process involves manually uploading a distributable to pypi, and so I'd need to give permissions there as well.

Thanks for everyone who still gets value out of this and wants it to stay around. :)

[robdennis]

I reached out to the hachyderm.io / mastodon account referenced in the user page. Fingers crossed.

[sheromon]

@robdennis Thanks for reaching out! I have been under a rock in a cave (actually my apartment), coughing and blowing my nose and trying many cold medicines over the past couple weeks, but things are getting better lately. I am probably not the maintainer you are looking for, since I don't have much experience, and I don't know how responsive I'd be. I'm happy to attempt to help, though. We can figure out if that even makes sense in another forum, though. I'll shoot you an email as well.

[anoduck]

@sheromon Hope you feel better, Cheryl.

[sheromon]

@anoduck Aw, thanks!

[robdennis]

After speaking with @sheromon here / over email, I think the next step would be for me (a few hours a week, for a few weeks) to put together a release that:

• fixes any identified bugs
• validates that everything works against new python versions since the last release.

And hopefully that's good enough until someone else wants to fork/take this one on.

If anyone wants to take stewardship of the project after that but maybe doesn't feel, then they could volunteer to go through that process with me, and I can at least teach someone how we were doing it back in 2014.

If there's a strong opinion-haver who knows how things are supposed in 2022 and feels like then they can just own this repo without input from me / @EliAndrewC , that's okay too. Just reach out and we can set up permissions.

[sheromon]

@robdennis Sounds like a good plan and totally reasonable. I have a flexible schedule and nothing on my calendar other than some work meetings, so feel free to reach out here, over gmail, or whatever chat thing Google currently has if you'd like to pair up for a particular task or want to just break off a task for someone else.

[anoduck]

Back in business...

[robdennis]

I think that it would be good to flush currently committed changes and make new release :)

There's ~110 commits since the last release, including a fair number of changes to the tooling/infrastructure needed to get a development environment.

After ~3 days worth of scoping / trying to get a checkout / getting my arms around the problem, here's where I'm at:

• Because of the changes to the tooling (and associated issues described in the bootstrap readme / utilities described in the readme not working on Ubuntu 20.04 #222), I don't feel like I can "just flush the currently committed changes"
  • A release of what's on master is essentially going to require someone to update the 2018-era tooling that was put in place and ensure it'll work going forward (or do "something else" that I don't have a good handle on)
• what I can do is make something, based on 5.0.6 / the release branch, that attempts to confirm that it's still working with newer versions of python (previous 3.3 was the last tested release)
  • this is described in Plan for 5.0.7 release #223 and would represent a "5.0.7" release
• this is unfortunately a smaller-scope than what this ticket is asking for, but it's what I am capable of doing within the amount of time my job is letting me take this on and my ability to ingest the last 8+ years of progress

[robdennis]

5.0.7 is released out onto pypi. I am committing to fixing any errors that are associated with that release. After that point I think the README.md in the default branch (now release instead of master) does correctly state that this project is not being actively maintained.

[kloczek]

I don;t see git 5.0.7 git tag in https://github.com/DiffSK/configobj/tags
Is it possible to tag that version in git repo? 🤔

[robdennis]

You’re right I didn’t tag / push the tag. Will correct that asap

…

On Wed, Jan 18, 2023 at 4:07 PM Tomasz Kłoczko ***@***.***> wrote: I don;t see git 5.0.7 git tag in https://github.com/DiffSK/configobj/tags Is it possible to tag that version in git repo? 🤔 — Reply to this email directly, view it on GitHub <#213 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAC4YQQRZH74HACWI3VWWRDWTBLPLANCNFSM5EGDKZ2Q> . You are receiving this because you modified the open/close state.Message ID: ***@***.***>

[kloczek]

Thank you 👍
SImple for me tags are important because I'm using autogenerated tar balls from git tags as input resources to build my packages 😋

[kloczek]

If may I ask next time to do one more thing 😋
Could you please make next time release to have appeared tag on https://github.com/DiffSK/configobj/releases?
In this case my automation uses that as async signal delivered over SMTP ro try automatically build package 😄
Github automation only takes releases to generate email notyfications ..

[kloczek]

Just tested 5.0.8 and looks like content of the src/validate/ is installed.
Is that intentional? 🤔

[anoduck]

I am so happy this beautiful library is back. 😃