[PROPOSAL] a calendar for oVirt builds and releases

[Roy Golan]

On 02/18/2014 02:28 PM, Eyal Edri wrote:
>
> ----- Original Message -----
>> From: "Vojtech Szocs" <vszocs at redhat.com>
>> To: "Allon Mureinik" <amureini at redhat.com>
>> Cc: "arch" <arch at ovirt.org>
>> Sent: Tuesday, February 18, 2014 2:00:25 PM
>> Subject: Re: [PROPOSAL] a calendar for oVirt builds and releases
>>
>>
>>
>> ----- Original Message -----
>>> From: "Allon Mureinik" <amureini at redhat.com>
>>> To: "Livnat Peer" <lpeer at redhat.com>
>>> Cc: "arch" <arch at ovirt.org>
>>> Sent: Tuesday, February 18, 2014 8:38:57 AM
>>> Subject: Re: [PROPOSAL] a calendar for oVirt builds and releases
>>>
>>>
>>>
>>> ----- Original Message -----
>>>> From: "Livnat Peer" <lpeer at redhat.com>
>>>> To: "Sandro Bonazzola" <sbonazzo at redhat.com>, "Roy Golan"
>>>> <rgolan at redhat.com>, "arch" <arch at ovirt.org>
>>>> Sent: Tuesday, February 18, 2014 8:51:05 AM
>>>> Subject: Re: [PROPOSAL] a calendar for oVirt builds and releases
>>>>
>>>> On 02/17/2014 05:02 PM, Sandro Bonazzola wrote:
>>>>> Il 17/02/2014 15:06, Roy Golan ha scritto:
>>>>>>
>>>>>> I don't know if this was brought up before, I'm proposing here to
>>>>>> manage
>>>>>> a calendar of the builds and releases of oVirt.
>>>>>>
>>>>>> I personally think that having a calendar instead of digging out the
>>>>>> details from mails is way easier to track and manage -
>>>>>> you get notified, you have aggregated view of events and your
>>>>>> time-slots
>>>>>> so you can plan ahead.
>>>>> +1
>>>>>
>>>>>> While writing it I'm thinking maybe its appropriate to all events we
>>>>>> may
>>>>>> have (test-day etc.)
>>>>>>   
>>>> +1, maybe include events we present at.
>>> A big +1!
>>>
>>> IMHO, a calendar is more than just a way to manage builds, it can be a sort
>>> of "window to what's going on in oVirt", and should aggregate all such
>>> issues:
>>> - builds - weekly, highlighted rc/ga builded
>>> - important dev. date - branch split, feature freeze, code freeze, etc.
>>> - test days
>>> - conventions/workshops either with a note "X is presenting about Y, A is
>>> presenting about B" or "CFP is open - we're looking for people to talk
>>> about
>>> oVirt!"
>> +1
> a calendar is nice to have as long as dates are met for builds & releases.
> right now it's not happening afaik, and almost each release has been postponed due to
> some packages not ready or blocking bugs, so i'm not quite sure how this can be updated in a calendar
> if it's not fixed dates.
> but as for other events it makes sense.
> another option is to release what we have at the date, no matter what - i.e even taking a nightly build
> for the missing pkg, if it's not ready by the release date by the maintainer.
> (sorry if a bit off topic here).

@Eyal - Like mentioned by Eli I think, its still better than not having 
this at all.
if  builds and releases are tentative you could specify in the event 
this fact and people will address that.
Hope you are convinced as per the feedback it seems people are missing that.



>>>>>> This also will be a great fit into ovirt.org front-page.
>>>>>>
>>>>>> thoughts?
>>>>>>
>>>>>> Thanks,
>>>>>> Roy
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Arch mailing list
>>>>>> Arch at ovirt.org
>>>>>> http://lists.ovirt.org/mailman/listinfo/arch
>>>>>
>>>> _______________________________________________
>>>> Arch mailing list
>>>> Arch at ovirt.org
>>>> http://lists.ovirt.org/mailman/listinfo/arch
>>>>
>>> _______________________________________________
>>> Arch mailing list
>>> Arch at ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/arch
>>>
>> _______________________________________________
>> Arch mailing list
>> Arch at ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/arch
>>
> _______________________________________________
> Arch mailing list
> Arch at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/arch