Do we have a place where all the current logic of the hooks is described?
I can use it as a base and adjust each one to the new logic we need.
On Tue, Feb 2, 2016 at 5:19 PM, David Caro wrote:
> On 01/28 16:17, Eyal Edri wrote:
> > David,
> > Is it something manual we need to
On 02/03 08:55, Eyal Edri wrote:
> Do we have a place where all the current logic of the hooks is described?
> I can use it as a base and adjust each one to the new logic we need.
Not really, we have the code, but the task to properly document was never
finished (in part because it's been
I've created a new spreadhsheet [1] with existing hooks.
Please review and comment on the current logic, and also on new logic or
new hooks needed.
Once we'll have everything sorted out we can plan how to update any hook if
needed.
[1]
On 01/28 16:17, Eyal Edri wrote:
> David,
> Is it something manual we need to change per version or we can add
> something automatic to work on any 3.6.X branch only (exluding the 3.6
> branch)?
Can you summarize the complete checks that should be done on the hooks
side? Because it's starting to
Maybe we should change the logic on moving bugs to MODIFIED,
Now that we moved to the version branch.
Tal - any thoughts on a logic that SHOULD move bugs to MODIFIED that we'll
be sure its OK?
e.
On Thu, Jan 28, 2016 at 10:03 AM, Tal Nisan wrote:
> After merging a patch for
After merging a patch for a 3.6.3 bug on the ovirt-engine-3.6 branch the
bug is moved to MODIFIED, since the 3.6.3 branch was opened yesterday the
bug should stay in POST until merged in ovirt-engine-3.6.3 branch as well
___
Infra mailing list
On Thu, Jan 28, 2016 at 10:23 AM, Yedidyah Bar David
wrote:
> On Thu, Jan 28, 2016 at 10:08 AM, Eyal Edri wrote:
> > Maybe we should change the logic on moving bugs to MODIFIED,
> > Now that we moved to the version branch.
> >
> > Tal - any thoughts on a logic
On Thu, Jan 28, 2016 at 10:08 AM, Eyal Edri wrote:
> Maybe we should change the logic on moving bugs to MODIFIED,
> Now that we moved to the version branch.
>
> Tal - any thoughts on a logic that SHOULD move bugs to MODIFIED that we'll
> be sure its OK?
Repeating myself from a
On Thu, Jan 28, 2016 at 10:59 AM, Eyal Edri wrote:
>
>
> On Thu, Jan 28, 2016 at 10:23 AM, Yedidyah Bar David
> wrote:
>>
>> On Thu, Jan 28, 2016 at 10:08 AM, Eyal Edri wrote:
>> > Maybe we should change the logic on moving bugs to MODIFIED,
This was the behavior in 3.6.2, don't know why it changed
On Thu, Jan 28, 2016 at 3:57 PM, Eyal Edri wrote:
> so maybe we'll stop moving bugs to MODIFIED if they are merged on stable
> branch (i.e ovirt-engine-3.6) and only if its merged into a version branch
> (i.e
It makes life easier for everyone when automation moves the bug to
MODIFIED, if the work is not done then the developer can always move it
back to POST like we sometimes do.
In any way, when a 3.6.3 bug is merged in 3.6.3 it should be moved to
MODIFIED, not a second before
On Thu, Jan 28, 2016
so maybe we'll stop moving bugs to MODIFIED if they are merged on stable
branch (i.e ovirt-engine-3.6) and only if its merged into a version branch
(i.e ovirt-engine-3.6.3) ?
On Thu, Jan 28, 2016 at 3:52 PM, Tal Nisan wrote:
> It makes life easier for everyone when automation
David,
Is it something manual we need to change per version or we can add
something automatic to work on any 3.6.X branch only (exluding the 3.6
branch)?
e.
On Thu, Jan 28, 2016 at 4:00 PM, Tal Nisan wrote:
> This was the behavior in 3.6.2, don't know why it changed
>
> On
13 matches
Mail list logo