Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 2 of 2 for Heimes (0.16 sec)

  2. github.com/gradle/gradle

    architecture-standards/0001-use-architectural-decision-records.md 

    The main logic with ADRs is to describe (architectural) decisions made:

* To provide best practices and solutions we (as *build tool* team) want to promote.
* To avoid asking the same thing multiple times during code review.
* To explain *rejected solutions*, for now and future development, in case they are proposed again.

ADRs can be written by any team.
Like code, they should be reviewed by any other relevant teams.
    Plain Text
    - Registered: Wed Feb 14 11:36:15 GMT 2024
    - Last Modified: Wed Feb 07 00:43:19 GMT 2024
    - 2.8K bytes
    - Viewed (0)
  3. github.com/gradle/gradle

    architecture/standards/0001-use-architectural-decision-records.md 

    The main logic with ADRs is to describe (architectural) decisions made:

* To provide best practices and solutions we (as the *build tool* team) want to promote.
* To avoid asking the same thing multiple times during code review.
* To explain *rejected solutions*, for now, and future development, in case they are proposed again.

ADRs can be written by any team.
Like code, they should be reviewed by any other relevant teams.
    Plain Text
    - Registered: Wed Apr 24 11:36:11 GMT 2024
    - Last Modified: Sat Mar 02 21:54:40 GMT 2024
    - 2.8K bytes
    - Viewed (0)
Back to top