Skip to content
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.

Sign up for GitHub

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

Jump to bottom

NICEMAN -> ReproMan #359

Closed
2 of 5 tasks
yarikoptic opened this issue Jan 8, 2019 · 1 comment
Closed
2 of 5 tasks

NICEMAN -> ReproMan #359

yarikoptic opened this issue Jan 8, 2019 · 1 comment

Comments

@yarikoptic
Copy link
Member

yarikoptic commented Jan 8, 2019 •
edited
Loading

Time has come again for a rename. And we should do it asap. But I wondered if to simplify we should just merge all PRs which are in good state (not failing tests) first, even though they are WiP, and then proceed from there?

TODOs:

  • codebase renames (RF: NICEMAN -> ReproMan #362)
  • Add to README information about prior name
  • rename repo
  • rename pypi/debian packages
  • add instructions for config renames etc
@kyleam
Copy link
Contributor

kyleam commented Jan 8, 2019

I'll take care of rebasing #330 and #331 after the rename. I think #357 and #358 are good to be merged.

So that leaves deciding about #273.

@yarikoptic yarikoptic mentioned this issue Jan 8, 2019
Draft
8 tasks
@yarikoptic yarikoptic mentioned this issue Jan 17, 2019
Merged
@asmacdo asmacdo closed this as completed Feb 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@yarikoptic @asmacdo @kyleam