Hi Jo, Thanks for all this information. I'll propagate it to the forum, since many people are asking.
> On Jan 28, 2017, at 9:35 AM, Jo-Philipp Wich <j...@mein.io> wrote: > > Hi Rich, > >> 1) When I got to downloads.lede-project.org, I see the following >> directory structure: [...] I do NOT see any targets under the >> /releases directory. Why? > > I intentionally hid the "17.01-SNAPSHOTS" directory because it is not a > fixed (as in non-moving) build, it merely reflects the build output of > the current branch HEAD. > >> 2) Why doesn't the /releases directory mirror the /snapshots >> directory? > > Because releases are structured slightly differently. I understand now. >> 3) I have discovered that the release images are available >> /releases/17.01-SNAPSHOT/ Is this what we should document? > > No, please do not document that particular directory, see below. OK. I have a recommendation re: naming & directories. Perhaps we should create /releases/17.01.0-rc1/ now. Its sole contents (today) could be a README text file with text like this: ===== /releases/17.01.0-rc1/README.txt ===== 2017-01-dd There are no LEDE 17.01.0-rc1 build images at this time. However, we are building snapshots for testing in preparation for the 17.01.0-rc1 build. Those snapshots are saved in the hidden /releases/17.01-SNAPSHOT/ directory. Once we create the LEDE 17.01.0-rc1 build, this directory will contain its image files and packages. ===== Once the 17.01.0-rc1 files have been created, the README.txt file could be updated to say: ===== /releases/17.01.0-rc1/README.txt ===== 2017-01-dd The files in this directory are the LEDE 17.01.0-rc1 snapshots. They are release candidates for the LEDE 17.01.0 build, and will never be updated. However, we are building snapshots for testing in preparation for the 17.01.0-rc2 build. Those snapshots are saved in the hidden directory /releases/17.01-SNAPSHOT/ ===== >> 4) It's really confusing to talk about (and document) the release >> candidates and the daily "trunk" builds. Currently, image file names >> for stable build candidates contain the word "snapshot", while trunk >> builds (in the /snapshots directory) do not: > > Those images are not stable build candidates but merely release branch > snapshots, thats why they contain the word "snapshot" and also why > they're currently hidden from the toplevel directory. > > I instructed the buildbot to produce tagged rc1 builds today, those will > be true, fixed release candidate images which do not move. How soon do you expect the /releases/17.01.0-rc1/ images to be available? > Once built, those images will appear in /releases/17.01.0-rc1/ and > remain unchanged. In addition to that, there will be a corresponding > "v17.01.0-rc1" tag in the repository which can be used to reproduce this > particular images. > > The /releases/17.01.[0-9]* directories (once existing) which are not > hidden are the ones that should be documented and referred to as fixed > builds. > >> 5) What is the naming scheme for the final 17.01 image URLs? > > The RCs will be: > > /releases/17.01.0-rc[0-9]*/targets/$target/$subtarget/lede-17.01.0-rc[0-9]*-r####-XXXXXXX-$target-$subtarget-*.bin > > The finals will be: > > /releases/17.01.0/targets/$target/$subtarget/lede-17.01.0-r####-XXXXXXX-$target-$subtarget-*.bin > >> 6) When we release a new version (say, 17.06), what will those URLs >> be? > > The RCs will be: > > /releases/17.06.0-rc[0-9]*/targets/$target/$subtarget/lede-17.06.0-rc[0-9]*-r####-XXXXXXX-$target-$subtarget-*.bin > > The finals will be: > > /releases/17.06.0/targets/$target/$subtarget/lede-17.06.0-r####-XXXXXXX-$target-$subtarget-*.bin This is a good, and easily understood/described plan. Thanks! Rich >> We'll adjust the documentation to match the results of this >> discussion. Thanks. > > I appreciate your efforts on this, thank you :) > > ~ Jo > > _______________________________________________ > Lede-dev mailing list > Lede-dev@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/lede-dev _______________________________________________ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
