From pmyers at redhat.com  Wed Jan  4 15:53:14 2012
From: pmyers at redhat.com (Perry Myers)
Date: Wed, 04 Jan 2012 10:53:14 -0500
Subject: oVirt Release Notes
In-Reply-To: <7dea1d9f-c1b3-4c6e-9dd3-d06e6fc4bfaa@zmail15.collab.prod.int.phx2.redhat.com>
References: <7dea1d9f-c1b3-4c6e-9dd3-d06e6fc4bfaa@zmail15.collab.prod.int.phx2.redhat.com>
Message-ID: <4F0475EA.8000704@redhat.com>

> - Writing a brief message in the bug's Technical Note field
> describing what the change being provided fixes/changed. Try to
> highlight the cause of the issue, the consequence it had in the past,
> the fix being implemented, and the result from a user perspective.
> That said generally we are only looking for a short paragraph per
> bug.

Don't know if you tried this but... when I log into bugzilla with my
non-redhat.com email address, I can see the Technical Notes field, but I
cannot edit it.  So we can't use the TechnicalNotes field unless that
restriction is removed.

> - Flag the bug as ovirt_requires_release_note?

This I can both see and set with my non-redhat.com login, so this is fine.

Perry


From sgordon at redhat.com  Wed Jan  4 21:18:17 2012
From: sgordon at redhat.com (Steve Gordon)
Date: Wed, 04 Jan 2012 16:18:17 -0500 (EST)
Subject: oVirt Release Notes
In-Reply-To: <4F0475EA.8000704@redhat.com>
Message-ID: <f02813a1-133a-4393-b802-b1420fa12f16@zmail15.collab.prod.int.phx2.redhat.com>

> > - Writing a brief message in the bug's Technical Note field
> > describing what the change being provided fixes/changed. Try to
> > highlight the cause of the issue, the consequence it had in the
> > past,
> > the fix being implemented, and the result from a user perspective.
> > That said generally we are only looking for a short paragraph per
> > bug.
> 
> Don't know if you tried this but... when I log into bugzilla with my
> non-redhat.com email address, I can see the Technical Notes field,
> but I
> cannot edit it.  So we can't use the TechnicalNotes field unless that
> restriction is removed.

Sure enough, the field is restricted. Apparently only the bug reporter or an internal user can edit this field and this is set globally across bugzilla, though it arguably isn't appropriate for this project. I think our options from here are either:

- Use a literal string to mark which comment(s) in a bug should be used as the technical note.

or

- Use a script to generate/update a wiki page containing a list of the flagged bugzillas so contributors can input the text directly there.

Both options have pros and cons, and neither is particularly neat, so this might be something to hash out on list and finalize at next weeks meeting.

> > - Flag the bug as ovirt_requires_release_note?
> 
> This I can both see and set with my non-redhat.com login, so this is
> fine.

While we sort out the other issues I definitely think we should keep setting the flag on bugs we think should be in the release notes, the deadline for this as discussed in today's oVirt sync meeting is January 16th.

Thanks,

Steve


From agl at us.ibm.com  Wed Jan  4 22:57:50 2012
From: agl at us.ibm.com (Adam Litke)
Date: Wed, 4 Jan 2012 16:57:50 -0600
Subject: Low-hanging fruit
Message-ID: <20120104225750.GB19854@us.ibm.com>

Hi all.  My team is adding 5-7 developers to help with oVirt development.  We
have some tasks in mind for them (especially around vdsm), but I wanted to ask
around for any low hanging fruit that could be suitable for developers that are
new to the project.  We are interested in helping out throughout oVirt (engine,
web ui, node, vdsm, etc.).  I know that all member projects use bugzilla, but it
is hard to identify entry level bugs/features unless you are familiar with the
project.  I am interested in anything that will help out the oVirt project.

So I will pose the question here:  Do you have some entry-level tasks/bugs that
you would like some help with?

Thanks for your replies!
-- 
Adam Litke <agl at us.ibm.com>
IBM Linux Technology Center



From iheim at redhat.com  Thu Jan  5 07:45:30 2012
From: iheim at redhat.com (Itamar Heim)
Date: Thu, 05 Jan 2012 09:45:30 +0200
Subject: Low-hanging fruit
In-Reply-To: <20120104225750.GB19854@us.ibm.com>
References: <20120104225750.GB19854@us.ibm.com>
Message-ID: <4F05551A.7010408@redhat.com>

On 01/05/2012 12:57 AM, Adam Litke wrote:
> Hi all.  My team is adding 5-7 developers to help with oVirt development.  We
> have some tasks in mind for them (especially around vdsm), but I wanted to ask
> around for any low hanging fruit that could be suitable for developers that are
> new to the project.  We are interested in helping out throughout oVirt (engine,
> web ui, node, vdsm, etc.).  I know that all member projects use bugzilla, but it
> is hard to identify entry level bugs/features unless you are familiar with the
> project.  I am interested in anything that will help out the oVirt project.
>
> So I will pose the question here:  Do you have some entry-level tasks/bugs that
> you would like some help with?
>
> Thanks for your replies!

how about if we flag some of the BZs with the keyword EasyFix/CodeChange?



From agl at us.ibm.com  Thu Jan  5 14:14:05 2012
From: agl at us.ibm.com (Adam Litke)
Date: Thu, 5 Jan 2012 08:14:05 -0600
Subject: Low-hanging fruit
In-Reply-To: <4F05551A.7010408@redhat.com>
References: <20120104225750.GB19854@us.ibm.com> <4F05551A.7010408@redhat.com>
Message-ID: <20120105141405.GC19854@us.ibm.com>

On Thu, Jan 05, 2012 at 09:45:30AM +0200, Itamar Heim wrote:
> On 01/05/2012 12:57 AM, Adam Litke wrote:
> >Hi all.  My team is adding 5-7 developers to help with oVirt development.  We
> >have some tasks in mind for them (especially around vdsm), but I wanted to ask
> >around for any low hanging fruit that could be suitable for developers that are
> >new to the project.  We are interested in helping out throughout oVirt (engine,
> >web ui, node, vdsm, etc.).  I know that all member projects use bugzilla, but it
> >is hard to identify entry level bugs/features unless you are familiar with the
> >project.  I am interested in anything that will help out the oVirt project.
> >
> >So I will pose the question here:  Do you have some entry-level tasks/bugs that
> >you would like some help with?
> >
> >Thanks for your replies!
> 
> how about if we flag some of the BZs with the keyword EasyFix/CodeChange?

Yes, that would be extremely helpful.  +2.

-- 
Adam Litke <agl at us.ibm.com>
IBM Linux Technology Center



From danken at redhat.com  Thu Jan  5 19:32:36 2012
From: danken at redhat.com (Dan Kenigsberg)
Date: Thu, 5 Jan 2012 21:32:36 +0200
Subject: Low-hanging fruit
In-Reply-To: <20120104225750.GB19854@us.ibm.com>
References: <20120104225750.GB19854@us.ibm.com>
Message-ID: <20120105193235.GB32289@redhat.com>

On Wed, Jan 04, 2012 at 04:57:50PM -0600, Adam Litke wrote:
> Hi all.  My team is adding 5-7 developers to help with oVirt development.  We
> have some tasks in mind for them (especially around vdsm), but I wanted to ask
> around for any low hanging fruit that could be suitable for developers that are
> new to the project.  We are interested in helping out throughout oVirt (engine,
> web ui, node, vdsm, etc.).  I know that all member projects use bugzilla, but it
> is hard to identify entry level bugs/features unless you are familiar with the
> project.  I am interested in anything that will help out the oVirt project.
> 
> So I will pose the question here:  Do you have some entry-level tasks/bugs that
> you would like some help with?

Recently I've opened an embarrassingly-empty
http://ovirt.org/wiki/Vdsm_TODO but it links to bugzilla. The problem is
that bugs there are not sortable by apparent difficulty. I've added
EasyFix keyword to few of the bugs, but it is way short of a proper
intoductory task list.

I'll try to add bullets in the coming as we go.

Dan.


From cctrieloff at redhat.com  Thu Jan  5 20:00:36 2012
From: cctrieloff at redhat.com (Carl Trieloff)
Date: Thu, 05 Jan 2012 15:00:36 -0500
Subject: Low-hanging fruit
In-Reply-To: <20120105193235.GB32289@redhat.com>
References: <20120104225750.GB19854@us.ibm.com>
	<20120105193235.GB32289@redhat.com>
Message-ID: <4F060164.9090607@redhat.com>

