sdzhepa / sandbox_ec Goto Github PK

"Progress: done"

Due to the rules and requirements of this public repository:

We are able to process, collaborate, fix, and deliver pull requests ONLY for Issues that can be reproduced on the latest 2.4-develop public branch.

Proof links:

• Code Contributions: Accepted pull requests and ported code
  Quote

  
  v2.4 Contribution Notice: Magento is focusing development efforts on v2.4, so we are no longer accepting pull requests to the v2.3, v2.2, v2.1, and v2.0 release lines.

• GitHub Issues Processing Workflow: Verification
  Quote

  
  Be advised, we only accept pull requests for 2.4-develop.
  Check if the issue exists on the 2.4-develop branch with a clean installation, configured by described preconditions, following the exact reproduction steps.
  -- If the described behavior was reproduced, the maintainer should apply the Reproduced on 2.4 label to the ticket, indicating that issue was reproduced and specific version.
  -- If the issue was not reproducible with 2.4-develop, the maintainer should close the issue and stop verification process here!

• Issue reporting guidelines this link exists in each new issue report template
  Quote

  
  Checks if the issue exists on the 2.4-develop branch with clean Magento installation. Be advised, we only accept pull requests for 2.4-develop. If the issue is not reproducible on 2.4-develop, it will be closed.

Branch 2.3-develop was removed from the public repository. All fixes to the previous release allowed and can be done ONLY by the Magento team. Based on the prioritized backlog by the Product Management team.
All issue related to the previous Magento versions can be reported only through:

• support channel associated with you magento.com account
• participation in Magento Beta Program

Proposer text/collor/description for labels

TODO

• review and prove final text/description with Guild
• update related documentation on DevDoc. e.g
  • "Genera"l section of https://devdocs.magento.com/contributor-guide/contributing.html#labels
• A blog post is published promoting collaboration around these labels.
• ??? announce and promote labels in slack channels (description, purpose,use cases examples, and main idea)

Questions to discuss and clarify

1. Need to discuss and be clear on Adobe/Magento involvement to participate in monitoring and processing ticket with such labels. Comment: As i know now we do not have a capacity for regular work on it. In other words, now label "help wanted" exist but Adobe/Magento does not have any regular process to process/assist with it
2. Are we going to use it in bitergia Top Contributors Leaderboard? If yes need to define the calculation rules etc. e.g. how are we going to track all user-names if several persons joined for collaboration?
3. Any additional rules for bots to set or remove these labels automatically or in other exceptional situations? examples

• in case if reopen
• in case if already resolved and help or collaboration does not need any more
• in case someone joined and labeled with collaboration and leave and help still needed

https://github.com/apps/stale

Cases to test

1. Issue receives assigned person(will it be closed as stale or not)
2. Issue was linked to PR
3. issue was just commented
4. issue was only labeled
5. Issue has related PR, no activities in issue, but there are activities in PR(new commits etc)
6. Issue is not marked stale is it has a specific label

test

"Progress: dev in progress" should not be deleted

"Progress: done" closed

sdfsdf
👍 +1