MITRE Defense Agile Acquisition Guide - Mar 2014
disciplines on how to appropriately and effectively implement Agile practices within current DoD policies. This guide draws on their insights to help program managers better understand Agile fundamentals current DoD acquisition environment. While acquisition executives emphasize the need to tailor policies and processes for greater effectiveness, few can do so successfully. This guide provides DoD acquisition Figure 1, this document fills the void at the intersection of Agile practices, DoD acquisition policies, and program office operations by digesting the extensive Agile strategies and acquisition processes0 码力 | 74 页 | 3.57 MB | 5 月前3Interesting Upcoming Features from Low Latency, Parallelism and Concurrency
optimization. ● Users are already using ranges with non-range parallel algorithms; integrating execution policies simplifies and streamlines code. The Power of Ranges and Parallelism ● The C++ Ranges library Introduction of bounded ranges for better parallel performance. ● ● Execution policies: Parallel range algorithms accept execution policies to control parallelism. ● Random access ranges: Algorithms require random-access abstraction that answers "where" the code should be executed. ● Limitations of current execution policies in specifying hardware execution contexts. C++17 parallel algorithms: A good start Current limitation:0 码力 | 56 页 | 514.85 KB | 5 月前3Template-Less Meta-Programming
Powered by TMP p.a; p.b; p.c; } ); 7 / 58[Examples] Performance / Policies [Examples] Performance / Policies constexpr std::array protocols{ std::pair{"ftp"sv, protocol::FTP}, std::pair{"file"sv protocol::WS}, std::pair{"wss"sv, protocol::WSS}, }; 8 / 58[Examples] Performance / Policies [Examples] Performance / Policies constexpr std::array protocols{ std::pair{"ftp"sv, protocol::FTP}, std::pair{"file"sv lookup(std::string_view) -> protocol; // Powered by TMP 8 / 58[Examples] Performance / Policies [Examples] Performance / Policies [1]: #uOps [2]: Latency [3]: RThroughput [4]: MayLoad [5]: MayStore [6]: HasSideEffects0 码力 | 130 页 | 5.79 MB | 5 月前3Django CMS 3.9.x Documentation
coding for django CMS in whichever way suits you. However, you need to be aware of the guidelines and policies for django CMS project development. Adhering to them will make much easier for the core developers efficiently and will increase the chances of making a successful pull request. Please see our Development policies for guidance on which branches to use, how to prepare pull requests and so on. Features To be accepted improvements, contributing code or documentation, and testing the Contributor Community Development policies How to contribute Code and project management Running and writing tests Code of Conduct Contributor0 码力 | 417 页 | 1.68 MB | 6 月前3Django CMS 3.8.x Documentation
coding for django CMS in whichever way suits you. However, you need to be aware of the guidelines and policies for django CMS project development. Adhering to them will make much easier for the core developers efficiently and will increase the chances of making a successful pull request. Please see our Development policies for guidance on which branches to use, how to prepare pull requests and so on. Features To be accepted contributing code or documentation, and testing the django CMS’s development community Development policies Contributing code Contributing documentation Contributing translations Code and project management0 码力 | 413 页 | 1.67 MB | 6 月前3Django CMS 4.0.x Documentation
coding for django CMS in whichever way suits you. However, you need to be aware of the guidelines and policies for django CMS project development. Adhering to them will make much easier for the core developers efficiently and will increase the chances of making a successful pull request. Please see our Development policies for guidance on which branches to use, how to prepare pull requests and so on. Features To be accepted Board Processes • Become a core contributor • Become a member of the Tech Committee Development policies Reporting security issues Attention: If you think you have discovered a security issue in our code0 码力 | 296 页 | 1.79 MB | 6 月前3Django CMS 3.9.x Documentation
coding for django CMS in whichever way suits you. However, you need to be aware of the guidelines and policies for django CMS project development. Adhering to them will make much easier for the core developers efficiently and will increase the chances of making a successful pull request. Please see our Development policies for guidance on which branches to use, how to prepare pull requests and so on. Features To be accepted Board Processes • Become a core contributor • Become a member of the Tech Committee Development policies Reporting security issues Attention: If you think you have discovered a security issue in our code0 码力 | 298 页 | 1.79 MB | 6 月前3Django CMS 3.11.10 Documentation
the frontend editor. This effectively barred projects from enforcing meaningful content security policies. In django CMS 5.0.0, we have removed all inline JavaScript from the edit mode (or other places to communicate with the frontend editor. This allows projects to enforce strict Content Security Policies (CSP) without any issues. For a fully working project, it is also important that other packages which could lead to an apphook without a slug Fixed numerous frontend issues Added contribution policies documentation Corrected an issue where someone could see and use the internal placeholder plugin0 码力 | 493 页 | 1.44 MB | 6 月前0.03The Most Important Design Guideline is Testability
must be removed •Deprecation Policies114 How can we test it? •Stopped using Power Peg in 2003, dead code still around •Dead code must be removed •Deprecation Policies •Code Review115 How can we •Stopped using Power Peg in 2003, dead code still around •Dead code must be removed •Deprecation Policies •Code Review •Static Analysis and Code Coverage116 How can we test it? •Remove old code and How can we test it? •Refactored code in 2005 ; moved dead code ; test still pass •Deprecation Policies •Code Review •Static Analysis and Code Coverage •Functionality Tests (unit tests or Knuth's torture0 码力 | 126 页 | 9.11 MB | 5 月前3Django CMS 4.1.x Documentation
which could lead to an apphook without a slug Fixed numerous frontend issues Added contribution policies documentation Corrected an issue where someone could see and use the internal placeholder plugin support is provided as an interim measure only. In accordance with the Django Project’s security policies [https://docs.djangoproject.com/en/dev/internals/security/], 1.6 no longer receives security updates contributing code or documentation, and testing the Contribute to django CMS How to contribute Development policies Guidelines for django CMS projects Code and project management Running and writing tests Code of0 码力 | 518 页 | 1.66 MB | 6 月前3
共 39 条
- 1
- 2
- 3
- 4