| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Here is the rationale for tagging all repositories:
- In Replicant 6.0 we now have mirrored all the repositories we use, so we
can now tag them all.
- For libsamsung-ipc, as the tag as replicant-<version> in its name, it
cannot conflict with future tags for other distributions, or future
Replicant versions.
- Even if libsamsung-ipc is meant to be shared across different
distributions, having a record of which Replicant versions use
which libsamsung-ipc versions in libsamsung-ipc is very important as
libsamsung-ipc is heavily tested with Replicant and users reporting bugs
in Replicant typically know the Replicant version not the exact
libsamsung-ipc commit used.
In addition, we need to tag the manifest otherwise we have an error like
that:
$ ./release.sh replicant-6.0 replicant-6.0-0004-rc2 all
Releasing metadata
fatal: ambiguous argument 'replicant-6.0-0004-rc2':
unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
And it is better to have it done automatically, in the same way than for
the other repositories.
To do that, we will document the release procedure in a subsequent commit
to make sure that no step is missed.
It will make sure that .repo/manifests has the required tag before being
used by release.sh by:
- Making sure that the people doing the release don't forget to add patches
in the manifest/ directory. Patches are needed to change the revision
to the release tag.
- Making sure that the tag pushed by releasetag.sh.
- Making sure that people doing the release will re-download the source for
building, so the tag will be in .repo/manifests.
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
