I find that my workflow for pretty much all development and QA work centers around Bugzilla now.  Even when git-bz fails to work as intended, I can still wget the patches and test them.

What about looking into a means of auto-generating patches to the patches list when new "Patch" type attachments are added to Bugzilla?  This would save everyone a step, and keep the incoming patches synced with the patches on bugs.koha-community.org.

For course, as MJ points out, we'd need time to implement such a thing.


-Ian

On Mon, Oct 10, 2011 at 11:05 AM, MJ Ray <mjr@phonecoop.coop> wrote:
> * Paul Poulain (paul.poulain@biblibre.com) wrote:
> > What would be absolutly WONDERFUL would be to add a parameter to update
> > the patch status.
> > Something like :
> > "git bz attach -status signed-off 4321 HEAD "
> > Plus fixing the bug that makes attaching more than one patch at a time
> > impossible.

The right way to do that is probably to let git bz attach take
arbitrary form input names and values from the bugzilla update form,
so the above example would be:
 git bz attach -cf_patch_status 'Signed Off' 4321 HEAD

Chris Cormack <chrisc@catalyst.net.nz>
> First i'd like to add a -3 switch so that the apply will use a 3way
> merge. At the moment if it fails you have to try that manually.

That sounds like a good but simple improvement, if only we had more
time!

Regards,
--
MJ Ray (slef), member of www.software.coop, a for-more-than-profit co-op.
Webmaster, Debian Developer, Past Koha RM, statistician, former lecturer.
In My Opinion Only: see http://mjr.towers.org.uk/email.html
Available for hire for various work through http://www.software.coop/



--
Ian Walls
Lead Development Specialist
ByWater Solutions
Phone # (888) 900-8944
http://bywatersolutions.com
ian.walls@bywatersolutions.com
Twitter: @sekjal