So. I think that the current semi-existence of Jackson Kotlin module is not good for anyone. While there has been positive progress wrt many features in 2.10, there have been a few new issues that are partly my fault for not being able to properly sanity check risks, concerns, or weight effects of changes. A particular example would be changes in 2.10 to handling of Singleton values, where situation is pretty close to lose-lose: regardless of whether to just blindly skip matching JSON content (2.10 behavior), return Singleton, or deserialize content, drop resulting instance and return Singleton (2.9 and before).
At this point my feeling is this: unless a new set of active maintainers can be found, agreed upon, I do not think I should release new minor versions of Kotlin module. That just gives false impression of maintained component. On plus side, multiple individuals have mentioned they would be interested in helping -- big thank you to everyone. But the problem here is this: since I can not properly judge development of the module, I also can not quite figure out how and who to hand over guardianship either. I would be very interested in hearing suggestions, proposals for finding new owners: and one of few things I have opinion about this here is that ownership should be shared across more than 1 individual (but probably no more than 2 - 4). So. WDYT? -+ Tatu +- -- You received this message because you are subscribed to the Google Groups "jackson-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jackson-dev/CAL4a10jSFPzGqZJGSyDvrfpWyGRpeFiH2%2BWBphSZev_EXZuGMQ%40mail.gmail.com.
