Yes, I agree, to be on the safe side we should replace the json stuff. This might delay Sling 9 a little bit, but that should be fine.
Carsten Karl Pauls wrote > I guess it would be a blocker. > > I created SLING-6679 to track updating bundles and will create some > sub-issues for a couple of bundles where I have some potential > patches. Its unfortunately not going super smoothly - there is at > least one bundle where I'm not sure what todo and with the other it > will be necessary to review the patches and make sure they don't > change anything. > > regards, > > Karl > > On Wed, Mar 22, 2017 at 3:11 PM, Stefan Seifert <[email protected]> > wrote: >> btw: sling 9 currently still has to ship with the commons.json bundle based >> on the json.org code. >> is this a release blocker if we want to release sling 9 after march 31th? >> >> we still have some dozens of sling bundles depending on commons.json code. >> >> stefan >> >> >>> -----Original Message----- >>> From: Carsten Ziegeler [mailto:[email protected]] >>> Sent: Monday, March 20, 2017 12:13 PM >>> To: Sling Developers >>> Subject: Where are we with Sling 9? >>> >>> Hi, >>> >>> sorry I lost a little bit track of where we are wrt Sling 9. Is anything >>> blocking us from getting it out the doors? >>> >>> Regards >>> Carsten >>> -- >>> Carsten Ziegeler >>> Adobe Research Switzerland >>> [email protected] >> > > > -- Carsten Ziegeler Adobe Research Switzerland [email protected]