On 01/05/2012 02:32 PM, Dan Kenigsberg wrote:
> On Wed, Jan 04, 2012 at 04:57:50PM -0600, Adam Litke wrote:
>> Hi all.  My team is adding 5-7 developers to help with oVirt development.  We
>> have some tasks in mind for them (especially around vdsm), but I wanted to ask
>> around for any low hanging fruit that could be suitable for developers that are
>> new to the project.  We are interested in helping out throughout oVirt (engine,
>> web ui, node, vdsm, etc.).  I know that all member projects use bugzilla, but it
>> is hard to identify entry level bugs/features unless you are familiar with the
>> project.  I am interested in anything that will help out the oVirt project.
>>
>> So I will pose the question here:  Do you have some entry-level tasks/bugs that
>> you would like some help with?
> Recently I've opened an embarrassingly-empty
> http://ovirt.org/wiki/Vdsm_TODO but it links to bugzilla. The problem is
> that bugs there are not sortable by apparent difficulty. I've added
> EasyFix keyword to few of the bugs, but it is way short of a proper
> intoductory task list.
>
> I'll try to add bullets in the coming as we go.
>
>

We should get lists for all the components going.

Carl


From agl at us.ibm.com  Thu Jan  5 21:49:04 2012
From: agl at us.ibm.com (Adam Litke)
Date: Thu, 5 Jan 2012 15:49:04 -0600
Subject: Low-hanging fruit
In-Reply-To: <20120105193235.GB32289@redhat.com>
References: <20120104225750.GB19854@us.ibm.com>
	<20120105193235.GB32289@redhat.com>
Message-ID: <20120105214904.GG19854@us.ibm.com>

On Thu, Jan 05, 2012 at 09:32:36PM +0200, Dan Kenigsberg wrote:
> On Wed, Jan 04, 2012 at 04:57:50PM -0600, Adam Litke wrote:
> > Hi all.  My team is adding 5-7 developers to help with oVirt development.  We
> > have some tasks in mind for them (especially around vdsm), but I wanted to ask
> > around for any low hanging fruit that could be suitable for developers that are
> > new to the project.  We are interested in helping out throughout oVirt (engine,
> > web ui, node, vdsm, etc.).  I know that all member projects use bugzilla, but it
> > is hard to identify entry level bugs/features unless you are familiar with the
> > project.  I am interested in anything that will help out the oVirt project.
> > 
> > So I will pose the question here:  Do you have some entry-level tasks/bugs that
> > you would like some help with?
> 
> Recently I've opened an embarrassingly-empty
> http://ovirt.org/wiki/Vdsm_TODO but it links to bugzilla. The problem is
> that bugs there are not sortable by apparent difficulty. I've added
> EasyFix keyword to few of the bugs, but it is way short of a proper
> intoductory task list.
> 
> I'll try to add bullets in the coming as we go.

Thanks Dan!  This looks like a good list to start with.

-- 
Adam Litke <agl at us.ibm.com>
IBM Linux Technology Center



From iheim at redhat.com  Sun Jan  8 07:11:23 2012
From: iheim at redhat.com (Itamar Heim)
Date: Sun, 08 Jan 2012 09:11:23 +0200
Subject: Low-hanging fruit
In-Reply-To: <20120105141405.GC19854@us.ibm.com>
References: <20120104225750.GB19854@us.ibm.com> <4F05551A.7010408@redhat.com>
	<20120105141405.GC19854@us.ibm.com>
Message-ID: <4F09419B.2080500@redhat.com>

On 01/05/2012 04:14 PM, Adam Litke wrote:
> On Thu, Jan 05, 2012 at 09:45:30AM +0200, Itamar Heim wrote:
>> On 01/05/2012 12:57 AM, Adam Litke wrote:
>>> Hi all.  My team is adding 5-7 developers to help with oVirt development.  We
>>> have some tasks in mind for them (especially around vdsm), but I wanted to ask
>>> around for any low hanging fruit that could be suitable for developers that are
>>> new to the project.  We are interested in helping out throughout oVirt (engine,
>>> web ui, node, vdsm, etc.).  I know that all member projects use bugzilla, but it
>>> is hard to identify entry level bugs/features unless you are familiar with the
>>> project.  I am interested in anything that will help out the oVirt project.
>>>
>>> So I will pose the question here:  Do you have some entry-level tasks/bugs that
>>> you would like some help with?
>>>
>>> Thanks for your replies!
>>
>> how about if we flag some of the BZs with the keyword EasyFix/CodeChange?
>
> Yes, that would be extremely helpful.  +2.
>

until i will manage to find how to share a public query:

all open ovirt EasyFix[1]:
http://tinyurl.com/6tsrrfk

all ovirt feature requests:
http://tinyurl.com/6rzbucg

will add more to these lists

[1] even if it is in POST, you could help review


From agl at us.ibm.com  Mon Jan  9 14:30:22 2012
From: agl at us.ibm.com (Adam Litke)
Date: Mon, 9 Jan 2012 08:30:22 -0600
Subject: Low-hanging fruit
In-Reply-To: <4F09419B.2080500@redhat.com>
References: <20120104225750.GB19854@us.ibm.com> <4F05551A.7010408@redhat.com>
	<20120105141405.GC19854@us.ibm.com> <4F09419B.2080500@redhat.com>
Message-ID: <20120109143022.GD3573@us.ibm.com>

On Sun, Jan 08, 2012 at 09:11:23AM +0200, Itamar Heim wrote:
> On 01/05/2012 04:14 PM, Adam Litke wrote:
> >On Thu, Jan 05, 2012 at 09:45:30AM +0200, Itamar Heim wrote:
> >>On 01/05/2012 12:57 AM, Adam Litke wrote:
> >>>Hi all.  My team is adding 5-7 developers to help with oVirt development.  We
> >>>have some tasks in mind for them (especially around vdsm), but I wanted to ask
> >>>around for any low hanging fruit that could be suitable for developers that are
> >>>new to the project.  We are interested in helping out throughout oVirt (engine,
> >>>web ui, node, vdsm, etc.).  I know that all member projects use bugzilla, but it
> >>>is hard to identify entry level bugs/features unless you are familiar with the
> >>>project.  I am interested in anything that will help out the oVirt project.
> >>>
> >>>So I will pose the question here:  Do you have some entry-level tasks/bugs that
> >>>you would like some help with?
> >>>
> >>>Thanks for your replies!
> >>
> >>how about if we flag some of the BZs with the keyword EasyFix/CodeChange?
> >
> >Yes, that would be extremely helpful.  +2.
> >
> 
> until i will manage to find how to share a public query:
> 
> all open ovirt EasyFix[1]:
> http://tinyurl.com/6tsrrfk
> 
> all ovirt feature requests:
> http://tinyurl.com/6rzbucg
> 
> will add more to these lists

Thanks Itamar!  I've added these two URLs to my list.  We should be sending in
some reinforcements in short order.

-- 
Adam Litke <agl at us.ibm.com>
IBM Linux Technology Center



From iheim at redhat.com  Mon Jan  9 14:34:52 2012
From: iheim at redhat.com (Itamar Heim)
Date: Mon, 09 Jan 2012 16:34:52 +0200
Subject: Low-hanging fruit
In-Reply-To: <20120109143022.GD3573@us.ibm.com>
References: <20120104225750.GB19854@us.ibm.com> <4F05551A.7010408@redhat.com>
	<20120105141405.GC19854@us.ibm.com> <4F09419B.2080500@redhat.com>
	<20120109143022.GD3573@us.ibm.com>
Message-ID: <4F0AFB0C.7070205@redhat.com>

On 01/09/2012 04:30 PM, Adam Litke wrote:
> On Sun, Jan 08, 2012 at 09:11:23AM +0200, Itamar Heim wrote:
>> On 01/05/2012 04:14 PM, Adam Litke wrote:
>>> On Thu, Jan 05, 2012 at 09:45:30AM +0200, Itamar Heim wrote:
>>>> On 01/05/2012 12:57 AM, Adam Litke wrote:
>>>>> Hi all.  My team is adding 5-7 developers to help with oVirt development.  We
>>>>> have some tasks in mind for them (especially around vdsm), but I wanted to ask
>>>>> around for any low hanging fruit that could be suitable for developers that are
>>>>> new to the project.  We are interested in helping out throughout oVirt (engine,
>>>>> web ui, node, vdsm, etc.).  I know that all member projects use bugzilla, but it
>>>>> is hard to identify entry level bugs/features unless you are familiar with the
>>>>> project.  I am interested in anything that will help out the oVirt project.
>>>>>
>>>>> So I will pose the question here:  Do you have some entry-level tasks/bugs that
>>>>> you would like some help with?
>>>>>
>>>>> Thanks for your replies!
>>>>
>>>> how about if we flag some of the BZs with the keyword EasyFix/CodeChange?
>>>
>>> Yes, that would be extremely helpful.  +2.
>>>
>>
>> until i will manage to find how to share a public query:
>>
>> all open ovirt EasyFix[1]:
>> http://tinyurl.com/6tsrrfk
>>
>> all ovirt feature requests:
>> http://tinyurl.com/6rzbucg

I found a mistype in this query...
this is the correct one for features:
http://tinyurl.com/oVirt-Features

I've aliased EasyFix query as well now as:
http://tinyurl.com/oVirt-EasyFix

>>
>> will add more to these lists
>
> Thanks Itamar!  I've added these two URLs to my list.  We should be sending in
> some reinforcements in short order.
>

looking forward to them


