udaykiran19491/user-stories-from-tawos-for-llm-fine-tuning huggingface dataset:
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Currently, we're limited to 2b graph edges by type from a single source or target edge.  In highly connected graphs, this makes it impossible to construct the entire graph.  To alleviate this, we should use a commit log + time series post processing.  I envision this working in the following way.  # Have a commit log set of CF's for all edges.  The gc_grace period should be set very low.  This should be around 1 minute.  Re-writing existing edges (due to phantom deletes) will not be an issue, all algorithms should be idempotent. # Always write to the commit log, Fire the async processing as usual, and immediately return # In post processing use variable size time series (algorithm TBD) to copy the edge from the commit log CF into the new correct CF.  Remove the entry from the commit log. # When seeking values, seek values from the correct shards (via time) on disk as well as the commit log.  These values can are already time ordered, so an in memory merge can easily take place for a final result set.  "
Answer: 65184.0

User story: "i am removing the dynamic menus from the portal, it is overcomplicated, and i'm adding bower dependencies so devs can import the portal and override"
Answer: 60173.0

User story: "Adding contextual help to portal also bringing in analytics framework to make life easier for those that wish to use GA"
Answer: 61857.0

User story: "Provide a way to to integrate Core Persistence into Usergrid by implementing the existing Usergrid EntityManager interface, but with the Core Persistence API providing entity and other forms of persistence."
Answer: 117870.0

User story: "The use case would be: You have a key, ID, or other piece of data that needs to be passed in the query string to allow the request to be authenticated, tracked, etc.  An example would be if you have a secure proxy in front of the API server that requires a user-specific token to access the APIs behind it. an example might look like:  curl http://api.usergrid.com/app/org/endpoint?token=USERTOKEN"
Answer: 691171.0

User story: "We need to extend UGC to include data upload and data download capabilities.    1. Spec out how this will work (do design doc, get reviewed by Rod, Chris Von See, and <USER>. 2. Should include ability to upload CSV or JSON files. 3. Eventually we will extend functionality to include uploading file directly to server, but interface in UGC should work the same. 4. Download would be based on a path plus optional query.   4. Should be able to set file type for download."
Answer: 1.0

User story: "Create two tests that both use multiple threads to write and index a large amount of data and then multiple threads to read all that data.  Implement one version of the test that runs against the old Usergrid Entity Manager and one version that runs against the new Core Persistence API.  Implement tests as JUnit tests so that they can be run by an automated build system like Jenkins on an automated testing system like Chop."
Answer: 449810.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Need an efficient way to fetch entities for a specified list of Ids. This could perhaps be a new method into the EntityCollectionManager interface:     List<Entity> load( List<id> ids );   Once it is implemented, the Query Index module's Results class should be changed to use the new multi-get method."
Answer: 449745.0

User story: "When an entity or a graph edge is committed, it requires post processing.  In the case of entities, this is indexing and processing of deletes from the mark operation.  In the case of edges, deletes from marks are required.  We need a general mechanism for creating a timeout checkpoint.  This will then return a timeout object.  This object can then be invoked asychronously.  Upon completion, it should remove the timeout object.  Only during a failure (JVM shutdown, node death etc) should the timeout event fire.  The timeout event will then restart the post processing.  This must ensure the following.  # No event will ever be lost.  Events will always fire eventually at a time >= to it's timeout  # Events should encapsulate all data required to perform async processing.  Since this could run on a different node than the caller, no state should be shared on queue/start/failover  # Events receivers should be idempotent.   They should checkpoint their work.  If at an time a receiver fails it may be resumed by another node.  The new node should be able to resume work without the need to perform all processing again"
Answer: 76186.0

User story: The new Core Persistence modules in the Usergrid "two-dot-o branch" branch support storing and retrieving Entities to Cassandra, but do not yet support indexing and query.  This task is to add an interface for Indexing, Deindexing and Querying of Core Persistence Entities that fully supports the Usergrid 1.0 query syntax.
Answer: 5936.0

User story: "The Inflector.java utility class is GPL based:  https://github.com/usergrid/usergrid/blob/master/stack/core/src/main/java/org/apache/usergrid/utils/Inflector.java  See USERGRID-4 for additional details "
Answer: 14319.0

User story: "http://mxcl.github.com/homebrew/  Homebrew is a package manager for OSX.  We should create a homebrew recipe for Usergrid, to make installing and running locally much easier."
Answer: 1010883.0

