+1 for v1. If we don't go back (= we don't make unstable stable
modules) it is enough IMO
@mark:
i never said that we should do #2.
regards,
gerhard
2013/11/12 Mark Struberg strub...@yahoo.de
Pete, Gerhard
The Problem here is that there are only 2 ways to handle the situation:
1.) all modules share the same version but have different maturity grades
2.) each module has it's
the minimum before v1:
everybody documents the feature/s they added (/helped with) within the next
weeks.
(for sure the rest is very welcome to join and/or provide feedback.)
if we don't handle it as a blocker for v1, it won't happen any time soon.
the optimum before v1:
docs + examples + agreed
-1 for 1.0 - till adding the most important features from CODI (e.g.
ViewAccessScoped)
2013/11/12 Gerhard Petracek gerhard.petra...@gmail.com
the minimum before v1:
everybody documents the feature/s they added (/helped with) within the next
weeks.
(for sure the rest is very welcome to join