From mburns at redhat.com  Mon Jan  9 14:45:14 2012
From: mburns at redhat.com (Mike Burns)
Date: Mon, 09 Jan 2012 09:45:14 -0500
Subject: Low-hanging fruit
In-Reply-To: <4F0AFB0C.7070205@redhat.com>
References: <20120104225750.GB19854@us.ibm.com>
	<4F05551A.7010408@redhat.com> <20120105141405.GC19854@us.ibm.com>
	<4F09419B.2080500@redhat.com> <20120109143022.GD3573@us.ibm.com>
	<4F0AFB0C.7070205@redhat.com>
Message-ID: <1326120314.3202.18.camel@beelzebub.mburnsfire.net>

On Mon, 2012-01-09 at 16:34 +0200, Itamar Heim wrote:
> On 01/09/2012 04:30 PM, Adam Litke wrote:
> > On Sun, Jan 08, 2012 at 09:11:23AM +0200, Itamar Heim wrote:
> >> On 01/05/2012 04:14 PM, Adam Litke wrote:
> >>> On Thu, Jan 05, 2012 at 09:45:30AM +0200, Itamar Heim wrote:
> >>>> On 01/05/2012 12:57 AM, Adam Litke wrote:
> >>>>> Hi all.  My team is adding 5-7 developers to help with oVirt development.  We
> >>>>> have some tasks in mind for them (especially around vdsm), but I wanted to ask
> >>>>> around for any low hanging fruit that could be suitable for developers that are
> >>>>> new to the project.  We are interested in helping out throughout oVirt (engine,
> >>>>> web ui, node, vdsm, etc.).  I know that all member projects use bugzilla, but it
> >>>>> is hard to identify entry level bugs/features unless you are familiar with the
> >>>>> project.  I am interested in anything that will help out the oVirt project.
> >>>>>
> >>>>> So I will pose the question here:  Do you have some entry-level tasks/bugs that
> >>>>> you would like some help with?
> >>>>>
> >>>>> Thanks for your replies!
> >>>>
> >>>> how about if we flag some of the BZs with the keyword EasyFix/CodeChange?
> >>>
> >>> Yes, that would be extremely helpful.  +2.
> >>>
> >>
> >> until i will manage to find how to share a public query:
> >>
> >> all open ovirt EasyFix[1]:
> >> http://tinyurl.com/6tsrrfk
> >>
> >> all ovirt feature requests:
> >> http://tinyurl.com/6rzbucg
> 
> I found a mistype in this query...
> this is the correct one for features:
> http://tinyurl.com/oVirt-Features
> 
> I've aliased EasyFix query as well now as:
> http://tinyurl.com/oVirt-EasyFix
> 
> >>
> >> will add more to these lists
> >
> > Thanks Itamar!  I've added these two URLs to my list.  We should be sending in
> > some reinforcements in short order.
> >

Sorry I'm jumping in a bit late.  I'm looking at ovirt-node bugs now and
will start flagging some with the EasyFix keyword.  Our current backlog
(as well as targeted release dates for ovirt-node) is here:  

http://www.ovirt.org/wiki/Node_Backlog

Mike

> 
> looking forward to them
> _______________________________________________
> Arch mailing list
> Arch at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/arch




From mgoldboi at redhat.com  Wed Jan 11 13:35:55 2012
From: mgoldboi at redhat.com (Moran Goldboim)
Date: Wed, 11 Jan 2012 15:35:55 +0200
Subject: oVirt test day is coming - Jan 16th
Message-ID: <4F0D903B.3020502@redhat.com>

Looking forward to ovirt first release on Jan 31th.
we would like all to participate in oVirt test day on the 16Th. This 
would be an opportunity to exercise a oVirt for the upcoming release. 
Each Test Day brings something unique and you're encouraged to join and 
share your ideas, tests, and results.
all needed information is available in 
http://www.ovirt.org/wiki/Testing/OvirtTestDay
please review it, subscribe and have fun with it.

Moran.


From oschreib at redhat.com  Sun Jan 15 15:24:48 2012
From: oschreib at redhat.com (Ofer Schreiber)
Date: Sun, 15 Jan 2012 10:24:48 -0500 (EST)
Subject: Brancing day - TODAY!
Message-ID: <059301ccd399$d3ca9db0$7b5fd910$@redhat.com>

As you may know, today is the branching day for oVirt project.
Please create a versioned branch (for example, in ovirt-engine we use
engine_3.0 as the branch name) today.
If you experience any problem doing so, or you have any other
issue/question, please contact me.

Thanks,
--
Ofer Schreiber 
Red Hat Israel, Ra'anana

+972-9-7692347
www.redhat.com




From mgoldboi at redhat.com  Sun Jan 15 15:36:38 2012
From: mgoldboi at redhat.com (Moran Goldboim)
Date: Sun, 15 Jan 2012 17:36:38 +0200
Subject: oVirt test day is coming - Jan 16th -  Deferred to Jan 18th
In-Reply-To: <4F0D903B.3020502@redhat.com>
References: <4F0D903B.3020502@redhat.com>
Message-ID: <4F12F286.5020800@redhat.com>

Due to a late re-base we have decided to defer the testday in 2 days to 
Wednesday Jan 18th.
Sorry for the late notice, hope to see you all there.

Moran.


On 01/11/2012 03:35 PM, Moran Goldboim wrote:
> Looking forward to ovirt first release on Jan 31th.
> we would like all to participate in oVirt test day on the 16Th. This 
> would be an opportunity to exercise a oVirt for the upcoming release. 
> Each Test Day brings something unique and you're encouraged to join 
> and share your ideas, tests, and results.
> all needed information is available in 
> http://www.ovirt.org/wiki/Testing/OvirtTestDay
> please review it, subscribe and have fun with it.
>
> Moran.



From mgoldboi at redhat.com  Sun Jan 15 15:39:20 2012
From: mgoldboi at redhat.com (Moran Goldboim)
Date: Sun, 15 Jan 2012 17:39:20 +0200
Subject: oVirt test day is coming - Jan 16th -  Deferred to Jan 18th
In-Reply-To: <4F12F286.5020800@redhat.com>
References: <4F0D903B.3020502@redhat.com> <4F12F286.5020800@redhat.com>
Message-ID: <4F12F328.6040701@redhat.com>

meant late branching not rebase.
Moran.

On 01/15/2012 05:36 PM, Moran Goldboim wrote:
> Due to a late re-base we have decided to defer the testday in 2 days 
> to Wednesday Jan 18th.
> Sorry for the late notice, hope to see you all there.
>
> Moran.
>
>
> On 01/11/2012 03:35 PM, Moran Goldboim wrote:
>> Looking forward to ovirt first release on Jan 31th.
>> we would like all to participate in oVirt test day on the 16Th. This 
>> would be an opportunity to exercise a oVirt for the upcoming release. 
>> Each Test Day brings something unique and you're encouraged to join 
>> and share your ideas, tests, and results.
>> all needed information is available in 
>> http://www.ovirt.org/wiki/Testing/OvirtTestDay
>> please review it, subscribe and have fun with it.
>>
>> Moran.
>
> _______________________________________________
> Arch mailing list
> Arch at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/arch


From dfediuck at redhat.com  Sun Jan 15 16:04:12 2012
From: dfediuck at redhat.com (Doron Fediuck)
Date: Sun, 15 Jan 2012 18:04:12 +0200
Subject: Brancing day - TODAY!
In-Reply-To: <059301ccd399$d3ca9db0$7b5fd910$@redhat.com>
References: <059301ccd399$d3ca9db0$7b5fd910$@redhat.com>
Message-ID: <4106269.iiZmIjfSaj@doronf-laptop>

On Sunday 15 January 2012 10:24:48 Ofer Schreiber wrote:
> As you may know, today is the branching day for oVirt project.
> Please create a versioned branch (for example, in ovirt-engine we use
> engine_3.0 as the branch name) today.
> If you experience any problem doing so, or you have any other
> issue/question, please contact me.
> 
> Thanks,
> --
> Ofer Schreiber
> Red Hat Israel, Ra'anana
> 
> +972-9-7692347
> www.redhat.com
> 
> 
Sorry to be the bad guy (again...)
But why should such actions take place on a Sunday, which
is a weekend for most people?

For next time, please try to do it during Monday-Thursday.
-- 

/d

"This message is made witn 100% recycled electrons. No new atoms were 
destroyed in the making of this message."



From mburns at redhat.com  Mon Jan 16 02:08:26 2012
From: mburns at redhat.com (Mike Burns)
Date: Sun, 15 Jan 2012 21:08:26 -0500
Subject: Brancing day - TODAY!
In-Reply-To: <4106269.iiZmIjfSaj@doronf-laptop>
References: <059301ccd399$d3ca9db0$7b5fd910$@redhat.com>
	<4106269.iiZmIjfSaj@doronf-laptop>
Message-ID: <1326679706.2463.1.camel@beelzebub.mburnsfire.net>