User story: """Clients have to try re-authenticating if they receive a 401.   {code}  $ curl -i http://api.usergrid.com/tim/sandbox/users/ti1231231  HTTP/1.1 401 Unauthorized  Access-Control-Allow-Origin: *  Content-Type: application/json  Date: Wed, 30 Oct 2013 20:22:38 GMT  Server: Apache-Coyote/1.1  Set-Cookie: rememberMe=deleteMe; Path=/; Max-Age=0; Expires=Tue, 29-Oct-2013 20:22:38 GMT  Content-Length: 206  Connection: keep-alive   {""""error"""":""""service_resource_not_found"""",""""timestamp"""":1383164558729,""""duration"""":0,""""exception"""":""""org.usergrid.services.exceptions.ServiceResourceNotFoundException"""",""""error_description"""":""""Service resource not found""""}  {code}"""
Answer: 125003.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: """Anecdotal evidence from production suggests that we are not buffering the file correctly. Scope of this issue should include:  - verify upload of large files  - make sure large files are spooled to disk and never occupy more than 5mb of memory, regardless of physical size  - once written out completely to disk, large files are POSTed to S3 bucket as anticipated   To generate files of specific size, use the following:  dd if=/dev/urandom of=/tmp/largefile bs=1m count=20   This will generate a file exactly 20MB in size from 1MB blocks of random data.   You will need to include the """"content-type"""" attribute on the Asset while testing if you use random data as described above or the content-type sniffer will get confused."""
Answer: 46.0

User story: """User is doing a geolocation query using three parameters. When he does this, the first page of data (10 records) is returned, but subsequent pages are empty.   For example, this query returns 19 rows:  """"location within 40075160 of 37.33517518, -122.03255055 and bucketId='LosAngels'""""   whereas this query, which should only omit one record returns 10 records:  """"location within 40075160 of 37.33517518, -122.03255055 and NOT email='<EMAIL>' and bucketId='LosAngels'""""   The order doesn't seem to matter. I tried it with both bucketId before and after email. Also, the field doesn't seem to matter because the following query also returns only 10 rows when it should return 18:  """"location within 40075160 of 37.33517518, -122.03255055 and NOT name='Fyndher Vtwo' and bucketId='LosAngels'""""   ."""
Answer: 1036710.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: """Not sure where this comes from. Here's the stack trace on the server   {code}  java.lang.NullPointerException  at org.usergrid.persistence.Query.containsUuidIdentifersOnly(Query.java:464)  at org.usergrid.persistence.Query.containsSingleUuidIdentifier(Query.java:453)  at org.usergrid.services.ServiceContext.isByUuid(ServiceContext.java:269)  at org.usergrid.services.ServiceContext.isByQuery(ServiceContext.java:277)  at org.usergrid.services.AbstractService.invoke(AbstractService.java:593)  at org.usergrid.services.AbstractService.invoke(AbstractService.java:509)  at org.usergrid.services.ServiceRequest.execute(ServiceRequest.java:186)  at org.usergrid.services.ServiceRequest.invokeMultiple(ServiceRequest.java:229)  at org.usergrid.services.ServiceRequest.execute(ServiceRequest.java:189)  at org.usergrid.services.ServiceRequest.execute(ServiceRequest.java:175)  at org.usergrid.rest.applications.ServiceResource.executeServiceRequest(ServiceResource.java:206)  at org.usergrid.rest.applications.ServiceResource.executePost(ServiceResource.java:298)  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)  at java.lang.reflect.Method.invoke(Method.java:597)  at com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)  at com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185)  at com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)  at com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:288)  at com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:134)  at com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)  at com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:134)  at com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)  at com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:134)  at com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)  at com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:134)  at com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)  at com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:134)  at com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)  at com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:134)  at com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)  at com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:134)  :   {code}  """
Answer: 137990.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: """ Problem:  User has 6000+ entities in their collection and their query returns the above NullPointerException. If they reduce the number of entities to less than 6000, the query works. User plans to add 8000 to 12000 entities in the future.    API call:  http://api.usergrid.com/fdsafdsa/fdsafdsa/flatsales?ql=select%20*%20where%20districtid%3D1%20and%20roomscount%3D3&limit=&_=1383958716647  Result:  {""""error"""":""""null_pointer"""",""""timestamp"""":1384220932467,""""duration"""":0,""""exception"""":""""java.lang.NullPointerException""""}    Access log entry shows HTTP status code 400 error:  192.168.12.144 - - [12/Nov/2013:01:45:06 +0000] """"GET /fdsafdsa/fdsafdsa/flatsales?ql=select%20*%20where%20districtid%3D1%20and%20roomscount%3D3&limit=&_=1383958716647&access_token=YWMtyO13lkizEeOWYnG2ICC8bAAAAUJdb8cTMcXAl8tze6vtB8IwgcO4hZ7kMGY HTTP/1.1"""" 400 119 688 text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8 application/json  Host: atc00usergrid Name: /var/log/tomcat7/localhost_access_log.2013-11-12.txt   catalina.out shows me nothing, we eat the stack trace.     """
Answer: 898318.0

User story: Using the new 2.0 code base, create a directed edge graph implementation.  *Terminology*  Id: And identifier interface.  The identifier has a string type, and a UUID Edge Type: The type of the edge as a string.  "like", "follows" etc Version: A time uuid that represents the version of the edge between the source and target Source: The source node in the directed edge Target: The target node in the directed edge.  *Data access operations*  Get edges from source by edge type  Get edges from source by edge type and target type  Get edges to target by edge type  Get edges to target by edge type and source type  Get all edge types from source  Get all target types from source with edge type  Get all edge types to target  Get all source types to target with edge type
Answer: 357393.0

