I plan to test and tag 3.4.0 iOS today if there are no objections. - went through all the iOS issues and labelled the ones that are core with 'core' : https://issues.apache.org/jira/issues/?jql=project%20%3D%20CB%20AND%20issuetype%20in%20standardIssueTypes()%20AND%20component%20%3D%20iOS%20AND%20labels%20%3D%20core%20AND%20status%20%3D%20Openand tried to resolve them as best I could - the 14 core issues left don't seem critical - left the iOS plugin issues for later since they have a different release schedule
On Thu, Jan 23, 2014 at 9:18 AM, Steven Gill <[email protected]> wrote: > James: it totally will. > > I plan on doing a tools release, plugins release and platforms release for > 3.4. > > > On Thu, Jan 23, 2014 at 8:22 AM, James Long <[email protected]> wrote: > > > This thread is getting quite broad but I need to make you guys aware > > of this: the camera plugin is currently totally broken for Firefox OS > > and the fix has been waiting on the dev branch for weeks. I want to > > make sure that the fix is going to be merged into master and go out > > with 3.4: https://issues.apache.org/jira/browse/CB-3204 > > > > On Wed, Jan 22, 2014 at 7:46 PM, Joe Bowser <[email protected]> wrote: > > > OK, Got it working now. I just tagged it. I'll update the ticket > > > once JIRA stops reindexing. > > > > > > On Wed, Jan 22, 2014 at 4:25 PM, Steven Gill <[email protected]> > > wrote: > > >> Looks like coho was changed to use grunt cordovajs which doesn't > exist. > > My > > >> local copy didn't have that change. I will push up my coho > > >> > > >> > > >> On Wed, Jan 22, 2014 at 4:21 PM, Steven Gill <[email protected]> > > wrote: > > >>> > > >>> ./coho prepare-release-branch --version 3.4.0-rc1 -r android > > >>> ./cordova-android/ =========== Executing: git fetch --progress origin > > >>> ./cordova-android/ =========== Executing: git fetch --progress --tags > > >>> origin > > >>> ./cordova-android/ =========== Confirmed already up-to-date: > > >>> cordova-android > > >>> ./cordova-android/ =========== Executing: git checkout -b 3.4.x > > >>> Switched to a new branch '3.4.x' > > >>> ./cordova-js/ ================ Executing: git checkout -q 3.4.0-rc1 > > >>> ./cordova-js/ ================ Executing: grunt > > >>> > > >>> why are our last lines different? > > >>> > > >>> > > >>> On Wed, Jan 22, 2014 at 4:09 PM, Joe Bowser <[email protected]> > wrote: > > >>>> > > >>>> Hey > > >>>> > > >>>> It looks like something either changed with cordova-js or with coho, > > >>>> because I can't get coho to build: > > >>>> jbowser-MacBookPro:~ jbowser$ cordova-coho/coho > prepare-release-branch > > >>>> --version 3.4.0-rc1 -r cordova-android > > >>>> ./cordova-android/ =========== Executing: git fetch --progress > apache > > >>>> ./cordova-android/ =========== Executing: git fetch --progress > --tags > > >>>> apache > > >>>> ./cordova-android/ =========== Confirmed already up-to-date: > > >>>> cordova-android > > >>>> ./cordova-android/ =========== Executing: git checkout 3.4.x > > >>>> Already on '3.4.x' > > >>>> ./cordova-js/ ================ Executing: git checkout -q 3.4.0-rc1 > > >>>> ./cordova-js/ ================ Executing: grunt cordovajs > > >>>> Warning: Task "cordovajs" not found. Use --force to continue. > > >>>> > > >>>> I'm going to have to proceed manually with the tagging and > vendoring. > > >>>> The next time we change how we build the JS, can we make sure coho > > >>>> works with it, otherwise there's no point having it. > > >>>> > > >>>> On Wed, Jan 22, 2014 at 2:04 PM, Josh Soref <[email protected]> > > >>>> wrote: > > >>>> > Fwiw, cordova-blackberry is currently broken due to the config.xml > > >>>> > move. > > >>>> > > > >>>> > We need to land a fix for this. > > >>>> > > > >>>> > > > --------------------------------------------------------------------- > > >>>> > This transmission (including any attachments) may contain > > confidential > > >>>> > information, privileged material (including material protected by > > the > > >>>> > solicitor-client or other applicable privileges), or constitute > > non-public > > >>>> > information. Any use of this information by anyone other than the > > intended > > >>>> > recipient is prohibited. If you have received this transmission in > > error, > > >>>> > please immediately reply to the sender and delete this information > > from your > > >>>> > system. Use, dissemination, distribution, or reproduction of this > > >>>> > transmission by unintended recipients is not authorized and may be > > unlawful. > > >>>> > > > >>> > > >>> > > >> > > >
