Homebrew
Upgrade Mercurial to 6.2 #3445
-
|
It seems that completion file path issues must be fixed for Mercurial to be upgraded to 6.2 (see Homebrew/homebrew-core#105540 (comment)). I don't know the details of Homebrew's or Mercurial's handling of completions. The existing PR is closed. Where should work on this issue be tracked? The New Issue form indicates that issues can be opened for bugs. It doesn't mention opening an issue for upgrading to a new version, so I'm not sure if a new issue will get closed or will be left open. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 5 replies
-
|
Work on version bumps is typically tracked in a PR. Issues usually are a very poor way of tracking them, so I don't think we'd keep one of those open. |
Beta Was this translation helpful? Give feedback.
-
|
The PR was closed as stale, so the work isn't being tracked anywhere. |
Beta Was this translation helpful? Give feedback.
-
|
It's still accessible, can be commented on, and shows the complete state of work done. A new PR can be opened if and when additional work is done. |
Beta Was this translation helpful? Give feedback.
-
|
Does it show up anywhere as something that needs work? So homebrew maintainers looking to work on things know that it is still needs work? I'd fix it, but I don't know anything about home-brew completion script handling, don't program in python, etc. |
Beta Was this translation helpful? Give feedback.
-
It shows up in your post here and for users of |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
It shows up in your post here and for users of
brew livecheck. The aforementioned users include maintainers and contributors who regularly update formulae in homebrew-core.