On Sun, 2012-01-15 at 18:04 +0200, Doron Fediuck wrote:
> On Sunday 15 January 2012 10:24:48 Ofer Schreiber wrote:
> > As you may know, today is the branching day for oVirt project.
> > Please create a versioned branch (for example, in ovirt-engine we use
> > engine_3.0 as the branch name) today.
> > If you experience any problem doing so, or you have any other
> > issue/question, please contact me.
> > 
> > Thanks,
> > --
> > Ofer Schreiber
> > Red Hat Israel, Ra'anana
> > 
> > +972-9-7692347
> > www.redhat.com
> > 
> > 
> Sorry to be the bad guy (again...)
> But why should such actions take place on a Sunday, which
> is a weekend for most people?
> 
> For next time, please try to do it during Monday-Thursday.

+1

Also,  is there a process for doing this in gerrit?  Or is it just a
matter of git checkout -b <branch-name>; git push gerrit <branch-name> ?
I'm also curious if there is a way to push tags into gerrit.

Mike



From iheim at redhat.com  Mon Jan 16 09:59:50 2012
From: iheim at redhat.com (Itamar Heim)
Date: Mon, 16 Jan 2012 11:59:50 +0200
Subject: Brancing day - TODAY!
In-Reply-To: <1326679706.2463.1.camel@beelzebub.mburnsfire.net>
References: <059301ccd399$d3ca9db0$7b5fd910$@redhat.com>
	<4106269.iiZmIjfSaj@doronf-laptop>
	<1326679706.2463.1.camel@beelzebub.mburnsfire.net>
Message-ID: <4F13F516.9010607@redhat.com>

On 01/16/2012 04:08 AM, Mike Burns wrote:
> On Sun, 2012-01-15 at 18:04 +0200, Doron Fediuck wrote:
>> On Sunday 15 January 2012 10:24:48 Ofer Schreiber wrote:
>>> As you may know, today is the branching day for oVirt project.
>>> Please create a versioned branch (for example, in ovirt-engine we use
>>> engine_3.0 as the branch name) today.
>>> If you experience any problem doing so, or you have any other
>>> issue/question, please contact me.
>>>
>>> Thanks,
>>> --
>>> Ofer Schreiber
>>> Red Hat Israel, Ra'anana
>>>
>>> +972-9-7692347
>>> www.redhat.com
>>>
>>>
>> Sorry to be the bad guy (again...)
>> But why should such actions take place on a Sunday, which
>> is a weekend for most people?
>>
>> For next time, please try to do it during Monday-Thursday.
>
> +1
>
> Also,  is there a process for doing this in gerrit?  Or is it just a
> matter of git checkout -b<branch-name>; git push gerrit<branch-name>  ?
> I'm also curious if there is a way to push tags into gerrit.

there are permissions in gerrit to create references/tags.
to avoid mistakes, they are not given by default, but for each project 
just specify who should create them (or if all maintainers should get 
them), or just ask to create a branch for you.


From mburns at redhat.com  Mon Jan 16 13:01:08 2012
From: mburns at redhat.com (Mike Burns)
Date: Mon, 16 Jan 2012 08:01:08 -0500
Subject: Brancing day - TODAY!
In-Reply-To: <4F13F516.9010607@redhat.com>
References: <059301ccd399$d3ca9db0$7b5fd910$@redhat.com>
	<4106269.iiZmIjfSaj@doronf-laptop>
	<1326679706.2463.1.camel@beelzebub.mburnsfire.net>
	<4F13F516.9010607@redhat.com>
Message-ID: <1326718868.2463.3.camel@beelzebub.mburnsfire.net>

On Mon, 2012-01-16 at 11:59 +0200, Itamar Heim wrote:
> On 01/16/2012 04:08 AM, Mike Burns wrote:
> > On Sun, 2012-01-15 at 18:04 +0200, Doron Fediuck wrote:
> >> On Sunday 15 January 2012 10:24:48 Ofer Schreiber wrote:
> >>> As you may know, today is the branching day for oVirt project.
> >>> Please create a versioned branch (for example, in ovirt-engine we use
> >>> engine_3.0 as the branch name) today.
> >>> If you experience any problem doing so, or you have any other
> >>> issue/question, please contact me.
> >>>
> >>> Thanks,
> >>> --
> >>> Ofer Schreiber
> >>> Red Hat Israel, Ra'anana
> >>>
> >>> +972-9-7692347
> >>> www.redhat.com
> >>>
> >>>
> >> Sorry to be the bad guy (again...)
> >> But why should such actions take place on a Sunday, which
> >> is a weekend for most people?
> >>
> >> For next time, please try to do it during Monday-Thursday.
> >
> > +1
> >
> > Also,  is there a process for doing this in gerrit?  Or is it just a
> > matter of git checkout -b<branch-name>; git push gerrit<branch-name>  ?
> > I'm also curious if there is a way to push tags into gerrit.
> 
> there are permissions in gerrit to create references/tags.
> to avoid mistakes, they are not given by default, but for each project 
> just specify who should create them (or if all maintainers should get 
> them), or just ask to create a branch for you.

Please grant that permission to all the maintainers of ovirt-node.  

Thanks

Mike



From anthony at codemonkey.ws  Mon Jan 16 13:36:37 2012
From: anthony at codemonkey.ws (Anthony Liguori)
Date: Mon, 16 Jan 2012 07:36:37 -0600
Subject: oVirt test day is coming - Jan 16th -  Deferred to Jan 18th
In-Reply-To: <4F12F286.5020800@redhat.com>
References: <4F0D903B.3020502@redhat.com> <4F12F286.5020800@redhat.com>
Message-ID: <4F1427E5.2060106@codemonkey.ws>

On 01/15/2012 09:36 AM, Moran Goldboim wrote:
> Due to a late re-base we have decided to defer the testday in 2 days to
> Wednesday Jan 18th.
> Sorry for the late notice, hope to see you all there.

Not that I mind the test day being moved, but how was it decided to move the 
test day?  I don't see any discussion on any of the various lists (at list, that 
I'm on).

We are planning on participating and would have liked to provide some input in 
the decision.

Regards,

Anthony Liguori

>
> Moran.
>
>
> On 01/11/2012 03:35 PM, Moran Goldboim wrote:
>> Looking forward to ovirt first release on Jan 31th.
>> we would like all to participate in oVirt test day on the 16Th. This would be
>> an opportunity to exercise a oVirt for the upcoming release. Each Test Day
>> brings something unique and you're encouraged to join and share your ideas,
>> tests, and results.
>> all needed information is available in
>> http://www.ovirt.org/wiki/Testing/OvirtTestDay
>> please review it, subscribe and have fun with it.
>>
>> Moran.
>
> _______________________________________________
> Arch mailing list
> Arch at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/arch



From iheim at redhat.com  Mon Jan 16 14:12:47 2012
From: iheim at redhat.com (Itamar Heim)
Date: Mon, 16 Jan 2012 16:12:47 +0200
Subject: Brancing day - TODAY!
In-Reply-To: <1326718868.2463.3.camel@beelzebub.mburnsfire.net>
References: <059301ccd399$d3ca9db0$7b5fd910$@redhat.com>
	<4106269.iiZmIjfSaj@doronf-laptop>
	<1326679706.2463.1.camel@beelzebub.mburnsfire.net>
	<4F13F516.9010607@redhat.com>
	<1326718868.2463.3.camel@beelzebub.mburnsfire.net>
Message-ID: <4F14305F.1080506@redhat.com>

On 01/16/2012 03:01 PM, Mike Burns wrote:
> On Mon, 2012-01-16 at 11:59 +0200, Itamar Heim wrote:
>> On 01/16/2012 04:08 AM, Mike Burns wrote:
>>> On Sun, 2012-01-15 at 18:04 +0200, Doron Fediuck wrote:
>>>> On Sunday 15 January 2012 10:24:48 Ofer Schreiber wrote:
>>>>> As you may know, today is the branching day for oVirt project.
>>>>> Please create a versioned branch (for example, in ovirt-engine we use
>>>>> engine_3.0 as the branch name) today.
>>>>> If you experience any problem doing so, or you have any other
>>>>> issue/question, please contact me.
>>>>>
>>>>> Thanks,
>>>>> --
>>>>> Ofer Schreiber
>>>>> Red Hat Israel, Ra'anana
>>>>>
>>>>> +972-9-7692347
>>>>> www.redhat.com
>>>>>
>>>>>
>>>> Sorry to be the bad guy (again...)
>>>> But why should such actions take place on a Sunday, which
>>>> is a weekend for most people?
>>>>
>>>> For next time, please try to do it during Monday-Thursday.
>>>
>>> +1
>>>
>>> Also,  is there a process for doing this in gerrit?  Or is it just a
>>> matter of git checkout -b<branch-name>; git push gerrit<branch-name>   ?
>>> I'm also curious if there is a way to push tags into gerrit.
>>
>> there are permissions in gerrit to create references/tags.
>> to avoid mistakes, they are not given by default, but for each project
>> just specify who should create them (or if all maintainers should get
>> them), or just ask to create a branch for you.
>
> Please grant that permission to all the maintainers of ovirt-node.