User story: "In the CollecitonModule for Guice, there appears to be old configuration code.  Can we remove and consolidate this to fully utilize the GuicyFig configurations?"
Answer: 822495.0

User story: "We need to determine the time between entity load and search availability and see if the data set size impacts that."
Answer: 507641.0

User story: "We want to see how fast we can search entries as a function of data size."
Answer: 865763.0

User story: "We want to see how fast we can delete entries and their indices with ES as a function of the data size."
Answer: 865764.0

User story: "Our existing PriamCluster scripts start a Cassandra cluster that is useful for performance testing of Usergrid.   Modify these scripts to install Elastic Search on each Cassandra node so that we can test the performance of Elastic Search for Core Persistence.  Use RAID for both Cassandra and ElasticSearch data files."
Answer: 51908.0

User story: "We want to see how fast we can load entries and have it indexed by ES as a function of the total data set loaded. "
Answer: 865767.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "To enable our Contributor Workflow we need to setup sync of our code-review repo at GitHub (usergrid/usergrid) to our Apache Git repo (incubator-usergrid). This should happen at least once a day.  "
Answer: 28.0

User story: "All package namespaces need to be updated from org.usergrid to org.apache.usergrid."
Answer: 151073.0

User story: "We need to get the code into ASF's git repo as the first step to moving forward under ASF processes. "
Answer: 11635.0

User story: "Merge code base of java-api branch into master branch of MXNet repo in order to bring over Java API work for MXNet 1.4 release."
Answer: 11651.0

User story: "The current MXNet C++ package contains API for training and inference workflows.    In order to decide whether we should continue to support training APIs, we need to understand the customer use cases.    The goal of this story is to gather the internal and external customer usage details of training API available in C++ Package.    We will evaluate:    1.   Github issues.    2. Discussion forums, and    3. Website analytics    to establish these details. Based on this analysis we will recommend the future direction.    The output of this story will be a one-pager document."
Answer: 30118.0

User story: "Scope of work:  - unit tests (per PR). These are Java unit tests, not Scala unit tests.  - integ tests of examples (nightly). There is at least one integ test needed - for SSD example"
Answer: 40314.0

User story: "Complete blog post describing Scala API improvements in MXNet 1.3."
Answer: 127918.0

User story: "https://github.com/apache/incubator-mxnet/issues/5052"
Answer: 31494.0

User story: "MXNet Scala API package should be easily distributable to users who would like to use Scala API for inference or training. Scope of this story is to provide users with complete package of MXNet engine, all its necessary dependencies and ScalaAPI bindings. Scala API supports three flavors of MXNet: MacOSX CPU, Linux CPU and Linux GPU, these flavors should be reflected in corresponding packages.    As a result of this story users will be able to choose and download maven package that would have everything needed for inference or training using Scala API included. User will be able to start using MXNet with Scala API bindings right away after that."
Answer: 255056.0

User story: "*Acceptance Criteria*  A markdown doc in Apache MXNet cwiki    "
Answer: 31308.0

User story: "https://lists.apache.org/thread.html/f4aafd0e772b8ae5d3a27fe30a354a11da188ad2c8282bad336f3037@%3Cdev.mxnet.apache.org%3E"
Answer: 174237.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: As a new developer, coming to the alloy repository can be quite irritating, because the latest release is marked with 2015, although there is still a vivid development around it. Therefore, two things could be done to "Make Alloy releases great again":    1. Mark the latest release (e.g. 1.15.0) as actually latest  2. Include the changelog in the releases page (same for Titanium itself btw - open source developers use that page as their primary source of releases)    See a few screenshots attached (Alloy right now vs Vue.js)
Answer: 56046.0

User story: "As per ALOY-1599 Alloy releases on GitHub are being tagged every build, we should only tag when we do an npm publish so that the releases on GitHub reflect the npm versions"
Answer: 87.0

User story: "Customer is having following question about core.js in Alloy proejct. Please help to provide a proper answer.    A single window core.js  was used in the app mentioned in the blog, http://www.appcelerator.com/blog/2014/06/now-app/, which is the actual link which has the multi window approach.    It was not updated from the past three years.   If it is good, people should be talking about it everywhere and updating it frequently.  So, I am a bit skeptical about it.     I have a few questions for you.     Does appcelerator use it in all their apps or was it used only in that particular app mentioned in the blog?  Is the advisable to use it in all our apps as a standard navigation framework?  Is it good enough to use in very complex apps?  Is it good enough at least for simple apps?    Please share your inputs on when it can be used and when it cannot be used.  "
Answer: 1318046.0

