Dummy patches for testing - Gluster development work flow automation

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

Myself and Manikandan are working on automating the development work flow of GlusterFS.

A bug for this task has been created here: https://bugzilla.redhat.com/show_bug.cgi?id=1285179
Existing notes on the task: https://public.pad.fsfe.org/p/gluster-automated-bug-workflow

For testing the modifications made to rfc.sh, we want to send some dummy patches(as minimal as possible) to gerrit.
The patches will be abandoned as soon as it serves the purpose. We hope this is okay. Please let us know if otherwise.


Quick updates on the automation:

We are done with modifying rfc.sh to prompt developer for the status of the patch (last one for the particular bug or not) and making changes in commit message accordingly.
We are tweaking with the hooks currently running, testing of which would require us to have access to gerrit and bugzilla setups.
We will keep the status updated on the list.

Thanks,

Nandaja
IRC nick: gem on freenode and OFTC
http://gemiam.in
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-devel



[Index of Archives]     [Gluster Users]     [Ceph Users]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux