Difference between revisions of "Extra meeting 30.1.2012"
Jump to navigation
Jump to search
(Created page with "Category:Meetings {{nav|prev=Regular meeting 26.1.2012|up=Platform development process|next=Regular meeting 6.2.2012}} == Agenda == ;1. Discussion on Layer0 * Hannu present...") |
|||
(11 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
[[Category:Meetings]] | [[Category:Meetings]] | ||
− | {{nav|prev= | + | {{nav|prev=Extra meeting 26.1.2012|up=Platform development process|next=Extra meeting 14.2.2012}} |
+ | |||
== Agenda == | == Agenda == | ||
Line 17: | Line 18: | ||
* Harri/Arto: How to use trunk/stable in products? | * Harri/Arto: How to use trunk/stable in products? | ||
+ | * Meeting material must be delivered to participants on wednesday/thursday axis of the previous week | ||
== Minutes == | == Minutes == | ||
− | ;1. Discussion on Layer0 | + | ;Meeting time: 9.45AM |
+ | ;Present: Antti Villberg, Kalle Kondelin, Hannu Niemistö, Tuukka Lehtonen, Arto Kallio, Jani Simomaa, Harri Ojanen, Marko Luukkainen (arrived at 10AM) | ||
+ | |||
+ | === 1. Discussion on Layer0 === | ||
+ | |||
+ | ; TODO Attach powerpoint presentation | ||
+ | |||
+ | ; ConsistsOf: | ||
+ | * Option 4 seems most elegant | ||
+ | * Impossible to definitively say what the performance effects of the changes are. URIs/indexing/TG export/import will naturally slow down. On the other hand some normal browsing operations will be a little faster and in some cases there will be less data. Obviously this bothers everyone. | ||
+ | * The changes are internal to DB, as long as they change. | ||
+ | * One caveat: TG format must be changed since it currently uses the current ConsistsOf assumption for hierarchy encoding | ||
+ | * '''Ruling:''' No objections, will be implemented | ||
+ | |||
+ | ; Immutable Subgraphs: | ||
+ | * '''Ruling:''' No objections, will be implemented | ||
+ | |||
+ | ; InverseOf: | ||
+ | * '''Ruling:''' Use c), requires immutable subgraphs. Added exception to allow user to still control whether inverses exist or not | ||
+ | ; Export/Import: | ||
+ | * Presented, not evaluated. | ||
+ | ; Constraints: | ||
+ | * Presented, not evaluated. | ||
+ | ; What belongs to Layer0: | ||
+ | * Presented, not evaluated. | ||
− | + | === 2. Discussion on Testing === | |
+ | [[image:Discussion on Testing.pptx]] | ||
− | + | === 3. Other issues === |
Latest revision as of 08:57, 2 April 2012
Previous | Up | Next |
Contents
Agenda
- 1. Discussion on Layer0
- Hannu presents PowerPoint
- 2. Discussion on Testing
- Organization of tests wrt. plugins and automation
- Automatic testing procedures
- Reporting of test results
- Priorities of creating tests
- 3. Other issues
- Harri/Arto: How to use trunk/stable in products?
- Meeting material must be delivered to participants on wednesday/thursday axis of the previous week
Minutes
- Meeting time
- 9.45AM
- Present
- Antti Villberg, Kalle Kondelin, Hannu Niemistö, Tuukka Lehtonen, Arto Kallio, Jani Simomaa, Harri Ojanen, Marko Luukkainen (arrived at 10AM)
1. Discussion on Layer0
- TODO Attach powerpoint presentation
- ConsistsOf
- Option 4 seems most elegant
- Impossible to definitively say what the performance effects of the changes are. URIs/indexing/TG export/import will naturally slow down. On the other hand some normal browsing operations will be a little faster and in some cases there will be less data. Obviously this bothers everyone.
- The changes are internal to DB, as long as they change.
- One caveat: TG format must be changed since it currently uses the current ConsistsOf assumption for hierarchy encoding
- Ruling: No objections, will be implemented
- Immutable Subgraphs
- Ruling: No objections, will be implemented
- InverseOf
- Ruling: Use c), requires immutable subgraphs. Added exception to allow user to still control whether inverses exist or not
- Export/Import
- Presented, not evaluated.
- Constraints
- Presented, not evaluated.
- What belongs to Layer0
- Presented, not evaluated.
2. Discussion on Testing
File:Discussion on Testing.pptx