User story: "Hi,  We are trying to get  Twitter user info using following documentation:   http://docs.appcelerator.com/platform/latest/#!/api/Alloy.builtins.social    Steps :  1. Create a simple alloy project.  2. Add following code:  {code}  var social = require('alloy/social').create({   consumerSecret :'yyy',   consumerKey : 'zzzz'  });    function doClick(e) {   if (!social.isAuthorized()) {    social.authorize(function(e) {     alert(JSON.stringify(e));    });   }  }  $.index.open();  {code}    3. After Authorize apps.  [^0-sa-d2-9e99ac3363469698d457463077931f46.jpg]  4. It said enter that pin number   !Screenshot_20170312-231225.png|thumbnail!  5. Where to put that pin number ?  "
Answer: 909962.0

User story: "Alloy uses {{wrench.js}} extensively throughout its code base, however the module have been  deprecated. We should replace it with another module to do filesystem operations, i.e. fs-extra."
Answer: 444681.0

User story: "At the moment, Uglify has limited support of ES6 features. https://github.com/mishoo/UglifyJS2/issues/448. Consider moving to using Babylon. https://github.com/babel/babylon    "
Answer: 512547.0

User story: "Should be remove from Alloy repo in favour of:  https://github.com/appcelerator-developer-relations/appc-sample-geocoder"
Answer: 1063.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Currently when compile tests fail they show:    !Screen Shot 2016-03-28 at 13.06.58.png!    There's two problems with this:    1. It is showing both the message and the stack trace, last is of no use  2. It is not showing what actually is different    I expect it to give:    !Screen Shot 2016-03-28 at 13.06.20.png!"
Answer: 292.0

User story: "We don't have a concise developer guide for Alloy.  It would be great if there is a page that provides step by step guide for anyone who wants to contribute to Alloy.  Some of the basic requirement for a PR to warrant a review:   1. Sign the CLA  2. Link to JIRA ticket  3. Include test app  4. All tests should pass  5. Code Conventions, this would be solved by integrate a linter.  "
Answer: 75119.0

User story: There are a number of out-dated Alloy dependencies, we should update them to the latest stable versions.    {quote}  "colors" can be updated from 0.6.0-1 to 1.1.2 (Installed: none, Latest: 1.1.2)  "pkginfo" can be updated from 0.2.2 to 0.3.0 (Installed: none, Latest: 0.3.0)  "commander" can be updated from 0.6.1 to 2.8.1 (Installed: none, Latest: 2.8.1)  "wrench" can be updated from 1.3.9 to 1.5.8 (Installed: none, Latest: 1.5.8)  "jsonlint" can be updated from 1.5.1 to 1.6.2 (Installed: none, Latest: 1.6.2)  "uglify-js" can be updated from 2.4.15 to 2.4.24 (Installed: none, Latest: 2.4.24)  "source-map" can be updated from 0.1.9 to 0.5.1 (Installed: none, Latest: 0.5.1)  "moment" can be updated from 2.7.0 to 2.10.6 (Installed: none, Latest: 2.10.6)  "node.extend" can be updated from 1.0.10 to 1.1.5 (Installed: none, Latest: 1.1.5)  {quote}
Answer: 1268687.0

User story: Looking for optimisations of https://github.com/appcelerator-developer-relations/Mobile-App-Performance I saw that enable strict mode meant a 20x performance increase on Android and a significant increase on iOS as well.    Unfortunately, because {{"use strict";}} needs to be the first line of the file or function scope and Alloy wraps the original controller code, a developer cannot (simply) enable strict mode. The workaround is to wrap inline controller code in a self-executing function and add {{"use strict";}} as the first line for this and every other function.    https://community.appcelerator.com/topic/391/how-to-enable-strict-mode-in-alloy    h3. Phase 1: Always add strict  We should probably promote strict mode in our docs, but with Alloy we could even force it. Simply adding {{"use strict";}} to all compiled files will only mean a slight decrease of performance if the code is not really strict but a huge increase if it is, as this [StackOverflow user found|http://stackoverflow.com/questions/23997267/using-node-why-is-code-so-much-faster-with-use-strict].    h3. Phase 2: Correct code to be strict  I'm not sure if UglifyJS maybe already does this, but there's several packages out there that can automatically correct strict lint errors and thus make the code strict for the user (or warn him if it's not).
Answer: 1058457.0

User story: "DEVOPS-1847 investigation."
Answer: 5.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: The https://github.com/<USER>alloy-smelter offers some nice capabilities that should perhaps be included in Alloy itself. For example, copying/moving/renaming/deleting controllers.    Sub-tickets will be needed to implement the individual features.    Alternately, alloy-smelter could be wrapped, providing "alloy foo" commands that call to smelter.
Answer: 103421.0

User story: "A community pull request for ALOY-1144 was merged to master. It did not include a test app. I added one for the corresponding PR I created to implement the fix in the 1_5_X branch. This ticket is to add that test app to the test/apps/testing folder for the master branch."
Answer: 4486.0

User story: "Investigate the use of tiO2 for automated runtime testing to improve our test coverage and improve quality for Alloy development."
Answer: 15484.0

User story: "We need to update docs as part of the larger Epic ticket.     We'll need to update existing pages (such as http://docs.appcelerator.com/titanium/latest/#!/guide/Alloy_Samples) and possibly create new ones."
Answer: 302343.0

