Bug 11613

Summary:	[Help] why and when the release files may update?
Product:	[Infrastructure] Release Process	Reporter:	Yunming Shi <emincemnt>
Component:	Release Process	Assignee:	Joshua Lock <joshuagloe>
Status:	RESOLVED NOTABUG	QA Contact:
Severity:	normal
Priority:	Medium+
Version:	unspecified
Target Milestone:	2.4 M2
Hardware:	x86
OS:	Multiple
Whiteboard:
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	No (bug/feature does not impact docs)

Description Yunming Shi 2017-06-06 06:48:34 UTC

Hi, I've been using yocto 1.5 since 2015, I downloaded all the release files from the URL:http://downloads.yoctoproject.org/releases/yocto/yocto-1.5/sources/.
But recently I discovered many released files were updated. Such as:
git2_git.yoctoproject.org.prelink-cross.git.tar.gz 2016-Aug-18 22:32
git2_git.yoctoproject.org.prelink-cross.git.tar.gz.done 2015-Jan-27 01:52
git2_git.yoctoproject.org.yocto-kernel-tools.git.tar.gz	2017-Apr-28 11:07
git2_git.yoctoproject.org.yocto-kernel-tools.git.tar.gz.done 2015-Feb-11 18:14
The original files's time stamp is 2016 or 2017, and the *.done file is still 2015.

Why these files were updated? 
Are there any update log or release note can explain the changes?

Comment 1 Joshua Lock 2017-07-03 15:10:10 UTC

The sources directory for a release isn't fixed, rather it's a symbolic link to the shared sources directory used by the Yocto Autobuilder for all builds. Therefore the revision control mirror tarballs will be updated when future recipes bump SRCREV.

The various revision control fetching mechanisms of the build system ensure that an older release which fetches an updated mirror tarball (including revisions beyond those used by the release) will still only use the specified release revision.