Tails

#3 Updated by intrigeri 2018-11-29 16:25:03

Forgot to say: once happy, please merge into master → stable → devel.

#4 Updated by Anonymous 2018-12-04 08:53:45

Hi kibi, this currently blocks some of my work. Could you please review and merge this asap? thanks!

#6 Updated by CyrilBrulebois 2018-12-04 13:12:18

Pushed trivial fixes (that can be squashed together) in the pu/doc/16171-generate-idf-v2 branch, I think the git add issue can be solved with a wildcard (latest.*) even if we lose some bits of information.

Another thing that might be nice to have is a more uniform “image description format”; that’s not been done across the whole site at the moment:

$ git grep -l 'ISO description file'
wiki/src/contribute/build/reproducible.mdwn
wiki/src/contribute/design/verification_extension.mdwn
wiki/src/contribute/release_process.mdwn

Again, nothing critical.

In the meanwhile, I’ve merged and pushed the branch into master, as it seemed good enough to merge, and u needed it to get other things going.

I haven’t merged into other branches yet, as it seems it would be slightly better to get the details mentioned above fixed (or dismissed as unimportant) before doing so. Feel free to correct me, still learning the ropes.

#8 Updated by intrigeri 2018-12-05 10:00:57

> Pushed trivial fixes (that can be squashed together) in the pu/doc/16171-generate-idf-v2 branch

Great, thanks! Merged into master.

>, I think the git add issue can be solved with a wildcard (latest.*) even if we lose some bits of information.

ACK, will do.

> Another thing that might be nice to have is a more uniform “image description format”; that’s not been done across the whole site at the moment:

Fully agreed but IMO that should be covered by Bug #15998: given that work has not been done yet, new terminology is not set in stone nor applied consistently, so I had to guess and improvise a bit here. IIRC I’ve done some of this work on my branch for Bug #15999 anyway. Keep in mind that this branch is a transitional one merely meant to ensure we generate IDF v2 during our next releases. The full blown thing is Bug #15998 and Bug #15999 :)

> I haven’t merged into other branches yet, as it seems it would be slightly better to get the details mentioned above fixed (or dismissed as unimportant) before doing so.

Well, merging master into the release branch is part of our release process and the RM is supposed to follow the version of the doc that’s on the release branch, so:

• Either the RM follows the version that’s in stable before merging master, and then they won’t generate IDF v2 and we have a serious problem.
• Or the RM follows the version that’ll be in stable after they merge master into it, and then they’ll be affected by those small problems.

So I’m not sure it makes much sense to differentiate “merge this into master” from “merge this into stable”. In any case, no big deal at all: I’m confident this work will reach the point when you’re happy to merge it everywhere by the end of the week :)

#9 Updated by intrigeri 2018-12-05 10:06:39

>>, I think the git add issue can be solved with a wildcard (latest.*) even if we lose some bits of information.

> ACK, will do.

Done, tested with your reproducer, works fine. Once happy, please merge into master → stable → devel.