Change strings and docs to Lix in the code where that is correct #148

Closed
opened 2024-03-18 22:17:32 +00:00 by jade · 6 comments
Owner
No description provided.
jade added this to the v2.90 milestone 2024-03-18 22:17:32 +00:00
jade added the
release-blocker
label 2024-03-18 22:17:32 +00:00
jade added this to the Release engineering project 2024-03-18 22:17:32 +00:00
raito self-assigned this 2024-03-19 01:18:26 +00:00
Author
Owner

I have a CL happening that i seem to have ... misplaced? that changes it inside the codebase.

I have a CL happening that i seem to have ... misplaced? that changes it inside the codebase.
Author
Owner

Docs still important but we might want to go after backports of docs prs first.

Docs still important but we might want to go after backports of docs prs first.
Owner

@jade Should we over-replace here, e.g. replace systematically in documentation any allusion or keep some concepts like "Nix store" instead of "Lix store", etc. ?

I feel like we should keep comment code / classes names / variable names to use Nix until we rewrite the code, right?

@jade Should we over-replace here, e.g. replace systematically in documentation any allusion or keep some concepts like "Nix store" instead of "Lix store", etc. ? I feel like we should keep comment code / classes names / variable names to use Nix until we rewrite the code, right?
Author
Owner

https://gerrit.lix.systems/c/lix/+/576 I have un-misplaced my CL.

https://gerrit.lix.systems/c/lix/+/576 I have un-misplaced my CL.
Author
Owner

@jade Should we over-replace here, e.g. replace systematically in documentation any allusion or keep some concepts like "Nix store" instead of "Lix store", etc. ?

I feel like we should keep comment code / classes names / variable names to use Nix until we rewrite the code, right?

I meant to put this in a document somewhere.

I think that style guide wise, it should still be Nix store, because it is referring to the technology. But the implementation is Lix.

> @jade Should we over-replace here, e.g. replace systematically in documentation any allusion or keep some concepts like "Nix store" instead of "Lix store", etc. ? > > I feel like we should keep comment code / classes names / variable names to use Nix until we rewrite the code, right? I meant to put this in a document somewhere. I think that style guide wise, it should still be Nix store, because it is referring to the technology. But the implementation is Lix.
ktemkin modified the project from Release engineering to Soft Launch 2024-04-27 01:16:17 +00:00
lunaphied changed title from Change strings and docs to Lix where that is correct to Change strings and docs to Lix in the code where that is correct 2024-04-28 23:58:03 +00:00
qyriad was assigned by ktemkin 2024-05-02 04:21:36 +00:00
ktemkin modified the project from Soft Launch to Release engineering 2024-05-05 17:36:42 +00:00
Owner
Will be fixed in https://gerrit.lix.systems/c/lix/+/1112.
Sign in to join this conversation.
No milestone
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: lix-project/lix#148
No description provided.