This is a high-level tracking issue for the tasks that should be accomplished prior to transferring or forking the repository to git-bug/git-bug. Note that this is a planning issue -- this relocation may not be done for several months.

• CI/CD improvements
  • Get all pipelines passing #1189
  • #1198
• #1204
• Work through dependabot module PRs
• #1209
  • Specifically, command-related documentation is out of date
  • CLI completion needs to be updated
• #1212
• #1214
  • Label all PRs appropriately
  • PRs that fix bugs should be included in the next release
  • PRs that add features should be planned for a future release
• #1215
  • Label all issues appropriately
• Release 0.8.1
• #1219

sudoforge changed the title from Maintenance revitalization to Maintenance revitalization 2 years ago

sudoforge added label triage/accepted 2 years ago

Hi, @sudoforge . Did version v0.8.1 ever get released somewhere?

The latest I see in GitHub Releases is v0.8.0 from 2022.

Since then there have been a lot of commits, so I'm assuming that the best way to get a working version now is to install from the source.

Is there an easier way?

Hey @sudoforge, thanks for all your work on this! It seems like life might've gotten a bit hectic. Would you be opposed to my initiating another issue to initiate a "Call for co-maintainers" process on your behalf?

Here's an example of how a previous one panned out: https://github.com/slack-go/slack/issues/207

@iainelder sorry for the late reply - you are correct, installing from source should be the preferred way to go for the time being.

@patcon active contributors are always appreciated - life does indeed make it difficult to maintain open-source projects sometimes.

this past weekend, i actually began working on catching up on a backlog of things that need to be addressed with git-bug, and we should see a release soon (sooner than half-life 3, at least).

thanks for the quick reply -- If I understand correctly, I'll leave the work to those already active, and not try to activate any reinforcements 🙏 (I get that not everyone wants to manage that vibe of distributing responsibility too much)

I have updated the release date for 0.8.1 to 2025/04/27.

sudoforge added label priority/important-soon 11 months ago

sudoforge added label lifecycle/active 11 months ago

heads up: i've pushed the expected release date for 0.8.1 back a week because i have family visiting and will be unable to close out the remaining milestone issues until the following week. the expected release date is now May 3 2025.

i've removed this issue from the milestone because it's really just an epic / group of other issues.

sudoforge removed label lifecycle/active 10 months ago

With the release of v0.8.1, this issue's tasks have now been completed and it can be closed.

sudoforge closed the bug 10 months ago