I have made some changes in the last couple of days what IVI publishes where on download.tizen.org.
You may be asking, "Dear God, what has she done now?" ;) Here's what I have done…. We now have two sets of images on download.tizen.org. One set is for Tizen:IVI. The other is for Tizen:IVI:Release. This means that snapshots for Tizen:IVI, which continues to move forward during code freeze, now has images available. We also have snapshots for Tizen:IVI:Release. This is very cool. Here's why… Old Model - Images were generated out of the Tizen:IVI OBS project - When we were in code freeze, I would switch images over to be generated from Tizen:IVI:Release instead. - When SRs came in, we would accept them as usual for Tizen:IVI, but cherry-pick for Tizen:IVI:Release. - This meant that people submitting changes that were not intended specifically for Release and not accepted there, did not have a production image to test and develop against. Not so cool. - It also meant that other teams, like the security team, were left "high and dry" without a "bleeding edge" Tizen 3.0 image to use for their work. Also not so cool. - When code freeze was over, I would switch the images back to the Tizen:IVI project. The New Model - Images are generated for both OBS projects. - We still cherry-pick changes for Release and use "normal" acceptance process for Tizen:IVI - People who need "bleeding edge" can use Tizen:IVI images. They are happy. This is cool. - People needing the release images are still happy. This is also cool. - There is no guessing which repos were using in the images. Is this a release repo image or is this a "normal" one. Someone just looking at the download.tizen.org/releases/daily/tizen/ivi images and repos could not know readily. Now they can. What it Looks Like: There are now two subdirectories under download.tizen.org/snapshots/ivi. They are ivi and ivi-release. http://download.tizen.org/snapshots/tizen/ivi/ivi<http://download.tizen.org/snapshots/tizen/ivi/ivi/> http://download.tizen.org/snapshots/tizen/ivi/ivi-release<http://download.tizen.org/snapshots/tizen/ivi/ivi-release/> Pretty obvious where the release images are, no? Each subdirectory contains ONLY the images that are pertinent to the respective OBS project. It looks like this: download.tizen.org/snapshots/tizen/ivi/ivi/latest/images: ivi-efi-i586 ivi-mbr-i586 ivi-mbr-i586-emul ivi-min-efi-i586 ivi-min-mbr-i586 download.tizen.org/snapshots/tizen/ivi/ivi/latest/images: ivi-release-efi-i586 ivi-release-mbr-i586 I have used snapshots as an example here, but the directory structure is also like this for http://download.tizen.org/releases/daily/tizen/ivi/ as well. There is a bit of a gap here since the ivi subdirectory is currently empty. It looks a little weird, and feels wrong somehow. So I am going to copy a snapshot over for Tizen:IVI images each day so we have something there for people to work with. A sort of "unofficial" daily release, if you will. Release activities keep us busy, so I have no plans to smoke test or do official daily releases for Tizen:IVI during code freeze. We (RE) will keep our focus on Tizen:IVI:Release images. Obviously we aren't going to QA non-release images during code freeze, either. That is the gist of the changes. I hope this proves useful to many people. There have been enough requests for having Tizen:IVI images available during code freeze, it made sense to start doing this. Please let me know if you have questions or comments. Thanks, Tracy _______________________________________________ IVI mailing list [email protected] https://lists.tizen.org/listinfo/ivi