done.
you should be able to create branches via the gerrit UI.
also to 'push annotated tags'.

i couldn't find a permission to 'remove branch' to delegate, so if you 
need to remove a branch, just ping.


From mburns at redhat.com  Mon Jan 16 14:18:26 2012
From: mburns at redhat.com (Mike Burns)
Date: Mon, 16 Jan 2012 09:18:26 -0500
Subject: Brancing day - TODAY!
In-Reply-To: <4F14305F.1080506@redhat.com>
References: <059301ccd399$d3ca9db0$7b5fd910$@redhat.com>
	<4106269.iiZmIjfSaj@doronf-laptop>
	<1326679706.2463.1.camel@beelzebub.mburnsfire.net>
	<4F13F516.9010607@redhat.com>
	<1326718868.2463.3.camel@beelzebub.mburnsfire.net>
	<4F14305F.1080506@redhat.com>
Message-ID: <1326723506.2463.4.camel@beelzebub.mburnsfire.net>

On Mon, 2012-01-16 at 16:12 +0200, Itamar Heim wrote:
> On 01/16/2012 03:01 PM, Mike Burns wrote:
> > On Mon, 2012-01-16 at 11:59 +0200, Itamar Heim wrote:
> >> On 01/16/2012 04:08 AM, Mike Burns wrote:
> >>> On Sun, 2012-01-15 at 18:04 +0200, Doron Fediuck wrote:
> >>>> On Sunday 15 January 2012 10:24:48 Ofer Schreiber wrote:
> >>>>> As you may know, today is the branching day for oVirt project.
> >>>>> Please create a versioned branch (for example, in ovirt-engine we use
> >>>>> engine_3.0 as the branch name) today.
> >>>>> If you experience any problem doing so, or you have any other
> >>>>> issue/question, please contact me.
> >>>>>
> >>>>> Thanks,
> >>>>> --
> >>>>> Ofer Schreiber
> >>>>> Red Hat Israel, Ra'anana
> >>>>>
> >>>>> +972-9-7692347
> >>>>> www.redhat.com
> >>>>>
> >>>>>
> >>>> Sorry to be the bad guy (again...)
> >>>> But why should such actions take place on a Sunday, which
> >>>> is a weekend for most people?
> >>>>
> >>>> For next time, please try to do it during Monday-Thursday.
> >>>
> >>> +1
> >>>
> >>> Also,  is there a process for doing this in gerrit?  Or is it just a
> >>> matter of git checkout -b<branch-name>; git push gerrit<branch-name>   ?
> >>> I'm also curious if there is a way to push tags into gerrit.
> >>
> >> there are permissions in gerrit to create references/tags.
> >> to avoid mistakes, they are not given by default, but for each project
> >> just specify who should create them (or if all maintainers should get
> >> them), or just ask to create a branch for you.
> >
> > Please grant that permission to all the maintainers of ovirt-node.
> 
> done.
> you should be able to create branches via the gerrit UI.
> also to 'push annotated tags'.
> 
> i couldn't find a permission to 'remove branch' to delegate, so if you 
> need to remove a branch, just ping.

Thanks!



From mgoldboi at redhat.com  Mon Jan 16 15:20:41 2012
From: mgoldboi at redhat.com (Moran Goldboim)
Date: Mon, 16 Jan 2012 17:20:41 +0200
Subject: oVirt test day is coming - Jan 16th -  Deferred to Jan 18th
In-Reply-To: <4F1427E5.2060106@codemonkey.ws>
References: <4F0D903B.3020502@redhat.com> <4F12F286.5020800@redhat.com>
	<4F1427E5.2060106@codemonkey.ws>
Message-ID: <4F144049.3020907@redhat.com>

