Add documentation for conventions/best practices for handling packages #78491
Unanswered
russellbanks
asked this question in
General
Replies: 3 comments
-
@denelon
Issue-Docs
|
Beta Was this translation helpful? Give feedback.
0 replies
-
I've converted this to a discussion so we can get multiple opinions. I would lean in the direction of what is best for the community long term. |
Beta Was this translation helpful? Give feedback.
0 replies
-
I think the answers here in terms of "What's best for the long term" are pretty straightforward. I'll post a condensed version of my thoughts here
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
There are often cases when different contributors have varying outlooks on how best packages' manifests and versions should be set up. Therefore, it makes sense to have documentation on conventions/best practices for handling packages.
For example:
exe
and anmsi
, do you provide both or just themsi
? (Answer: provide both - MSI or MSI & EXE? #68595 (comment))This list is not exhaustive and the "answers" I have described are mostly what I have learned myself from the opinions of moderators and from questions asked in discussions.
This should provide more clarity for contributors and provide more of a justification for PRs to be accepted/rejected based on whether they follow/don't follow the repositories' conventions.
Beta Was this translation helpful? Give feedback.
All reactions