Re: [gentoo-dev] Gentoo git workflows and the stabilization/keywording process

[Ulrich Mueller]

>>>>> On Sun, 21 Sep 2014, hasufell  wrote:

> https://wiki.gentoo.org/wiki/Gentoo_git_workflow

> But so far, not many people have been particularly interested in the
> details of these things. I'm also not sure if the ML is the right
> way to figure out these details.

Where else should this be discussed then? Discussion page of the wiki
page?

| commit policy
| • atomic commits (one logical change)

A version bump plus cleaning up older ebuilds will be considered one
logical change, I suppose?

| • commits may span across multiple ebuilds/directories if it's one
|   logical change 
| • every commit on the left-most line of the history (that is, all
|   the commits following the first parent of each commit) must be gpg
|   signed by a gentoo dev 
| • repoman must be run from all related ebuild directories (or
|   related category directories or top-level directory) on the tip of
|   the local master branch (as in: right before you push and also
|   after resolving push-conflicts)

Have you tested if running repoman in the top-level directory is
realistic as part of the workflow?

| commit message format
| • all lines max 70-75 chars
| • first line brief explanation
| • second line always empty
| • optional detailed multiline explanation must start at the third
|   line
| • for commits that affect only a single package, prepend
|   "CATEGORY/PN: " to the first line

In some cases of long package names, this may be in conflict with the
first item. "dev-python/rax-default-network-flags-python-novaclient-ext: "
as a prefix doesn't leave much space for an explanation. ;)

| • for commits that affect only a single package, but also modify
|   eclasses/profiles/licenses as part of a logical change, also
|   prepend "CATEGORY/PN: " to the first line
| • for commits that affect only the profile directory, prepend
|   "profiles: " to the first line
| • for commits that affect only the eclass directory, prepend
|   "ECLASSNAME.eclass: " to the first line

Maybe just "eclass: " would be slightly more systematic? (Because for
all others it is a directory.)

| • for commits that affect only licenses directory, prepend
|   "licenses: " to the first line

Same for commits that affect licenses and profiles?

| • for commits that affect only metadata directory, prepend
|   "metadata: " to the first line
| • mass commits that affect a whole category (or large parts of it)
|   may prepend "CATEGORY: " to the first line

All in all, this looks sane to me. Is it planned to enforce this
policy by repoman?

Ulrich