I want to update yocto upper than 1.8.
But, I can't find way of update yocto.
Let me know site or search keyword.
Thanks.
The current latest version of Yocto is 2.4-Rocko released in October 2017.
Yocto Project usually updates every 6 months.
Downloads: https://www.yoctoproject.org/downloads
Documentation: https://www.yoctoproject.org/documentation
Git: https://git.yoctoproject.org/cgit/cgit.cgi/poky/
Related
According to the TFS 2018 Update 2 Release Notes, the partially downloading artifacts feature was added. This is further backed up on the uservoice item.
However, I cannot seem to find where to configure this option within the release template editor.
They provide a screenshot:
However, I don't have anything like that:
I am confident I am on the tfs 2018 Update 2 release as this is the version specified in the TFS Admin Console:
The release notes are wrong, check this feedback: TFS 2018 Update 2 RC - Select artifacts to download not available
Partial downloading of artifacts feature isn't available in TFS 2018
Update2 RC. Since this feature has dependency on couple of other
features and those features are not enabled in TFS 2018 Update2, we
chose to not to roll it out. Having said that feature showing up in
docs is a bug - we will remove that section from docs.
I have validated what you're saying. My best guess is that Microsoft made a mistake. It's already a feature in VSTS, so it looks like the release notes are wrong.
I want to update a huge Ruby on Rails v2.3.18 application to Rails v4.2.4 (latest).
After doing some research, I've came up with:
After Rails 2.3.18 (March 18, 2013), a total of 195 versions have been released until Rails 4.2.4 (August 24, 2015)
in which 92 are stable releases
and 2 major releases
775 files changed
909 commits
Our application runs Ruby on Rails 2.3.18 on Ruby 2.1.5.
Ruby should also be updated from this version to 2.2.x ?
Are there any individuals who achieved or tried this "leap of faith" and succeeded ?
Where should I start from in order to achieve my goal?
What is the basic flow of updating any Ruby on Rails application?
I have also been pondering this issue with some 5 year old projects - do I keep using rails 2.3.18 LTS https://railslts.com/ , or migrate to rails 4.2, knowing that I will then need to look at annually/biannually updating the rails version. I suspect I will be more succesful in doing a selective replacement as new functionality is developed.
Anyway, the information I found seems to indicate it is a long step by step process:
This post may be of help - https://groups.google.com/d/msg/rubyonrails-talk/y0q1fc8N_GU/H2xOsy2mYpwJ
In it Rob Biedenharn suggests
• update to rails-2.3.18
There's really no reason not to and PLENTY of good reasons that you should have done this already.
2.3.9 (2010-09-04) was the version that first gave deprecation warnings for the upgrade to rails-3.0
2.3.18 (2013-03-18) was the last releast in the 2.3 line and contains fixes for at least 10 vulnerabilities (some of them quite serious!)
• get all your tests to pass (if you don't have tests, you'd better have faith)
• address all the deprecation warnings
• don't upgrade ruby yet
https://developer.uservoice.com/blog/2012/03/04/how-to-upgrade-a-rails-2-3-app-to-ruby-1-9-3/
But you might have to upgrade to ruby-1.8.7 as rails-3.0 doesn't officially support 1.8.6)
Oh, and I took a look at http://edgeguides.rubyonrails.org/upgrading_ruby_on_rails.html as suggested by Jason Fleetwood-Boldt and that has a MUCH more detailed walk though the upgrade process from 3.0 to 4.1. But if you don't have time to go and look at that yourself, then perhaps I've given you enough with which to weigh the upgrade v. rewrite paths.
• upgrade to rails-3.0.0 (perhaps even directly to rails-3.0.20)
• get all your tests to pass
• upgrade to ruby-1.9.2 (or perhaps even ruby-1.9.3)
• get all your tests to pass
• upgrade to rails-3.1.12 (last of the rails-3.1 line)
This might not strictly be required, but 3.1 introduced the Asset Pipeline and also made jQuery the default JavaScript framework.
If you have much use of Prototype or Scriptaculous in your application, it would probably be a good idea to convert that to jQuery (and get https://github.com/rails/jquery-ujs)
• get all your tests to pass
• upgrade to rails-3.2.19
• get all your tests to pass
• upgrade to ruby-2.1.2 (there's probably no reason to just use 2.0 at this point)
• get all your tests to pass
• upgrade to rails-4.0.8
• get all your tests to pass
• upgrade to rails-4.1.4
• cope with the new secrets.yml file
• get all your tests to pass
• take a vacation
Seriously, there's a lot to do if you really want to go the upgrade route. I haven't even mentioned any of the issues that you're almost certain to encounter with gems that cease to function with newer versions of Rails or even newer Rubies. I'd recommend that you very seriously consider "refreshing" the application as a simpler way to bring the application onto a current, supported RoR stack.
Two days ago the released version of the google maps API was updated to 3.19
Version 3.18 broke some things in our application so we had been explicitly asking for 3.17 until it was deprecated. We updated the application to work with 3.19 and ask for the latest release version, instead of explicitly specifying the version.
Yesterday it went back to 3.18.20, which again broke our application.
We have since updated to explicitly request 3.19, but I'm wondering why the default version is now returning 3.18 instead of the current release version?
Thanks
If you don't specify the version number the version you get will vary according to the documentation on versioning:
You can indicate which version of the API to load within your application by specifying it using the v parameter of the Maps Javascript API bootstrap request. Three options are supported:
The experimental version, specified with v=3.exp.
The release version, specified with v=3
The frozen version, specified with v=3.0
If you do not explicitly specify a version, you will receive the experimental version by default. Google Maps API for Work customers who specify a client ID will receive the release version by default.
If you specify a specific version (i.e. v=3.18), you will get that version while it is available. Once it is retired, you will get the frozen version.
I experienced this same issue, and submitted a bug to Google. See their answer here:
https://code.google.com/p/gmaps-api-issues/issues/detail?id=7694
To reiterate their answer, there were apparently some issues with 3.19, so they reverted their experimental/release/frozen versions. I've chosen to directly use 3.19, as it doesn't seem to introduce any issues for my purposes.
I've been iterating versions of my application trough beta and install4j auto-updater was updating successfully trough versions (2.1 -> 3.0b0 -> 3.0b1 -> 3.0b2). Now I've published version 3.0 and auto-updater is refusing to recognize the new version.
Now, I know that there is an option that allows you to customize update scheme but it's too late now since I didn't know that when I was publishing older versions.
I've played around with it and it updates to 4.0 and 3.0b3 but fails to recognize 3.0, 3.1.
So, is there a way to force auto updater to update by manipulating the new update.xml file?
EDIT: I have version 4.2.8 of install4j installed.
Unfortunately not. install4j 5 will correctly update from 3.0b2 to 3.0, but in install4j 4 you would have to modify the updater logic, so you would first have to release a 3.0b4 to do that.
I have updated to a new bios version which is probably corrupt. Now I can't fall back to an older bios version because the build date always has to be newer than the currently installed bios.
Is there a safe way to manipulate the build date? In windows it is called "Date modified"
Okay never mind I just figured it out by myself. I just had to re safe it.