Re: [gentoo-project] Official rsync->git mirror & 'Git mirror' project announcement

[Alexey Lapitsky]

Hi Rich,

I'm sorry if I don't understand the cherry-picking workflow very well,
I'm not a gentoo dev myself.
Correct me if I'm wrong, but in my opinion it's very valuable to save
maintainer time and I don't see a lot of value in doing manual
cherry-picking to cvs (given that QA tests pass automatically and
there is no conflicts).

Here's a naive example how it might work:

1. A user creates a PR
2. travis-ci automatically runs QA tests: repoman full on the PR,
reports the result back
3. Github hook is emitted, a "system" does some processing: for
example, create a bug in bugzilla, notify the maintainer, comment on
the PR
4. The relevant maintainer checks the PR, comments: "looks fine, merging"
5. Github hook is emitted to "the system", which checks the PR
comments, does some sanity checks, merges commit back to cvs, rejects
the PR

"The system" might be a simple script which has opt-in membership for
the subsystems / maintainers who wants to use it.

Does it sound sane?


On Wed, Jan 28, 2015 at 4:58 PM, Rich Freeman <rich0@g.o> wrote:
> On Wed, Jan 28, 2015 at 10:51 AM, Alexey Lapitsky <lex.public@×××××.com> wrote:
>>
>>> Since the changes will be re-committed in CVS manually, we will end up updating the commit message anyway.
>>
>> It should be possible to automate this step as well. Is there a reason
>> why not to do that?
>>
>
> You're proposing auto-committing from the git mirror back into cvs?
> Or just a tool to allow devs to cherry-pick commits from git and stage
> them in cvs?  The first seems potentially fraught with peril.
>
> At what point does this basically turn into Gentoo forking itself out
> of frustration with the git migration?  :)
>
> --
> Rich
>