Wouldn't it be easier just to download the source RPMs that are archived with the particularly release? http://download.tizen.org/releases/milestone/tizen/ivi/tizen_20130829.9/repos/ivi/source/ Rather than trying to rebuild stuff from the git repos that have already been updated with new patches before we even finish building the release much less verifying its good enough to actually release.
Regards Joel From: [email protected] [mailto:[email protected]] On Behalf Of Hanchett, Paul Sent: Thursday, September 12, 2013 11:00 AM To: [email protected] Subject: [Tizen General] Why not use tags to mark releases rather than the manifest file? Why not use tags to mark a particular release, rather than the object ID in the manifest file? I see several advantages: * You get a single value that can be handed to gbs/obs to pull all of the packages as of a particular point in time; new commits have no impact on the git tag (unlike the branches we use now.) In fact, you might not even need manifest files........ * Now, it becomes dead easy to *see* in each repository the version that was actually released. Placing tags for other significant events makes those visible in every repository. I'm sure there are other advantages. Is there a down side? (I'm relatively new to git...) Thanks, Paul Hanchett ------------------- Infotainment Engineer MSX on behalf of Jaguar Land Rover One World Trade Center, 121 Southwest Salmon Street, 11th Floor, Portland, Oregon, 97204 Email: [email protected]<mailto:[email protected]> ------------------- Business Details: Jaguar Land Rover Limited Registered Office: Abbey Road, Whitley, Coventry CV3 4LF Registered in England No: 1672070
_______________________________________________ General mailing list [email protected] https://lists.tizen.org/listinfo/general
