[Koha-devel] Packing needs - status to add to bugzilla and the dashboard?

[Katrin Fischer]

Hi,

I think I'd add some steps before 1. to the suggested workflow: we
should check before any patches are pushed if the dependencies
introduced are absolutely needed and can be packaged, following the
guidelines that Galen pointed out.

I'd also agree that the load of packaging should be shared.

About bugzilla: I have been using the keyword "dependency" on any bug I
spot that adds a new one. I have created and shared a search
"NewDependency" based on it:
https://bugs.koha-community.org/bugzilla3/buglist.cgi?cmdtype=dorem&list_id=157609&namedcmd=NewDependency&remaction=run&sharer_id=13

Hope this helps!

Katrin

Am 08.03.2016 um 18:30 schrieb Chris Cormack:
> 
> 
> On 9 March 2016 6:25:18 am NZDT, Brendan Gallagher <info at bywatersolutions.com> wrote:
>> Hello All -
>>
>> I'd like to have a chance to talk about the packing work flow at the
>> next
>> developers meeting or even the general meeting.
>>
>> My thoughts are that we need a status in Bugzilla that says something
>> like
>> "Needs package created" or something.  Also add a little spot on the
>> dashboard under the Bugs Statuses which has a canned search for that
>> queue.
>>
>> I imagine the workflow being something like...
>>
>> 1. RM pushes code to master
>> 2. RM changes status to "needs package created"
>> 3. PackingManager creates package
> 
> I don't think it's fair to push this all on the package manager. If a dev  introduces new dependencies that need packaging, it should be their responsibility to make sure this is done.
> 
> 
> Chris
> 
>> 4. PM changes the status to "Pushed to Master"
>>
>> The work flow is important and I'd like to make it as transparent as
>> possible and make sure that we don't miss something.  Robin, Galen, or
>> others do you have any thoughts on this?
>>
>> Thanks,
>> Brendan
>