Short version: Nope...\u00a0\u00a0 \ud83d\ude09<\/p>\n
Long Version:<\/p>\n
I see this pop up frequently in the bug tracker and slack where someone is complaining about a issue; then we all find out it is a issue in the This is not actually the The In the meantime if you decide to try Please if you don't need<\/strong> to upgrade to However I would ask that if a bug you reported is fixed on To upgrade you do <\/p>\n","protected":false},"excerpt":{"rendered":" Short version: Nope...\u00a0\u00a0 \ud83d\ude09 Long Version: I see this pop up frequently in the bug tracker and slack where someone is complaining about a issue; then we all find out it is a issue in the @next version.\u00a0\u00a0\u00a0 Unfortunately Telerik really did everyone a huge disservice when they named it @next. This is not actually… Continue reading NativeScript: @Next- should I use it?<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_crdt_document":"","footnotes":""},"categories":[15,39],"tags":[105,104,16],"class_list":["post-528","post","type-post","status-publish","format-standard","hentry","category-nativescript","category-tips","tag-latest","tag-next","tag-nativescript","entry"],"_links":{"self":[{"href":"http:\/\/fluentreports.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/528","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/fluentreports.com\/blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/fluentreports.com\/blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/fluentreports.com\/blog\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/fluentreports.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=528"}],"version-history":[{"count":1,"href":"http:\/\/fluentreports.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/528\/revisions"}],"predecessor-version":[{"id":529,"href":"http:\/\/fluentreports.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/528\/revisions\/529"}],"wp:attachment":[{"href":"http:\/\/fluentreports.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=528"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/fluentreports.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=528"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/fluentreports.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=528"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}@next<\/code> version.\u00a0\u00a0\u00a0 Unfortunately Telerik really did everyone a huge disservice when they named it @next<\/code>.<\/p>\nnext<\/code> version of that specific repo\/codebase.\u00a0\u00a0\u00a0\u00a0 What, you say???\u00a0 But it is named next<\/code>. \u00a0 Yes, I'm sorry to say it is totally a mis-named tag. \u00a0 None of the repos have an actualNEXT<\/code> branch.<\/p>\n@next<\/code> tag is actually tied to the MASTER<\/code> branch.\u00a0\u00a0\u00a0 And Master<\/code> is not a RELEASE<\/strong> branch in NativeScript. \u00a0\u00a0 Master is used for testing, and validating things.\u00a0 Once they have been validated and the feature(s), or fixes approved;\u00a0 then that single item will be tracked and eventually moved into the Release<\/code> branch before the real next upgrade release.<\/p>\n@next<\/code>, you will have many features\/bugs that are still in testing or transition that might not even be 100% complete or working properly.\u00a0\u00a0\u00a0\u00a0 Now the Telerik devs have been trying really hard to keep the Master branch in a usable state (Kudos for the guys putting \"DO NOT MERGE\" on really major pull requests that are still being developed).\u00a0\u00a0 But even with them being careful; Master is still a DEVELOPMENT<\/strong> branch, so just like my own DEVELOPMENT<\/strong> branches, thing will slip through. \u00a0 Or a design change will occur; where we decide to refactor something and then the current \"master\" is broken in some weird way that we didn't anticipate.\u00a0\u00a0 In addition there will be many features\/bugs that are present on Master that will never be in Release in that form. \u00a0\u00a0 So, @next<\/code> != release<\/code> or really even release quality.<\/p>\n@next<\/code>; don't do it.\u00a0 Not only will you stay saner; you won't be wasting peoples time with issues that are frequently meaningless.\u00a0\u00a0 @Next<\/code> is really so that you can test if a bug is fixed; but be very leary of using it for ANY other reason, the rest of the non-release changes in @next<\/code> will probably bite you...<\/p>\n@next<\/code>; please upgrade temporarily to verify the bug is fixed, and report back to the team.\u00a0\u00a0 This is helpful for them to know they squashed your bug as you see it.\u00a0\u00a0 But once you are done,testing; I would highly recommend you go back to the @latest<\/code> tag.\u00a0\u00a0 \ud83d\ude09<\/p>\nnpm i tns-core-modules@next<\/code>\u00a0 (Example sake; we are assuming it is the core you are upgrading, but all the repos have a @next).\u00a0\u00a0 Then a tns platform clean android<\/code> or ios<\/code>.\u00a0 Then re-build and run the app.\u00a0\u00a0\u00a0 When you are done testing, change the @next<\/code> to @latest<\/code>, and you will get the latest RELEASE<\/code> version available for that repo.<\/p>\n