On Thu, Oct 01, 2015 at 02:44:50PM +0200, Sandro Bonazzola wrote:
> Hi,
> We planned to start composing next milestone of oVirt 3.6.0 on *2015-10-12
> 08:00 UTC* from 3.6 branches.
>
> There are still 234 bugs [1] targeted to 3.6.0.
>
> Whiteboard RC GA Total
> docs5 0 15
> dwh
Hi,
We planned to start composing next milestone of oVirt 3.6.0 on *2015-10-12
08:00 UTC* from 3.6 branches.
There are still 234 bugs [1] targeted to 3.6.0.
Whiteboard RC GA Total
docs5 0 15
dwh 1 0 1
external0 1 1
gluster 40 0 40
i18n2 0 2
i
Hi,
We planned to start composing oVirt 3.6.0 RC on *2015-09-16 08:00 UTC* from
3.6 branches.
There are still 855 bugs [1] targeted to 3.6.0.
Maintainers should scrub them and start pushing non critical bugs to
ZStream releases.
There are still 34 bugs marked as blocker:
Bug ID Status Whiteboard
Hi, here's an update on 3.6 status on integration / rel-eng side
Schedule for 3.6.0 has been published[1] and external project schedules have
been updated[2].
The tracker bug for 3.6.0 [3] currently shows no blockers.
There are 561 bugs [4] targeted to 3.6.0.
Excluding node and documentation bu
Hi, here's an update on 3.6 status on integration / rel-eng side
ACTION: Feature proposed for 3.6.0 must now be collected in the 3.6 Google doc
[1] and reviewed by maintainers.
Finished the review process, the remaining key milestones for this release will
be scheduled.
For reference, external
Hi, here's an update on 3.6 status on integration / rel-eng side
ACTION: Feature proposed for 3.6.0 must now be collected in the 3.6 Google doc
[1] and reviewed by maintainers.
Finished the review process, the remaining key milestones for this release will
be scheduled.
For reference, external
Hi, here's an update on 3.6 status on integration / rel-eng side
ACTION: Feature proposed for 3.6.0 must now be collected in the 3.6 Google doc
[1] and reviewed by maintainers.
Finished the review process, the remaining key milestones for this release will
be scheduled.
For reference, external
Hi,
I haven't many news for 3.6 this week:
ACTION: Feature proposed for 3.6.0 must now be collected in the 3.6 Google doc
[1] and reviewed by maintainers.
Finished the review process, the remaining key milestones for this release will
be scheduled.
For reference, external project schedules we'r
Hi,
I haven't many news for 3.6 this week:
ACTION: Feature proposed for 3.6.0 must now be collected in the 3.6 Google doc
[1] and reviewed by maintainers.
Finished the review process, the remaining key milestones for this release will
be scheduled.
For reference, external project schedules we'r
Hi,
I haven't many news for 3.6 this week:
ACTION: Feature proposed for 3.6.0 must now be collected in the 3.6 Google doc
[1] and reviewed by maintainers.
Finished the review process, the remaining key milestones for this release will
be scheduled.
For reference, external project schedules we'r
Hi,
I haven't many news for 3.6 this week:
ACTION: Feature proposed for 3.6.0 must now be collected in the 3.6 Google doc
[1] and reviewed by maintainers.
Finished the review process, the remaining key milestones for this release will
be scheduled.
For reference, external project schedules we'r
Hi,
Release management for 3.6.0 [1] has been updated following the new release
process[2].
ACTION: Feature proposed for 3.6.0 must now be collected in the 3.6 Google doc
[3] and reviewed by maintainers.
Finished the review process, the remaining key milestones for this release will
be schedule
Hi,
Release criteria discussion has been closed and wiki has been updated
accordingly by Brian [1][2].
Release management for 3.6.0 [3] has been updated with the accepted changes in
release criteria.
ACTION: Feature proposed for 3.6.0 must now be collected in the 3.6 Google doc
[4] and review
Il 04/12/2014 09:19, Sven Kieske ha scritto:
>
>
> On 04/12/14 02:24, Robert Story wrote:
>> On Wed, 03 Dec 2014 10:37:19 +0100 Sandro wrote: SB> Two different
>> proposals have been made about above scheduling [3]: SB> 1) extend
>> the cycle to 10 months for allowing to include a large SB> featu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/12/14 02:24, Robert Story wrote:
> On Wed, 03 Dec 2014 10:37:19 +0100 Sandro wrote: SB> Two different
> proposals have been made about above scheduling [3]: SB> 1) extend
> the cycle to 10 months for allowing to include a large SB> feature
> se
On Wed, 03 Dec 2014 10:37:19 +0100 Sandro wrote:
SB> Two different proposals have been made about above scheduling [3]:
SB> 1) extend the cycle to 10 months for allowing to include a large
SB> feature set 2) reduce the cycle to less than 6 months and split
SB> features over 3.6 and 3.7
I'd prefer
Hi,
Release criteria discussion has been closed with last week oVirt sync meeting
[1].
Release management for 3.6.0 [2] will soon be updated with the accepted changes
in release criteria.
The remaining key milestones for this release must now be scheduled.
For reference, external project sched
Il 26/11/2014 11:45, Sven Kieske ha scritto:
> I'm not 100% sure if I understand your definitions:
>
> On 26/11/14 10:26, Sandro Bonazzola wrote:
>> "The alpha phase usually ends with a feature freeze, indicating that no more
>> features will be added to the software. At this time, the software i
I'm not 100% sure if I understand your definitions:
On 26/11/14 10:26, Sandro Bonazzola wrote:
> "The alpha phase usually ends with a feature freeze, indicating that no more
> features will be added to the software. At this time, the software is
> said to be **feature complete**."
>
> So if you
Il 26/11/2014 09:50, Sven Kieske ha scritto:
>
>
> On 26/11/14 09:31, Sandro Bonazzola wrote:
>> If no objections will be raised, the proposed changes [2] will be accepted.
>
> I fear I got an objection:
>
> quote:
>>> * Alpha release should come after feature freeze
>> Nothing more to say abou
On 26/11/14 09:31, Sandro Bonazzola wrote:
> If no objections will be raised, the proposed changes [2] will be accepted.
I fear I got an objection:
quote:
>> * Alpha release should come after feature freeze
> Nothing more to say about it
I really think you are twisting the way what is commonly
Hi,
Release criteria discussion started on 2014-10-22 and will end today 2014-11-26
as discussed in last oVirt sync meeting [1].
If no objections will be raised, the proposed changes [2] will be accepted.
Release management for 3.6.0 has been created [3]
The key milestones for this release must
Hi,
Release criteria discussion started on 2014-10-22 and should have ended last
week as per current release process [1].
Since oVirt sync meeting wasn't held last week, it has been postponed to today
2014-11-19.
Current options are:
1) keeping the same release criteria we had for 3.5 [2]
2) re
Hi,
Release criteria discussion started on 2014-10-22 and should end today as per
current release process [1].
Current options are:
1) keeping the same release criteria we had for 3.5 [2]
2) review the proposed changes [3] and prepare new release criteria for 3.6
Release management for 3.6.0 ha
On 11/05/2014 12:18 PM, Sandro Bonazzola wrote:
Release: 6 months after oVirt 3.5.0 release
I'm still not sure about this one.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Hi,
Release criteria discussion started on 2014-10-22 and should end on 2014-11-12
as per current release process [1].
Current options are:
1) keeping the same release criteria we had for 3.5 [2]
2) review the proposed changes [3] and prepare new release criteria for 3.6
Release management for
Hi,
according to oVirt Release Process [1], a week after the n-1 release is out, a
release criteria for the new release should be discussed.
Release criteria will include MUST items and SHOULD items (held in wiki)
MUST items will DELAY the release in any case.
SHOULD items will include le
27 matches
Mail list logo
