libtuf.py: Staged metadata directory names with user-set suffixes

[vladimir-v-diaz]

libtuf.py supports staged metadata directories so that repository maintainers may work on the next release, or multiple, without affecting the "live" repository's metadata. The new repository tool currently fixes the staged metadata directory to "metadata.staged", however, any suffix should be allowed and set by the repository maintainer(s) (e.g., "metadata.new_release", "metadata.next", etc.)

libtuf.py should allow user-set suffixes of staged metadata directories.

[JustinCappos]

This might be more complicated. The version number needs to be
incremented. What if two groups are trying to get signatures for a
partial write simultaneously?

On Sat, Nov 23, 2013 at 6:52 PM, Vladimir Diaz notifications@github.comwrote:

libtuf.py supports staged metadata directories so that repository
maintainers may work on the next release, or multiple, without affecting
the "live" repository's metadata. The new repository tool currently fixes
the staged metadata directory to "metadata.staged", however, any suffix
should be allowed and set by the repository maintainer(s) (e.g.,
"metadata.new_release", "metadata.next", etc.)

libtuf.py should allow user-set suffixes of staged metadata directories.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/145
.

[vladimir-v-diaz]

If both maintainers are only incrementing the version number, that means the resulting metadata will be identical. That is, both metadata updates are treated as a write_partial() and their respective version numbers automatically incremented. In that case, both signatures may be merged.

If you are instead asking about simultaneous access to the repository:
We have mentioned locked files and directories. Repository maintainers may also be restricted to specific staged metadata. Santiago and I will come up with a precise proposal in the near future that we can then review.

[JustinCappos]

If both maintainers are only incrementing the version number, that means
the resulting metadata will be identical. That is, both metadata updates
are treated as a write_partial() and their respective version numbers
automatically incremented. In that case, both signatures may be merged.

Only if they are writing the same content. Otherwise they will each have
version number n+1 which will conflict.

If you are instead asking about simultaneous access to the repository:
We have mentioned locked files and directories. Repository maintainers may
also be restricted to specific staged metadata. Santiago and I will come up
with a precise proposal in the near future that we can then review.

Okay, sounds good.

[trishankatdatadog]

Closing because stale