Cleaning up issues #2741
Comments
|
👍 for @TheBB replacing me as assistant Issue Traffic Controller. |
|
So @trishume has designated his successor, congratulations @TheBB ! @trishume Thank you for all the help and contributions you provided during the first year of Spacemacs. Special thanks for being the first contributor to the project 👍 I hope one day I'll be able to replace Spacemacs with your own editor ;-) |
|
Thanks! I'll get to it momentarily. |
|
Yes, @TheBB you're on the clock now. Unfortunately, we can't provide much in the way of benefits. |
|
@TheBB We should ask those people with lots of open issues to go through the old ones and close any that aren't relevant any more (they should be able to do this quicker than you or anyone else). I can't figure out how to find out who has the most issues open easily, but at least the people who actively contribute should be able to do this quickly. Just quickly going through it to find who has the most: @tuhdo has 33 |
|
Yes, good idea. I'll have you know that 4 of mine are due to be closed upon release and there's a PR open for the fifth. 😉 |
|
found it... at the top of ones github page |
|
You can filter on author or click issues at the top of the page
|
|
Good idea. I've checked mine and was able to close some. For edge cases I pinged @TheBB and he can decide if they should be closed. |
Currently almost half the issues are still open. Many of them are labeled "fixed in develop" and will be closed on next release, but there are many others that in my opinion should be closed, not just bugs that are actually fixed but also questions and discussions that remain open long after they've been answered, discussed to death and/or abandoned.
I don't think this is ideal. It makes it difficult to get an overview.
I've looked through a few and found some candidates. I will update as I find more, and I invite everyone else with spare time to go treasure hunting.
For abandoned issues that we're not sure are fixed or not (the relevant code may have gone through heavy refactoring, or several versions of an upstream package have gone by since then, for example), it can be an option to close them with an invitation to reopen or re-report with fresh information if necessary.
Consider also whether it's worth to add a trusted collaborator or two with the go-ahead to do this for you, @syl20bnr. I know there's @trishume but he's
now one of THEMnot active at the moment.Company Mode RET Completion Can Be Annoying #102: See my commentad-handle-definition errors at startup #192: Maybe not a bug?How to add a dependency on xmpfilter not available in paradox? #354: Discussion has run its coursercirc-track-minor-mode not showing in modeline? #435: Should be fixed in developAdd support for installing unreleased packages #464: Should be fixed in developThe mode-line is empty #510: Unsupported version, old and probably fixed in developMini DSL to define powerline segment #524: Should be fixed in developMotion di( doesn't work when the cursor is on the paren #554: Fixed upstreamAbility to display current time in the modeline #624: Should be fixed in develophaskell layer overriding C-left & C-right #677: Outdated, no such thing as haskell-move-nested shows up with grepediff mode #695: Ediff is in Spacemacs nowMode line disappears when selecting until end of buffer #732: Should be fixed in developcompany mode in org-mode documents is extremely annoying #771: Discussion has run its course (and company is disabled in org now)evil-surround inserts literal escape character #814: Fixed upstreamDifferences from vim: Ctrl-L #826: Discussion has run its course (and problem is upstream)evil-tabs, android and java support #923: MPD: java layer is in, eyebrowse does tabsMove SLIME layer into Common Lisp layer #1002: Should be fixed in developCan't escape from isearch-mode normally as vim #1004: FixedNo option for global auto-complete #1043: Discussion has run its courseUpdating Packages Broken: auto-complete-mode void #1091: Probably fixedmagit-status-mode, evil-leader/set-key-for-mode, and evil-emacs-state #1101: Fixed (magit is evilified, not emacs state)desktop-save-mode #1112: Discussion has run its courseKey mapping #1113: Discussion has run its courseBind the default describe key to its default Emacs bindings #1117: Can't reproduce, fixed in the meantime?git-gutter working strangely #1119: Git-gutter has been removedclojure-mode not activated for 'build.boot' #1172: Fixed[Proposal] Add highlight-parentheses to Spacemacs core for Lisp modes #1173: Should be fixed in developGit addresses fail with http #1214: Fixed (no references to clone http in docs, no more submodules)scala is not loading #1228: No responseguide-key: Polling behavior kills kittens #1263: Should be fixed in developRemove current buffer from helm-projectile-switch-project #1275: Fixed upstreamDefault powerline theme breaks EMMS modeline #1311: Fixedphp-extras package only available from marmalade #1314: Should be fixed in developLayers are loaded in alphabetical order insted as defined in dotspacemacs-configuration-layers. #1321: Discussion has run its course[Wishlist] Don't take over emacs.d, deprecate layers #1351: Discussion has run its course (wontfix?)Replace defvar with setq in packages.el template #1358: Fixedsemantic layer causing python layer to die indevelop#1505: Git-gutter has been removedgit status conflicts with line num #1741: Git-gutter has been removedThe text was updated successfully, but these errors were encountered: