Jesse, could you please also include the following commit to 3.6.0. After additional testing I found out that it leads to incorrect filtering of not supported rules (https only) on Windows.
https://github.com/apache/cordova-windows/commit/31bac42808e56a2239cbda07a02794147ebafb8b CB-7377 Removes unnecessary rules tracing which is also incorrectly handled by PS Thx! Sergey -----Original Message----- From: purplecabbage [mailto:purplecabb...@gmail.com] Sent: Wednesday, August 27, 2014 11:26 AM To: dev@cordova.apache.org Subject: Re: [Discuss] 3.6.0 Release All tagged too. I'll take care of the npm publish in the morning here. Sent from my iPhone > On Aug 26, 2014, at 11:51 PM, "Sergey Grebnov (Akvelon)" > <v-seg...@microsoft.com> wrote: > > Btw, who will publish cordova-windows to npm? Since the name is not taken > (we previously used cordova-windows8) I can do this, I'm also fine if someone > else who is more experienced in such things will do this. > > Windows platform looks like as 100% ready for tagging, Jesse has added > Release notes and polished other related things. > > -Sergey > -----Original Message----- > From: Steven Gill [mailto:stevengil...@gmail.com] > Sent: Wednesday, August 27, 2014 12:57 AM > To: dev@cordova.apache.org > Subject: Re: [Discuss] 3.6.0 Release > > Hopefully this gets resolved soon. Seeing how it is a BB only issue, it won't > hinder other platforms from tagging. > > >> On Tue, Aug 26, 2014 at 1:53 PM, Josh Soref <jso...@blackberry.com> wrote: >> >> There's still a problem w/ blackberry10. >> >> We have code that assumes the location of the blackberry10 code in >> ~/.cordova/lib/blackberry10, >> >> https://issues.apache.org/jira/browse/CB-7409 >> >> >> I found this while working on the version script (which we should >> have replaced a while ago...). >> >>