On 01/16/2012 03:36 PM, Anthony Liguori wrote:
> On 01/15/2012 09:36 AM, Moran Goldboim wrote:
>> Due to a late re-base we have decided to defer the testday in 2 days to
>> Wednesday Jan 18th.
>> Sorry for the late notice, hope to see you all there.
>
> Not that I mind the test day being moved, but how was it decided to 
> move the test day?  I don't see any discussion on any of the various 
> lists (at list, that I'm on).
>
> We are planning on participating and would have liked to provide some 
> input in the decision.
>
> Regards,
>
> Anthony Liguori

Anthony, this issue has been discussed at oVirt Weekly Sync Meeting on 
Jan 11th, in which it was decided that if a late branching will happen 
testday will be deferred by one or two days.

Moran.

>
>>
>> Moran.
>>
>>
>> On 01/11/2012 03:35 PM, Moran Goldboim wrote:
>>> Looking forward to ovirt first release on Jan 31th.
>>> we would like all to participate in oVirt test day on the 16Th. This 
>>> would be
>>> an opportunity to exercise a oVirt for the upcoming release. Each 
>>> Test Day
>>> brings something unique and you're encouraged to join and share your 
>>> ideas,
>>> tests, and results.
>>> all needed information is available in
>>> http://www.ovirt.org/wiki/Testing/OvirtTestDay
>>> please review it, subscribe and have fun with it.
>>>
>>> Moran.
>>
>> _______________________________________________
>> Arch mailing list
>> Arch at ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/arch
>



From sgordon at redhat.com  Mon Jan 16 15:34:01 2012
From: sgordon at redhat.com (Steve Gordon)
Date: Mon, 16 Jan 2012 10:34:01 -0500 (EST)
Subject: Call for oVirt subproject release note beats!
In-Reply-To: <c8e36eae-f88d-4f09-a2b6-be79f3094708@zmail15.collab.prod.int.phx2.redhat.com>
Message-ID: <8fa1a6b7-c39a-45a4-8cd6-9be6ac0d6faa@zmail15.collab.prod.int.phx2.redhat.com>

Hi all,

As discussed in last week's sync-up meeting I emailed the contributors listed as oVirt subproject maintainers requesting release note beats. So far only the oVirt engine section of the release notes page has been populated (thanks Livnat!). The release notes page is here:

    http://www.ovirt.org/wiki/Release_Notes

Please take the time to update it with any features, resolved issues, or known issues you are aware of that you think should be noted for this first release of oVirt. Even one liners or a link to the relevant feature page/bugzilla would be great, I intend to edit this into a cohesive document before the actual release.

Thanks,

Steve

----- Original Message -----
> From: "Steve Gordon" <sgordon at redhat.com>
> To: "Michael Pasternak" <mpastern at redhat.com>, "Einav Cohen" <ecohen at redhat.com>, "Itamar Heim" <iheim at redhat.com>,
> "Barak Azulay" <bazulay at redhat.com>, "Yaniv Dary" <ydary at redhat.com>, "Ofer Schreiber" <oschreib at redhat.com>, "Alan
> Pevec" <apevec at redhat.com>, "Livnat Peer" <lpeer at redhat.com>, "Ayal Baron" <abaron at redhat.com>
> Cc: "Karsten 'quaid' Wade" <kwade at redhat.com>, "Robyn Bergeron" <rbergero at redhat.com>
> Sent: Wednesday, January 11, 2012 11:51:09 AM
> Subject: Call for oVirt subproject release note beats!
> 
> Hi all,
> 
> If you are getting this email you are listed as the first maintainer
> of an oVirt subproject at http://www.ovirt.org/project/subprojects/.
> As we ramp up towards our initial formal release of the oVirt
> project we were hoping that you could provide a short run down of
> what your subproject is, and a brief blurb on any noteworthy
> features/resolved issues/known issues in it for this initial
> release. If you have bugzilla #s to include even better!
> 
> This effort would assist us greatly in providing a release notes
> document for this initial release. Please add your input to the
> relevant section of this page on the wiki:
> 
> http://www.ovirt.org/wiki/Release_Notes
> 
> Note that the structure I have provided is just to be used as a guide
> for now, once we have see what we have we can discuss further and
> reformat appropriately.
> 
> Thanks!
> 
> Steve


From sgordon at redhat.com  Mon Jan 16 16:45:10 2012
From: sgordon at redhat.com (Steve Gordon)
Date: Mon, 16 Jan 2012 11:45:10 -0500 (EST)
Subject: [Users] oVirt test day is coming - Jan 16th - Deferred to Jan	18th
In-Reply-To: <4F144049.3020907@redhat.com>
Message-ID: <ba1a7cee-4636-439f-8018-4ffe5a8ac6c6@zmail15.collab.prod.int.phx2.redhat.com>



----- Original Message -----
> From: "Moran Goldboim" <mgoldboi at redhat.com>
> To: "Anthony Liguori" <anthony at codemonkey.ws>
> Cc: announce at ovirt.org, arch at ovirt.org, users at ovirt.org
> Sent: Monday, January 16, 2012 10:20:41 AM
> Subject: Re: [Users] oVirt test day is coming - Jan 16th - Deferred to Jan	18th
> 
> On 01/16/2012 03:36 PM, Anthony Liguori wrote:
> > On 01/15/2012 09:36 AM, Moran Goldboim wrote:
> >> Due to a late re-base we have decided to defer the testday in 2
> >> days to
> >> Wednesday Jan 18th.
> >> Sorry for the late notice, hope to see you all there.
> >
> > Not that I mind the test day being moved, but how was it decided to
> > move the test day?  I don't see any discussion on any of the
> > various
> > lists (at list, that I'm on).
> >
> > We are planning on participating and would have liked to provide
> > some
> > input in the decision.
> >
> > Regards,
> >
> > Anthony Liguori
> 
> Anthony, this issue has been discussed at oVirt Weekly Sync Meeting
> on
> Jan 11th, in which it was decided that if a late branching will
> happen
> testday will be deferred by one or two days.
> 
> Moran.

Note: For those who don't attend the meetings minutes get sent to board at ovirt.org (possibly other lists as well). The minutes from that particular meeting are here:

http://ovirt.org/meetings/ovirt/2012/ovirt.2012-01-11-15.01.html

Thanks,

Steve


From kwade at redhat.com  Mon Jan 16 18:19:36 2012
From: kwade at redhat.com (Karsten 'quaid' Wade)
Date: Mon, 16 Jan 2012 10:19:36 -0800
Subject: [Users] oVirt test day is coming - Jan 16th - Deferred to Jan 18th
In-Reply-To: <ba1a7cee-4636-439f-8018-4ffe5a8ac6c6@zmail15.collab.prod.int.phx2.redhat.com>
References: <ba1a7cee-4636-439f-8018-4ffe5a8ac6c6@zmail15.collab.prod.int.phx2.redhat.com>
Message-ID: <4F146A38.6030006@redhat.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 01/16/2012 08:45 AM, Steve Gordon wrote:
> 
> Note: For those who don't attend the meetings minutes get sent to 
> board at ovirt.org (possibly other lists as well). The minutes from
> that particular meeting are here:
> 
> http://ovirt.org/meetings/ovirt/2012/ovirt.2012-01-11-15.01.html

That said, in the future we should go an extra few steps beyond the
minutes when a schedule is changed in a meeting. A separate email
should go out to arch@ about the schedule change, with a link to the
relevant meeting minutes.

This is why people say, "It's not a decision if it's not on the
mailing list."[1]

- - Karsten

[1] >
https://www.theopensourceway.org/wiki/Stuff_everyone_knows_and_forgets_anyway#Take_even_more_care_to_do_all_design_decisions_in_the_open

- -- 
name:  Karsten 'quaid' Wade, Sr. Community Architect
team:    Red Hat Community Architecture & Leadership
uri:              http://communityleadershipteam.org
                         http://TheOpenSourceWay.org
gpg:                                        AD0E0C41
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iD8DBQFPFGo42ZIOBq0ODEERAkaQAKCX1wuyX0GFTqC8/pVb6eg/s8qZ3QCffb3t
OhRezGQLmsFyiLrgUCB7w0Y=
=2IGa
-----END PGP SIGNATURE-----


From anthony at codemonkey.ws  Mon Jan 16 19:27:15 2012
From: anthony at codemonkey.ws (Anthony Liguori)
Date: Mon, 16 Jan 2012 13:27:15 -0600
Subject: [Users] oVirt test day is coming - Jan 16th - Deferred to Jan 18th
In-Reply-To: <4F146A38.6030006@redhat.com>
References: <ba1a7cee-4636-439f-8018-4ffe5a8ac6c6@zmail15.collab.prod.int.phx2.redhat.com>
	<4F146A38.6030006@redhat.com>
Message-ID: <4F147A13.3010808@codemonkey.ws>

On 01/16/2012 12:19 PM, Karsten 'quaid' Wade wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 01/16/2012 08:45 AM, Steve Gordon wrote:
>>
>> Note: For those who don't attend the meetings minutes get sent to
>> board at ovirt.org (possibly other lists as well). The minutes from
>> that particular meeting are here:
>>
>> http://ovirt.org/meetings/ovirt/2012/ovirt.2012-01-11-15.01.html
>
> That said, in the future we should go an extra few steps beyond the
> minutes when a schedule is changed in a meeting. A separate email
> should go out to arch@ about the schedule change, with a link to the
> relevant meeting minutes.
>
> This is why people say, "It's not a decision if it's not on the
> mailing list."[1]

Ack.  I was trying to think of the right way to say this and this captures it 
perfectly :-)

Thanks,

Anthony Liguori

>
> - - Karsten
>
> [1]>
> https://www.theopensourceway.org/wiki/Stuff_everyone_knows_and_forgets_anyway#Take_even_more_care_to_do_all_design_decisions_in_the_open
>
> - --
> name:  Karsten 'quaid' Wade, Sr. Community Architect
> team:    Red Hat Community Architecture&  Leadership
> uri:              http://communityleadershipteam.org
>                           http://TheOpenSourceWay.org
> gpg:                                        AD0E0C41
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.11 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iD8DBQFPFGo42ZIOBq0ODEERAkaQAKCX1wuyX0GFTqC8/pVb6eg/s8qZ3QCffb3t
> OhRezGQLmsFyiLrgUCB7w0Y=
> =2IGa
> -----END PGP SIGNATURE-----
> _______________________________________________
> Arch mailing list
> Arch at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/arch



From kwade at redhat.com  Mon Jan 16 22:09:33 2012
From: kwade at redhat.com (Karsten 'quaid' Wade)
Date: Mon, 16 Jan 2012 14:09:33 -0800
Subject: [Users] oVirt test day is coming - Jan 16th - Deferred to Jan 18th
In-Reply-To: <4F147A13.3010808@codemonkey.ws>
References: <ba1a7cee-4636-439f-8018-4ffe5a8ac6c6@zmail15.collab.prod.int.phx2.redhat.com>
	<4F146A38.6030006@redhat.com> <4F147A13.3010808@codemonkey.ws>
Message-ID: <4F14A01D.50403@redhat.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 01/16/2012 11:27 AM, Anthony Liguori wrote:
> 
> Ack.  I was trying to think of the right way to say this and this 
> captures it perfectly :-)

Yeah, and honestly, it's something I could have thought of to do as
meeting chair, too. Oh, well, no worries, we're all learning.

- - Karsten
- -- 
name:  Karsten 'quaid' Wade, Sr. Community Architect
team:    Red Hat Community Architecture & Leadership
uri:              http://communityleadershipteam.org
                         http://TheOpenSourceWay.org
gpg:                                        AD0E0C41
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iD8DBQFPFKAd2ZIOBq0ODEERAhRHAKDAXefMr2DViWQFMqUHlsSu/ZShwACfaAh0
vNdttMwTXKNTZFWCZpx5GFU=
=IeyX
-----END PGP SIGNATURE-----


From mgoldboi at redhat.com  Tue Jan 17 18:15:40 2012
From: mgoldboi at redhat.com (Moran Goldboim)
Date: Tue, 17 Jan 2012 20:15:40 +0200
Subject: oVirt test day is coming tomorrow -  Jan 18th - Reminder
Message-ID: <4F15BACC.6070002@redhat.com>

All are invited to join and share your ideas, tests, and results.
all details available at http://www.ovirt.org/wiki/Testing/OvirtTestDay


IRC - #ovirt at irc.oftc.net

hope to see you there.
Moran.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/arch/attachments/20120117/c64e5966/attachment.html>

From mgoldboi at redhat.com  Thu Jan 19 09:26:46 2012
From: mgoldboi at redhat.com (Moran Goldboim)
Date: Thu, 19 Jan 2012 11:26:46 +0200
Subject: oVirt test day summery
Message-ID: <4F17E1D6.2020007@redhat.com>

