for the record: michael, marcel and myself had a short discussion in the office. based on the indication that we can reach consensus for stefans proposal, we went ahead deprecating the mk api for 1.2 as initial step for the cleanup. all subsequent cleanup work will be done once the stable 1.2 release is out giving us enough time to get rid of the few remaining usages of the mk-api in oak-core and oak-it. see subtasks for OAK-2697 for the proposed sequence of steps.
kind regards angela On 30/03/15 14:16, "Angela Schreiber" <[email protected]> wrote: >see https://issues.apache.org/jira/browse/OAK-2697 > >On 30/03/15 12:49, "Michael Dürig" <[email protected]> wrote: > >> >> >>On 30.3.15 10:01 , Angela Schreiber wrote: >>> Not sure, what the correct procedure is now. Shall I cancel >>> this vote and start a new one for >>> >>> "moving oak-mk and oak-mk-api to attic and removing all other >>> MicroKernel implementations" >>> >>> ? Or should I rather extend this very vote to make sure everyone >>> would be comfortable with the extended scope as proposed by Stefan? >>> >>> Please advise >> >>This vote didn't pass. >> >>But there is strong indication that we have a consensus for Stefan's >>proposal. The most controversial part is probably the timing of such a >>change, which it turn depends on its complexity and impact. I think it >>is best to start with an JIRA issue for this and prepare a bunch of >>patches for people to review and take it from there then. >> >> >>Michael >> >> >
