Changes between Version 2 and Version 3 of ucore
- Timestamp:
- 05/13/10 20:15:11 (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ucore
v2 v3 2 2 = S3 !UltraCore = 3 3 4 S3 !UltraCore (ucore) is a special branch of the S3project:4 S3 !UltraCore (ucore) is a special branch of the Eden project: 5 5 6 - [https://launchpad.net/sahana /ucore]6 - [https://launchpad.net/sahana-eden/ucore] 7 7 8 8 The S3 !UltraCore series contains the pure essentials of S3. It is meant to be truly fast, clean and minimalistic - and the most rigorously tested and quality-approved S3 branch: a rock-solid foundation for the development of S3-based applications. … … 25 25 26 26 Any piece of code that shall be proposed for ucore must: 27 a )be core (meaning, relevant for all S3-based applications)28 b )be in trunk29 c )have a complete developer documentation (including blueprint)30 d )have a maintainer (or a maintainer team)27 a. be core (meaning, relevant for all S3-based applications) 28 b. be in trunk 29 c. have a complete developer documentation (including blueprint) 30 d. have a maintainer (or a maintainer team) 31 31 32 32 The maintainers can submit an informal proposal to the !SahanaPy developer's mailing list to take up their code into ucore. … … 35 35 36 36 A piece of code can be accepted for ucore, if: 37 a )it works perfectly with the existing ucore code38 b )there are no open bugs related to that code in trunk39 c )there are no workarounds or temporary solutions in that code40 d )the code has sucessfully passed some destructive testing (yet to be defined), and at best stood a real-world deployment41 e )the code follows strictly all coding conventions (yet to be defined)37 a. it works perfectly with the existing ucore code 38 b. there are no open bugs related to that code in trunk 39 c. there are no workarounds or temporary solutions in that code 40 d. the code has sucessfully passed some destructive testing (yet to be defined), and at best stood a real-world deployment 41 e. the code follows strictly all coding conventions (yet to be defined) 42 42 43 If code gets accepted for ucore, then that does not mean that all updates of that code will automatically be accepted as well - any update version of the 44 code has to pass the whole procedure again. 43 If code gets accepted for ucore, then that does not mean that all updates of that code will automatically be accepted as well - any update version of the code has to pass the whole procedure again. 44 45 ---- 46 DeveloperGuidelines