User story: "h2. Description  When adding a breakpoint to alloy.js, the debugger does not stop at it.    h2. Steps to reproduce  1. Create a new Alloy project  2. Add some code into alloy.js  3. Add a breakpoint in alloy.js  4. Run debugger"
Answer: 29262.0

User story: "Document jake, tools/create_test.js, Harness and the associated project"
Answer: 73009.0

User story: "Document the team processes, including such topics as:    * how to format a pull request  * ticket comment format to use once you have submitted a pull request  * any deviations from standard Engineering processes  * functional & code review processes  * how to notify the Docs team that a new feature or fix should be described in release notes or fully documented"
Answer: 73083.0

User story: "Document the folders and files within the repo, noting the purpose of each and how each is used by the various Alloy commands."
Answer: 372743.0

User story: "I've submitted a PR to xmldom to fix issues with unclosed comments, which cause an infinite loop during XML parsing. If/once that PR is accepted, update Alloy package dependencies to require the new version.    PR: https://github.com/jindw/xmldom/pull/74 "
Answer: 19994.0

User story: "We need to change the androidView behavior for optionDialog (and any other components that support an Android-specific view as a child) so that an AndroidView proxy parser is used rather than creating an arbitrary view.    Need also to communicate the change, as it deprecates old behavior.    Instead of an anroidView being assigned like this:    {code:xml}  <OptionDialog>      <View/>  </OptionDialog>  {code}    It should instead be like this, like the rest of the generic view proxy properties:    {code:xml}  <OptionDialog>      <AndroidView>          <View/>      </AndroidView>  </OptionDialog>  {code}  "
Answer: 251938.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: If you attempt to compile an Alloy app that has [should.js|https://github.com/visionmedia/should.js] (the browser-compatible file that works with traditional Titanium dev), it will result in the following compile time error:    {code}  [INFO] ----- OPTIMIZING -----  [INFO] - iphone/alloy.js  [TRACE]   processing "builtins" module...  [TRACE]   processing "optimizer" module...  [TRACE]   processing "compress" module...  [INFO] - iphone/should.js  WARN: ERROR: Unexpected token keyword «with», expected punc «(» [iphone/should.js:383,6]  [ERROR] Error generating AST for "/Users/<USER>development/aloy920/Resources/iphone/should.js"  [ERROR] Unexpected token keyword «with», expected punc «(»  [ERROR] line 383, column 6, position 9813  {code}    We should investigate the root of the error, put in a quick fix, then address the specific problems with uglify-js either via new options or an update to uglify-js.
Answer: 260655.0

User story: "Make sure all samples (rss, todo, mapping) work for the supported platforms."
Answer: 1522.0

User story: "Assemble the release notes in the changelog for version 1.3.0"
Answer: 4102.0

User story: "Work with existing CI to get Alloy processed in the loop"
Answer: 273438.0

User story: We should remove "jake" from the list of dependencies, as jake needs to be installed globally and cannot be installed that way via the dependency list. The [github docs for using jake|https://github.com/appcelerator/alloy#running-sample-test-apps] show clearly how to do this, so there's no reason for it to be in the dependency list.
Answer: 7.0

User story: There's a number of ways to speed up Alloy compile time. 2 simples ones are setting the following values in the config.json:    {code:javascript}  {    "sourcemap": false,    "adapters": []  }  {code}    This will skip the sourcemap step and won't include any sync adapters. Each test app should be evaluated based on its needs and have an optimized config.json to make the automated test suite run as quickly as possible.
Answer: 11.0

User story: The current list of "contributors" in the package.json for alloy is dated. We should make use of [AUTHORS file shortcut available in npm|https://npmjs.org/doc/json.html] for adding contributors. We should also create a simple script that will pull the contributors from github and assemble this AUTHORS file.
Answer: 18785.0

User story: "h2. problem    Android & Mobileweb have some issues rendering the dynamic_styling app's UI, listed here respectively:  * TIMOB-14753  * TIMOB-14754    Slight adjustments should be made to the appear to avoid the appearance of these UI bugs in the Alloy app    h2. expected    The app should lay out the UI and behave similarly across all supported platforms.  "
Answer: 35948.0

User story: The oauth builtin has been disabled in the "unstable" folder for many versions of Alloy now. There have been no requests for this specific functionality to be added into the builtins. Therefore, the builtin will be removed as it represents unnecessary bloat.
Answer: 3.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "PR: https://github.com/appcelerator/alloy/pull/180    Needs to be reviewed and merged"
Answer: 2828.0

User story: Since Studio shows the alloy samples under the "Alloy" category, having it also in the label will appear redundant.
Answer: 154.0

User story: "Need a test app for developers to use an example of how to use the new dynamic styling functionality."
Answer: 10047.0

User story: The constants.js file is located in the "Alloy/common" folder, which should be reserved for modules that work in both the nodejs and Titanium environment. In its current state, the module works only with nodejs. This module needs to be made to work with Titanium as well and distributed with the runtime modules so it can reliably be used by other modules at runtime. This should involve either wrapping specific sections in environment conditionals, or create a derived version of the constants.js file more tailored for runtime.
Answer: 1553.0

User story: only modules that would work in both nodejs and Titanium should be housed in the "Alloy/common" folder in the alloy distribution. While logger.js _should_ work in both environments, it is not necessary for it to attempt to replace the current Ti.API logging functions. For this reason it should be moved out of the "Alloy/common" folder and into the "Alloy" folder. All require() calls referencing logger.js will also need to be changed as well.
Answer: 87.0

User story: "All sample and test apps associated with the Alloy repository currently work with the Android, iOS, and Mobileweb platforms, or at the very least have graceful messages and failures where a particular platform does not work. The same needs to be achieved for Blackberry. This will likely serve to surface a number of Titanium-level issue with Blackberry."
Answer: 919405.0

User story: "When a new version of alloy is released, e.g. 3.1.1, the corresponding source code should be tagged with 3.1.1. This is to help Studio implemnt TISTUD-4632.  "
Answer: 2124.0

User story: "Create a test app that leverages global, controller, theme, and platform specific styles that produce different results on all platforms. These styles should be additive, overwriting, use device queries, and basically anything that can test Alloy's ability to merge the files correctly."
Answer: 563894.0

User story: "Need to release Alloy 1.1.1 in order to support BB as it cannot wait until 1.2.0."
Answer: 16166.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: Blackberry support was recently added to Alloy (ALOY-424). While it wasn't terribly complicated it took a little more than a day to implement and test to make sure all the various functionality regarding platforms was accounted for. In order to make this easier with future platforms, it would be ideal to abstract the bits of platform-specific functionality into config files that will make this trivial in the future, as simple as a one-file pull request against Alloy by the platform creator.    h2. Notes on adding platforms    _this information was learned during the process of adding Blackberry to Alloy_    * Add platform to:  ** CONST.PLATFORMS  ** CONST.PLATFORM_FOLDERS  ** CONST.PLATFORM_FOLDERS_ALLOY  * Add platform conditional optimization to compile/optimizer.js  * Add platform to CONDITION_MAP in compile/index.js  * Add platform to config.json and widget.json templates, if appropriate  * Add platform to appropriate adapters in info command  * Add platform to platforms in optimizer.js test  * Add platform-specific folder to top-level Resources folder   * HarnessTemplate   ** Add platform-specific resources folder  ** Need to enable the platform in the tiapp.xml  * test specs  ** add new platform to the "platforms" object in test spec optimizer.js
Answer: 9841.0

User story: "Need to make sure that all unit tests run correctly against BB. This includes all test apps as well. Unimplemented APIs in BB should gracefully fail and report as much to the user."
Answer: 120990.0

User story: Source maps are currently placed in "PROJECT_DIR/.map". They should instead be placed in the "build/map".
Answer: 42.0

User story: "The source maps generated by Alloy currently go to the .map folder. They should probably be placed in the build folder somewhere. Perhaps just in build/.map, or something specific to alloy, like build/alloy/.map since other projects may also introduce source maps. "
Answer: 1497.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "The models/login test app is meant to only run on iOS as this time. I need to enforce this with platform-specific views and controllers."
Answer: 5.0

User story: """jake app:run"" does a full rebuild of every test app when executed. It would be nice, now that Alloy supports ""app:quickrun"" builds with ios and fastdev with android, if we could also support quick builds with jake. For deep testing, it would be a good idea to do full rebuilds, but for quick testing, this will increase the speed of the development workflow."
Answer: 117.0

User story: "Remove all {{/\*\*}} occurrences in the oauth.js builtin, replacing them with {{/\*}} so that documentation is not generated."
Answer: 85.0

User story: Just like:    {code}  <TableView dataCollection="place">    <TableViewRow title="{title}" />  </TableView>  {code}    I want to be able to do:    {code}  <View id="mapview" ns="Ti.Map" animate="true" regionFit="true" userLocation="true" dataCollection="place">      <Annotation latitude="{latitude}" longitude="{longitude}" title="{title}" />  </View>  {code}
Answer: 704561.0

User story: The old "sql" adapter will be replaced with the "sql_new" adapter. The "sql_new" adapter was introduced in Alloy 0.3.5 due to the massive amount of changes and improvements, some of which were not 100% backwards compatible. The linked related tickets show all these changes. The replacement should be made and tested against all test apps.
Answer: 1306.0

User story: "The current {{alloy run}} is simply a shell for {{titanium build}}, see details in ALOY-330. With Alloy 1.1.0, this deprecated command should be removed entirely in favor of actually executing {{titanium build}}."
Answer: 73139.0

User story: "The expr() syntax in TSS files should be removed to avoid having logic directly in the styles. Developers will still have all the power that expr() provided by using the Alloy namespaces within their styles. My comment on Github regarding the removal of expr() covers how to do this in detail:    https://github.com/appcelerator/alloy/commit/e9fdc93c9760a1590c0abd0136662c11dc678066#commitcomment-2401085    The expr() syntax will not be present in the new TSS grammar being generated for ticket ALOY-389."
Answer: 1.0

User story: "h2. update (1/21/2013)    {{jake app:run}} now uses the new CLI. Below shows a full list of the possible options, all of which are optional. It will build for iphone sim by default:    {code}  jake app:run dir=ui/splitwindow platform=ios tiversion=3.0.0.GA simtype=ipad  {code}    h2. original    The {{jake app:run}} command will use the old titanium.py script. We should convert it to use the new CLI to move forward with it, and aid in testing."
Answer: 51134.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Test, and merge if appropriate, the PR found here: https://github.com/appcelerator/alloy/pull/90    This PR includes a couple improvements for the buttongrid widget:  * - Add ability to specify the asset directory, default is '/images/'  * - Add a global click callback which can be overridden at the individual button level.  * - Allow for passthrough of all valid button properties for creation."
Answer: 526.0

User story: The samples could then be shown in the Studio. Ideally each sample will have its own git repository, e.g. the Titanium samples are in the respective git://github.com/appcelerator-developer-relations/Sample.<name>.git repos.    The apps will be housed in the "templates" folder at the top-level of the alloy folder. The apps will be organized by named folders and contain only the contents of the "app" directory, just as the templates. Alloy will also expose a new "alloy info" option to allot TiStudio to get a listing of sample apps and all important information about them:    {code}  alloy info samples  {code}     This will return a JSON listing of information just like the "alloy info templates" command
Answer: 103108.0

User story: "We should have a basic test app, simpler than the todo, which shows the 4 permutations of TableView Collection binding.    # inline rows with a singleton collection  # <Require> rows with a singleton collection  # inline rows with a instance collection  # <Require> rows with a instance collection    This will likely operate as a TabGroup driven app, each one of the scenarios represented in each tab  "
Answer: 5282.0

User story: "Currently only singleton collections are working for tableview binding. We need to enable instance collections to work as well through the markup tableview collection binding."
Answer: 33.0

User story: h2. update (1/29/2013)    A new adapter type was not created. Instead, a test app was created showing how you can use plain old Backbone models and collections and still leverage Alloy data binding. it can be found here: https://github.com/appcelerator/alloy/tree/master/test/apps/models/binding_no_persistence    h2. original    It is assumed that if you are using Alloy Models that you want to use local/remote persistence as well, as the only choices for adapter are sql, properties, and localStorage. We should make an adapter that abides by the normal Alloy Model conventions that has no persistence, an adapter that simply allows devs to take advantage of model-view binding.    The adapter type will likely be "*none*" and will be the default when an adapter is not specified.     Another consideration is just making plain old backbone models/collections work with Alloy's binding
Answer: 86490.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: Right now the generated code for making sure we have an instance of a singleton Collection (or Model) looks like this:    {code:javascript}  Alloy.Collections.todo || (Alloy.Collections.todo = Alloy.createCollection("todo"));  {code}    It would be nicer to have a function that returns an instance if we need one, or the already created instance if it exists. Basically, the line of code above shouldn't be generated every single time a <Collection> or <Model> is used in markup. This will help reduce the size of the code, and make it more readable.    {code:javascript}  Alloy.Collections.instance('todo');  Alloy.Models.instance('todo');  {code}
Answer: 49.0

User story: h2. update (1/23/2013)    ALOY-485, which depends on TIMOB-12399, is marked as related, but will not be completed for Alloy 1.0.0. This unfortunately leaves collection binding for views in only a seme-stable state for iOS. We may want to consider marking collection binding for views as "experimental" and note the issues in those tickets some where in our Alloy 1.0.0 migration notes. This hasn't changed from 0.3.x, but it hasn't been documented either.     Collection binding for tableviews, though, works as expected. This only affects collection binding on arbitrary views, as seen in the [models/journal test app|https://github.com/appcelerator/alloy/tree/master/test/apps/models/journal]    h2. update (1/21/2013)    All tickets relevant to further Alloy 1.0.0 changes that should be covered in a migration document will be linked as related tickets.    h2. description    We have the following Alloy namespace APIs marked as deprecated:    * - Alloy.getController()  * - Alloy.getModel()  * - Alloy.getCollection()   * - Alloy.getWidget()  * - Alloy.globals    We need to plan to remove these completely to reduce the size of the runtime file, as well as move developers to what will be the best practices for creating Alloy apps. Typically in TiSDK this process takes much longer, but in the case of Alloy which is still considered beta, I think its safe to move faster and notify developers that these APIs will be removed in Alloy 1.0.0. Warnings will state as much and developers can prepare to move over to the proper development methods.    h3. additional deprecations  * - We should also officially remove the deprecated *size* device query, which has been replaced with *formFactor*.  * - remove the datetime.js builtin, as it has been made obsolete by the moment.js builtin  
Answer: 86313.0

User story: "In 0.3.2 I added *Alloy.globals* for storing global variables and functions. In retrospect, this should probably be *Alloy.Globals*, making sure that namespaces start with a capital letter, like:    * Alloy.CFG  * Alloy.Models  * Alloy.Collections    For the time being, both will be left in Alloy, but *Alloy.globals* will be marked as deprecated. I will create another ticket which deals with deprecating this and some other obsolete Alloy items. "
Answer: 73.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "It makes more sense to organize standard properties for the Alloy namespace object within the runtime Alloy.js file, rather than initializing them in the app.js itself. For example, the app.js template:    {code:javascript}  /**   * Alloy for Titanium by Appcelerator   * This is generated code, DO NOT MODIFY - changes will be lost!   * Copyright (c) 2012 by Appcelerator, Inc.   */  var Alloy = require('alloy'),   _ = require('alloy/underscore')._;    Alloy.Collections = {};  Alloy.globals = {};  Alloy.CFG = require('alloy/CFG');  <%= alloyJs %>  Alloy.createController('index');  {code}    Ideally, it will look like this, with all code that was removed placed in the actual runtime Resources/alloy.js library:    {code:javascript}  /**   * Alloy for Titanium by Appcelerator   * This is generated code, DO NOT MODIFY - changes will be lost!   * Copyright (c) 2012 by Appcelerator, Inc.   */  var Alloy = require('alloy'),   _ = require('alloy/underscore')._;    <%= alloyJs %>  Alloy.createController('index');  {code}"
Answer: 1138.0

User story: "As it stands, all automatically generated variable names in Alloy get a standard prefix and then a counter as more variables are generated. In other words, the list will always look like this:    * __alloyId1  * __alloyId2  * __alloyId3  * __alloyId4  * __alloyId5  * and so on...    While this serves its purpose correctly, it makes it difficult in some cases to understand what is going on if a developer decides to inspect the generated code. They can figure it out, but it would be nicer if they could understand it a little more at a glance.     To help with this, when the deploy type is either *development* or *test*, I'd like to make the name a little more meaningful. Perhaps adding a part to the variable name that indicates what API it pertains to, or anything to really make it more applicable. In *production* we'll just squeeze these names down to something small and unique, but a more verbose name in *development* and *test* will prove useful.    Fortunately the auto generation of variable names has been abstracted out to a single function called *generateUniqueId()* in https://github.com/appcelerator/alloy/blob/master/Alloy/commands/compile/compilerUtils.js. We can add additional parameters to this function relatively easily and make this improvement gradually, starting with the most used or most cryptic generated code."
Answer: 148170.0

User story: We need to be able to use model-view binding on generic view components just as we do on TableViews in ALOY-104. This will allow views in Alloy do render a repeated series of UI components based on a Collection.    {code:xml}  <Collection src="myModel"/>  <View layout="horizontal" dataCollection="myModel">      <ImageView image="{image}"/>  </View>  {code}    We also need to determine if all Titanium views should be able to do this or if we should reserve this for the basic ones like Window, View, etc... 
Answer: 37738.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "The optimizer.js was disabled for a short time due to the linked issues. The optimizer.js has since become more stable and covers more of the platform conditional cases that it was meant to. We should re-enable the optimizer.js as part of the runtime JS file optimization process. It should be inserted in the flow of optimizations just before the final ast_squeeze() step. Extensive internal testing should be done to ensure that the optimizer operates as expected and causes no errors in valid JS.    This module will make optimizations at compile time to improve runtime performance. It will attempt to make any runtime platform conditionals into compile time ones, removing the runtime overhead. More performance enhancements to come."
Answer: 11901.0

User story: In alloy's early state, it's a good idea to keep the "master" branch as the current path of development for the next release. If a new feature is not going to be ready within the space of a single release, it should be developed in a new "alpha" branch. In the "alpha" branch new development can be a little more relaxed in terms of testing. Also, the development can take place over a longer period of time without impacting the "master". This will be useful for new features that will have a large impact on alloy like model-view binding and dynamic styling. The extra time this code remains in the "alpha" branch can be used to solicit feedback and help mold the beta or final state of the feature.
Answer: 13.0

User story: "The testing for the optimizer.js script is currently embedded in the code for the optimizer.js itself. We should pull this testing out of the optimizer.js file and instead group it with the rest of the unit testing for alloy. "
Answer: 752.0

User story: "The testing for the optimizer.js script is currently embedded in the code for the optimizer.js itself. We should pull this testing out of the optimizer.js file and instead group it with the rest of the unit testing for alloy. "
Answer: 357.0

User story: "This ticket is a placeholder for testing that will be performed after TIMOB-11752 is resolved. In short, globals are accessible in commonjs modules in iOS and Mobileweb, but not on Android. See TIMOB-11752 for the full details."
Answer: 230602.0

User story: "Would be good to have more insight into what are the most processor intensive sections of the alloy compile process. Will make it easier to focus efforts on speeding up that process. It may not seem critical now, but as the complexity of projects grows and the introduction of rapid deployment techniques (like TiShadow) are introduced, the compile time will more evident."
Answer: 35848.0