Remove env_logger from this repository #145
Labels
No labels
bug
duplicate
easy
enhancement
help wanted
invalid
question
rfc
structured-logging
wontfix
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
gh-rust-lang/log#145
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Let's find a suitable maintainer and move it out of the
logrepository itself. While still a high quality logger that we'd likely want to recommend, it may benefit from spreading out the maintenance burden! Tons of possible features were mentioned forenv_loggeron the evaluation thread and may wish to make their way to the new repository.EDIT
PRs that need to be resubmitted to the new repo:
Hey @alexcrichton, I've started to work on this split at sebasmagri/env_logger.
I'll review the features mentioned in the evaluation thread and check out the API guidelines for the new repo.
For now, I'm pointing it to
log's git repo since there where some breaking changes in its enums. What would be the plan inlog's side to make a stable dep forenv_logger?@alexcrichton @sfackler by @brson suggestion, I've added you guys as collaborators in the new repo.
Is there any particular improvement that should be done for it?
Thanks @sebasmagri!
How do you want to handle outstanding PRs?
@jethrogb ideally the changes should be resubmitted to the new repo... Can you please point me to those?
Seems like we need to make some decisions about this - are we going to do a handover here, and how?
If we're confident doing it then it seems like we should maybe land the outstanding PRs, remove env_logger from this repo, and maybe reimport that state into @sebasmagri's.
cc @sfackler @alexcrichton
For the record, the open PRs that touch
env_loggerare #203 (though this is already open in the new repo as well), #196 which is just about adding a noopflushmethod to env_logger'sLogger, and #113 which is not yet defined as per @dtolnay's feedback.There has no been further changes to
env_loggersince I transplanted it.I would love to give env-logger over to a motivated maintainer.
#200 has also made a small change to env_logger in this repo and #196 has now been merged. I've made both changes to the forked env_logger here: sebasmagri/env_logger#15.
@sebasmagri have you logged into crates.io yet? I tried adding you as an owner but it said you weren't registered :(
@alexcrichton I hadn't, you should be able to find me now.
@sebasmagri ok you're added as an owner, as soon as everything's sorted away I think we can just have a PR to remove it from this repo.
I'll leave this open until we've got the current set of PRs against
env_loggerported over (updated OP).