Update channels early draft #225
Conversation
@electronwill please review and edit.
|
|
||
| At [https://**pypi**.anaconda.org/conda](https://pypi.anaconda.org/conda) a channel | ||
| dropdown lists all the available channels in this user namespace. | ||
| Each file within a package may be tagged with one or more labels, or not tagged at all. |
There was a problem hiding this comment.
Keep in mind that if it is not tagged, you can not download it.
There was a problem hiding this comment.
Sean, do you mean that main is no longer the default, it must actually be labeled explicitly?
Correct additional uses of `label` and `channel`
| dropdown lists all the available channels in this user namespace. | ||
| Each file within a package may be tagged with one or more labels, or not tagged at all. | ||
| Labels are commonly used to divide a package's files into sections labeled development, | ||
| testing (and/or other custom labels), and main or dev, test, main or other custom label. |
There was a problem hiding this comment.
This sentence is pretty confusing. I can't tell what it is trying to convey - is it telling me to use the names dev, test, and main for my labels? I think we could remove it without much harm.
There was a problem hiding this comment.
Perhaps we could say:
Each file within a package may be tagged with one or more labels, or not tagged at all.
A package's files can be sorted into categories such as development, testing, and main with labels such as "dev" "test" and "main". Then developers can set their machines to install all updates, testers can set their machines to install only "test" and "main" updates, and other users can set their machines to install only "main" updates. Any other custom labels can be used instead so that the label system can fit any workflow.
|
@dsludwig please make it so. |
Remove confusing sentence.
@electronwill please review and edit. Please do NOT merge yet.