I would like to thank all who has participated the oVirt test day below 
are some of the observation seen during the test day 
(http://www.ovirt.org/wiki/Testing/OvirtTestDay).

    * Participation -
          o Participation was mainly from Redhat, i have seen some
            mailing list activity which involved some non-redhats but
            all 30 bugs opened were by Redhats (28 by Rhevm QE). I was
            disappointed that not to many developers taking an active
            part in the testing.
          o It would be nice to hear some outside opinions on first
            encounter with oVirt from the community
    * Bugs found:
          o total of 30 bugs were found on ovirt - http://bit.ly/AAqM6A
          o Bugs per component:
                + ovirt-engine-webadmin - 12 Bugs
                + ovirt-engine-installer - 4 Bugs
                + ovirt-engine-cli - 4 Bugs
                + ovirt-engine-config - 2 Bugs
                + ovirt-engine-core - 3 Bugs
                + ovirt-engine-sdk - 2 Bugs
                + vdsm - 2 Bugs
                + ovirt-engine-api - 1 Bug
    * Component status - components are working as expected on basic
      operations, except ovirt-engine-cli in which some basic flows are
      broken.
          o tools weren't tested


I think that all after all we have a stable candidate for first ovirt 
version Jan 31th.

Thanks again,
Moran.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/arch/attachments/20120119/2bf003a6/attachment.html>

From sgordon at redhat.com  Tue Jan 24 19:53:47 2012
From: sgordon at redhat.com (Steve Gordon)
Date: Tue, 24 Jan 2012 14:53:47 -0500 (EST)
Subject: Call for oVirt subproject release note beats!
In-Reply-To: <8fa1a6b7-c39a-45a4-8cd6-9be6ac0d6faa@zmail15.collab.prod.int.phx2.redhat.com>
Message-ID: <ba9c7a2c-7cba-4a70-9a81-4b0d3f137ae5@zmail15.collab.prod.int.phx2.redhat.com>

Hi all,

Assuming we are still on schedule for a release this is the last call for release note items. We will discuss further in the weekly sync up meeting tomorrow.

Steve

----- Original Message -----
> From: "Steve Gordon" <sgordon at redhat.com>
> To: arch at ovirt.org
> Sent: Monday, January 16, 2012 10:34:01 AM
> Subject: Re: Call for oVirt subproject release note beats!
> 
> Hi all,
> 
> As discussed in last week's sync-up meeting I emailed the
> contributors listed as oVirt subproject maintainers requesting
> release note beats. So far only the oVirt engine section of the
> release notes page has been populated (thanks Livnat!). The release
> notes page is here:
> 
>     http://www.ovirt.org/wiki/Release_Notes
> 
> Please take the time to update it with any features, resolved issues,
> or known issues you are aware of that you think should be noted for
> this first release of oVirt. Even one liners or a link to the
> relevant feature page/bugzilla would be great, I intend to edit this
> into a cohesive document before the actual release.
> 
> Thanks,
> 
> Steve
> 
> ----- Original Message -----
> > From: "Steve Gordon" <sgordon at redhat.com>
> > To: "Michael Pasternak" <mpastern at redhat.com>, "Einav Cohen"
> > <ecohen at redhat.com>, "Itamar Heim" <iheim at redhat.com>,
> > "Barak Azulay" <bazulay at redhat.com>, "Yaniv Dary"
> > <ydary at redhat.com>, "Ofer Schreiber" <oschreib at redhat.com>, "Alan
> > Pevec" <apevec at redhat.com>, "Livnat Peer" <lpeer at redhat.com>, "Ayal
> > Baron" <abaron at redhat.com>
> > Cc: "Karsten 'quaid' Wade" <kwade at redhat.com>, "Robyn Bergeron"
> > <rbergero at redhat.com>
> > Sent: Wednesday, January 11, 2012 11:51:09 AM
> > Subject: Call for oVirt subproject release note beats!
> > 
> > Hi all,
> > 
> > If you are getting this email you are listed as the first
> > maintainer
> > of an oVirt subproject at
> > http://www.ovirt.org/project/subprojects/.
> > As we ramp up towards our initial formal release of the oVirt
> > project we were hoping that you could provide a short run down of
> > what your subproject is, and a brief blurb on any noteworthy
> > features/resolved issues/known issues in it for this initial
> > release. If you have bugzilla #s to include even better!
> > 
> > This effort would assist us greatly in providing a release notes
> > document for this initial release. Please add your input to the
> > relevant section of this page on the wiki:
> > 
> > http://www.ovirt.org/wiki/Release_Notes
> > 
> > Note that the structure I have provided is just to be used as a
> > guide
> > for now, once we have see what we have we can discuss further and
> > reformat appropriately.
> > 
> > Thanks!
> > 
> > Steve
> 


From kwade at redhat.com  Tue Jan 24 20:09:21 2012
From: kwade at redhat.com (Karsten 'quaid' Wade)
Date: Tue, 24 Jan 2012 12:09:21 -0800
Subject: Call for oVirt subproject release note beats!
In-Reply-To: <ba9c7a2c-7cba-4a70-9a81-4b0d3f137ae5@zmail15.collab.prod.int.phx2.redhat.com>
References: <ba9c7a2c-7cba-4a70-9a81-4b0d3f137ae5@zmail15.collab.prod.int.phx2.redhat.com>
Message-ID: <4F1F0FF1.1050607@redhat.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 01/24/2012 11:53 AM, Steve Gordon wrote:
> Hi all,
> 
> Assuming we are still on schedule for a release this is the last
> call for release note items. We will discuss further in the weekly
> sync up meeting tomorrow.

Have we been getting sufficient information from the various member
projects for the release notes?

- - Karsten
- -- 
name:  Karsten 'quaid' Wade, Sr. Community Architect
team:    Red Hat Community Architecture & Leadership
uri:              http://communityleadershipteam.org
                         http://TheOpenSourceWay.org
gpg:                                        AD0E0C41
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iD8DBQFPHw/x2ZIOBq0ODEERAnA0AKCTErXHcwuvt0XgSpAJHWMqhSOpcwCglzjs
AiRBuiGIki5yp6QtObZnQR4=
=e1R7
-----END PGP SIGNATURE-----


From sgordon at redhat.com  Tue Jan 24 21:05:29 2012
From: sgordon at redhat.com (Steve Gordon)
Date: Tue, 24 Jan 2012 16:05:29 -0500 (EST)
Subject: Call for oVirt subproject release note beats!
In-Reply-To: <4F1F0FF1.1050607@redhat.com>
Message-ID: <664b7db9-13e0-4e5d-8fcc-1f5cff825bd7@zmail15.collab.prod.int.phx2.redhat.com>

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On 01/24/2012 11:53 AM, Steve Gordon wrote:
> > Hi all,
> > 
> > Assuming we are still on schedule for a release this is the last
> > call for release note items. We will discuss further in the weekly
> > sync up meeting tomorrow.
> 
> Have we been getting sufficient information from the various member
> projects for the release notes?

At this time the Wiki has only been updated by maintainers of the SDK, CLI, and Engine subprojects. Even of those I am of the belief that only the Engine section provides enough information to provide a meaningful release note. Barring further updates I will be getting my creative writing hat on...you have all been warned ;p.

Steve


From sdake at redhat.com  Wed Jan 25 18:31:41 2012
From: sdake at redhat.com (Steven Dake)
Date: Wed, 25 Jan 2012 11:31:41 -0700
Subject: Fedora package sponsorship
Message-ID: <4F204A8D.4080403@redhat.com>

Hi,

I see some package review requests coming in for ovirt on the Fedora
cloud sig, and I know there are more in the pipe.  I offer to act as a
sponsor for your project's packagers.

The job of a Fedora sponsor is:
1. Make sure the sponsored packager absolutely understands the Fedora
   packaging guidelines
2. Validate that the packager understands the review process and can
   review other people's packages
3. Answer your questions after you have become a packager when your are
   blocked by a package review

After being accepted into the packager group, there is a general
expectation the new packager will help other people package software by
reviewing other packager's review request bugzillas.

To meet #1 and #2 requirements above, I have a general expectation that
packagers will review other people's packages and essentially show they
are effective in packaging and review process before reviewing your
actual packages.

To help move that along, rather then submitting a package to Fedora for
review, and then blocking for 4-6 weeks while the prospective packager
learns the ropes, I'd suggest learning the ropes and then submit packages.

The more packagers, the slower the process will be (to train 10 people
takes more time then to train 2-3).

I'd suggest working together as a community to identify who you would
like to act as Fedora packagers for ovirt.  Once that step is done, each
individual person can contact me offlist for next steps to becoming a
packager.

Regards
-steve


From jbrooks at redhat.com  Thu Jan 26 00:53:46 2012
From: jbrooks at redhat.com (Jason Brooks)
Date: Wed, 25 Jan 2012 16:53:46 -0800
Subject: oVirt slide decks & other collateral
Message-ID: <4F20A41A.5020306@redhat.com>

I've created marketing and marketing/collateral categories on the 
ovirt.org wiki, and started a page listing the slide decks that we have 
for the project so far: http://www.ovirt.org/wiki/OVirt_Slide_Decks.

At the top of the page I've linked to a new, generic ovirt deck, 
assembled out of the other decks, meant to be used for project 
overview-type presentations.

Karsten Wade used a version of this generic deck for his recent talk at 
SCALE: http://www.ovirt.org/wiki/User:Quaid/SCALE_10x_presentation. His 
version spreads the text out over multiple slides to combat the dense 
"wall of text" effect on some of these.

To a similar end, I'm working on thinning out some of these slides, as 
well as adding screenshots from the current version of the code, and 
making some of the diagrams less Red Hat-centric.

If you have other feedback on this deck, or suggestions/requests for 
other pieces of collateral the project could benefit from, please let me 
know, and/or add to the wiki under the relevant categories.

Thanks, Jason


From oschreib at redhat.com  Thu Jan 26 09:47:17 2012
From: oschreib at redhat.com (Ofer Schreiber)
Date: Thu, 26 Jan 2012 11:47:17 +0200
Subject: First release go/no go meeting on Monday (30.01)
Message-ID: <4F212125.1060207@redhat.com>

All,

As decided in the last oVirt sync meeting, we will have a go/no meeting 
about our first release in the upcoming Monday (30.01.12), 15:00 UTC.

I'm inviting you all to join this important meeting in the official 
#ovirt irc channel.

Thanks,

Ofer Schreiber
oVirt Release Manager


From pmyers at redhat.com  Thu Jan 26 16:54:20 2012
From: pmyers at redhat.com (Perry Myers)
Date: Thu, 26 Jan 2012 11:54:20 -0500
Subject: oVirt slide decks & other collateral
In-Reply-To: <4F20A41A.5020306@redhat.com>
References: <4F20A41A.5020306@redhat.com>
Message-ID: <4F21853C.7090801@redhat.com>

On 01/25/2012 07:53 PM, Jason Brooks wrote:
> I've created marketing and marketing/collateral categories on the
> ovirt.org wiki, and started a page listing the slide decks that we have
> for the project so far: http://www.ovirt.org/wiki/OVirt_Slide_Decks.
> 
> At the top of the page I've linked to a new, generic ovirt deck,
> assembled out of the other decks, meant to be used for project
> overview-type presentations.

Hi,

Thanks, that's a good overview deck.  But one suggestion...

Perhaps it would be good to add in some slides here that show off the UI
a little more?  Not necessarily a deep dive into the oVirt Engine but at
least some general concepts like showing how things are organized
(datacenter, cluster, storage domain) and showing some basic workflows.
 That might make things a little more concrete/tangible for folks
listening to this presentation.

Right now the presentation is very high level, and for technical
audiences (like we'd see at conferences like FOSDEM, FUDcon, etc)
there's not enough meat in there to capture the attention of potential
contributors.

Make sense?

Perry

> Karsten Wade used a version of this generic deck for his recent talk at
> SCALE: http://www.ovirt.org/wiki/User:Quaid/SCALE_10x_presentation. His
> version spreads the text out over multiple slides to combat the dense
> "wall of text" effect on some of these.
> 
> To a similar end, I'm working on thinning out some of these slides, as
> well as adding screenshots from the current version of the code, and
> making some of the diagrams less Red Hat-centric.
> 
> If you have other feedback on this deck, or suggestions/requests for
> other pieces of collateral the project could benefit from, please let me
> know, and/or add to the wiki under the relevant categories.
> 
> Thanks, Jason
> _______________________________________________
> Arch mailing list
> Arch at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/arch



From jbrooks at redhat.com  Thu Jan 26 17:16:21 2012
From: jbrooks at redhat.com (Jason Brooks)
Date: Thu, 26 Jan 2012 09:16:21 -0800
Subject: oVirt slide decks & other collateral
In-Reply-To: <4F21853C.7090801@redhat.com>
References: <4F20A41A.5020306@redhat.com> <4F21853C.7090801@redhat.com>
Message-ID: <4F218A65.1040105@redhat.com>

> Perhaps it would be good to add in some slides here that show off the UI
> a little more?  Not necessarily a deep dive into the oVirt Engine but at
> least some general concepts like showing how things are organized
> (datacenter, cluster, storage domain) and showing some basic workflows.

That's a great suggestion, and a slide deck like this is a great place 
to provide illustrations. I will add them.

Jason


From jbrooks at redhat.com  Thu Jan 26 18:24:57 2012
From: jbrooks at redhat.com (Jason Brooks)
Date: Thu, 26 Jan 2012 10:24:57 -0800
Subject: oVirt slide decks & other collateral
In-Reply-To: <4F2198D8.1060109@redhat.com>
References: <4F20A41A.5020306@redhat.com> <4F21853C.7090801@redhat.com>
	<4F218A65.1040105@redhat.com> <4F2198D8.1060109@redhat.com>
Message-ID: <4F219A79.5090503@redhat.com>

On 01/26/2012 10:18 AM, Perry Myers wrote:
> On 01/26/2012 12:16 PM, Jason Brooks wrote:
>>> Perhaps it would be good to add in some slides here that show off the UI
>>> a little more?  Not necessarily a deep dive into the oVirt Engine but at
>>> least some general concepts like showing how things are organized
>>> (datacenter, cluster, storage domain) and showing some basic workflows.
>>
>> That's a great suggestion, and a slide deck like this is a great place
>> to provide illustrations. I will add them.
>
> Just to be clear, not just diagrams but actual screen shots of the oVirt
> Engine UI are what I was after.  (Though more diagrams is good too)

Yep, that's what I understood you to mean. Screen shots.


From pmyers at redhat.com  Thu Jan 26 18:18:00 2012
From: pmyers at redhat.com (Perry Myers)
Date: Thu, 26 Jan 2012 13:18:00 -0500
Subject: oVirt slide decks & other collateral
In-Reply-To: <4F218A65.1040105@redhat.com>
References: <4F20A41A.5020306@redhat.com> <4F21853C.7090801@redhat.com>
	<4F218A65.1040105@redhat.com>
Message-ID: <4F2198D8.1060109@redhat.com>

On 01/26/2012 12:16 PM, Jason Brooks wrote:
>> Perhaps it would be good to add in some slides here that show off the UI
>> a little more?  Not necessarily a deep dive into the oVirt Engine but at
>> least some general concepts like showing how things are organized
>> (datacenter, cluster, storage domain) and showing some basic workflows.
> 
> That's a great suggestion, and a slide deck like this is a great place
> to provide illustrations. I will add them.

Just to be clear, not just diagrams but actual screen shots of the oVirt
Engine UI are what I was after.  (Though more diagrams is good too)


From jchoate at redhat.com  Fri Jan 27 13:37:44 2012
From: jchoate at redhat.com (Jon Choate)
Date: Fri, 27 Jan 2012 08:37:44 -0500 (EST)
Subject: [Engine-devel] First release go/no go meeting on Monday (30.01)
In-Reply-To: <4F212125.1060207@redhat.com>
Message-ID: <b9545daf-8d94-4487-8274-b36b1ecb606c@zmail15.collab.prod.int.phx2.redhat.com>

Will there be a formal release vote (3 +1's) in this meeting? 

Also,I don't see a link on the site for a release candidate. 
Is there one available so the release can be evaluated/tested before deciding on the go/no-go?

----- Original Message -----
> From: "Ofer Schreiber" <oschreib at redhat.com>
> To: board at ovirt.org, arch at ovirt.org, engine-devel at ovirt.org
> Sent: Thursday, January 26, 2012 4:47:17 AM
> Subject: [Engine-devel] First release go/no go meeting on Monday (30.01)
> 
> All,
> 
> As decided in the last oVirt sync meeting, we will have a go/no
> meeting
> about our first release in the upcoming Monday (30.01.12), 15:00 UTC.
> 
> I'm inviting you all to join this important meeting in the official
> #ovirt irc channel.
> 
> Thanks,
> 
> Ofer Schreiber
> oVirt Release Manager
> _______________________________________________
> Engine-devel mailing list
> Engine-devel at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/engine-devel
> 


From oschreib at redhat.com  Sun Jan 29 08:53:46 2012
From: oschreib at redhat.com (Ofer Schreiber)
Date: Sun, 29 Jan 2012 10:53:46 +0200
Subject: [Engine-devel] First release go/no go meeting on Monday (30.01)
In-Reply-To: <b9545daf-8d94-4487-8274-b36b1ecb606c@zmail15.collab.prod.int.phx2.redhat.com>
References: <b9545daf-8d94-4487-8274-b36b1ecb606c@zmail15.collab.prod.int.phx2.redhat.com>
Message-ID: <4F25091A.6070101@redhat.com>

On 01/27/2012 03:37 PM, Jon Choate wrote:
> Will there be a formal release vote (3 +1's) in this meeting?
>
> Also,I don't see a link on the site for a release candidate.
> Is there one available so the release can be evaluated/tested before deciding on the go/no-go?

Since this is our first release, we're still trying to produce a formal 
release process.

Although we didn't talk about a formal release vote, that sounds like 
the general intention of the go/no go meeting.

I'll send a separate mail about  a formal RC.

>
> ----- Original Message -----
>> From: "Ofer Schreiber"<oschreib at redhat.com>
>> To: board at ovirt.org, arch at ovirt.org, engine-devel at ovirt.org
>> Sent: Thursday, January 26, 2012 4:47:17 AM
>> Subject: [Engine-devel] First release go/no go meeting on Monday (30.01)
>>
>> All,
>>
>> As decided in the last oVirt sync meeting, we will have a go/no
>> meeting
>> about our first release in the upcoming Monday (30.01.12), 15:00 UTC.
>>
>> I'm inviting you all to join this important meeting in the official
>> #ovirt irc channel.
>>
>> Thanks,
>>
>> Ofer Schreiber
>> oVirt Release Manager
>> _______________________________________________
>> Engine-devel mailing list
>> Engine-devel at ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/engine-devel
>>



From cctrieloff at redhat.com  Mon Jan 30 20:05:04 2012
From: cctrieloff at redhat.com (Carl Trieloff)
Date: Mon, 30 Jan 2012 15:05:04 -0500
Subject: going to FOSDEM?
Message-ID: <4F26F7F0.7080103@redhat.com>


Take some pictures of the sessions and let's post them and the talks to
the site.

Carl.