On 13/09/2017 09:22, Vikas Saurabh wrote: > Hi, > > On Wed, Sep 13, 2017 at 9:32 AM, Chetan Mehrotra > <chetan.mehro...@gmail.com> wrote: > >> Would the backport be of use now? As any upgrade I think would happen >> first to initial release from that branch where this fix would not be >> present > Well, from arguments pov, I think one can always package upgraded > setup with latest oak (yes, I understand that's not the case for AEM). > But, my hidden agenda is that "this is a bad bug + the fix is simple > => we should fix it". > But, sure, if it doesn't feel right, then I agree it's a not a major > bug from backport pov.
+1 for backporting. It's trivial, well test covered and it's definitely better to have this as we don't know exactly what an Oak deployment could be. D.
