-
Notifications
You must be signed in to change notification settings - Fork 162
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
please delete the deform2
branch
#279
Comments
I deleted all the stale branches with '| 0' showing just now. |
fastest. response. ever. ;) |
ugh.. it seems that PR's related to the dead branch were also killed. Sorry, I didn't see that there were PR's attached to that branch. I guess those people could update their PR and resubmit. |
So there were three PRs submitted by myself (#184, #185, #187) which were just closed. I'm happy to put some work into them to rebase to current master and clean out any code rot, but... these pull requests have been sitting around feeling neglected for nearly two years now. If I do clean them up, what's the chance that it will lead somewhere? |
@dairiki as of today, here's the latest discussion on the matter, starting from this message. tl;dr: There is currently no active maintainer of deform, and finding a qualified maintainer is hard. |
@dairiki I am now an active maintainer of Deform on both PyPI and GitHub. Sorry it took so long. I would like to get your PRs #185 and #187 into Deform 3.0 (#184 made it in via #280). Would you please create a PR against the Lots of work has already taken place on deformdemo. In Deform I'm starting triage of open PRs now, and issues later this week. Thank you! |
The current
master
branch is the lastest version of deform which is 2.0. However, there's also a dead branch calleddeform2
which is currently 138 commits behind the master with nothing not already ready in the master branch. This is a source of confusion.In general, it'd also be nice to simply delete all the stale branches that have already been merged into the
master
and are no longer valid, butdeform2
seems to be the largest source of confusion.The text was updated successfully, but these errors were encountered: