| 1 | F3PR Code-Sprint 1 (2008-09-05 - 2008-09-07) Description
|
| 2 | - [ ] Attendees
|
| 3 | - [ ] Thomas Hempel
|
| 4 | - [ ] Christopher Hlubek
|
| 5 | - [ ] Tobias Liebig
|
| 6 | - [ ] What had been done
|
| 7 | - [ ] Implemented
|
| 8 | - [ ] createPackage A new package can be creates. This
|
| 9 | creates Package folder and a Meta
|
| 10 | folder with a package.xml file in it.
|
| 11 | - [ ] activatePackage Stores the package (if found) in the
|
| 12 | internal list of acivated packages
|
| 13 | - [ ] deactivatePackage Removes the packages (if active) from
|
| 14 | the internal list of activated packages
|
| 15 | - [ ] removePackage Removes the packages from all lists and
|
| 16 | from the file system
|
| 17 | - [ ] CLI for Package Manager
|
| 18 | - [ ] What is missing
|
| 19 | - [ ] Package Manager
|
| 20 | - [ ] Downloading packages
|
| 21 | - [ ] Switch package version
|
| 22 | - [ ] Create default action controller
|
| 23 | - [ ] Package Repository
|
| 24 | - [ ] Release package
|
| 25 | - [ ] Search package
|
| 26 | - [ ] Tag released package
|
| 27 | - [ ] Register package key
|
| 28 | - [ ] Block new releases
|
| 29 | - [ ] Open To-Dos
|
| 30 | - [ ] Package versioning The system needs a concept for package
|
| 31 | versioning. The system should be able
|
| 32 | to keep several versions of a certain
|
| 33 | package and it should be possible to
|
| 34 | activate a package for a specific
|
| 35 | context only.
|
| 36 | A possible way to achieve this, would
|
| 37 | be to have the activated version of a
|
| 38 | package always in a subfolder called
|
| 39 | "activeCONTEXT". All other versions are
|
| 40 | located in folders with the version
|
| 41 | number as name. e.g.
|
| 42 |
|
| 43 | Packages
|
| 44 | | \- FLOW3
|
| 45 | | | \- activeDistribution
|
| 46 | | | | \- Classes
|
| 47 | | | \ - ...
|
| 48 | | | \- activeDevelopment
|
| 49 | | | |\- Classes
|
| 50 | | | \ - ...
|
| 51 | | |\- 1.1
|
| 52 | | \ - 1.2
|
| 53 | \- YetAnotherTestPackage
|
| 54 |
|
| 55 | For this implementation, some
|
| 56 | additional things have to clarified
|
| 57 | with FLOW3 project leaders.
|