5:18 p.m.
The oVirt Project is pleased to announce the availability of the first Alpha release of
oVirt 3.6 for testing, as of May 20, 2015.
oVirt is an open source alternative to VMware vSphere, and provides an excellent KVM
management interface for multi-node virtualization.
The Alpha release is available now for Fedora 20,
Red Hat Enterprise Linux 6.6, CentOS 6.6 (or similar) and
Red Hat Enterprise Linux 7.1, CentOS 7.1 (or similar).
The Alpha release can also be deployed on Hypervisor Hosts running Fedora 21 and Fedora
22.
This Alpha release of oVirt includes numerous bug fixes.
See the release notes [1] for an initial list of the new features and bugs fixed.
Please refer to release notes [1] for Installation / Upgrade instructions.
A new oVirt Live ISO and Node ISO will be available soon[2].
Please note that mirrors[3] may need usually one day before being synchronized.
Please refer to the release notes for known issues in this release.
[1] http://www.ovirt.org/OVirt_3.6_Release_Notes
[2] http://resources.ovirt.org/pub/ovirt-3.6-pre/iso/
[3] http://www.ovirt.org/Repository_mirrors#Current_mirrors
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
10:33 p.m.
New subject: Possible documentation fixes - advice needed
Hi all-
I am new to this, so please bear with me. I was researching oVirt, looking for information
on "developer guidelines," and I found some, but they weren't all connected
or linked iin from the same page.
I think I can fix that (and I've been given wiki permissions), but I want to make sure
I'm not doing something really stupid before I do.
What I think should happen is that this page:
http://www.ovirt.org/Backend_Coding_Standards
should have links to the following pages on it:
* http://www.ovirt.org/Vdsm_Coding_Guidelines
* http://www.ovirt.org/Infra_Bash_style_guide
* http://www.ovirt.org/Community_guidelines#Code_submission_guidelines
* http://www.ovirt.org/Building_oVirt_Engine/IDE --> see section about engine and
Checkstyle: "Make sure that you import the engine code formatter into eclipse before
starting development. The engine maven build uses checkstyle to check coding standards.
One of the standards checked is that the code should not contain tabs or trailing
whitespaces. Since eclipse inserts tabs by default for code formatting, you can end up
with a lot of compilation errors in command line maven build if you don't follow this
(and the next) step."
And this page: http://www.ovirt.org/DevProcess should have a link to
http://www.ovirt.org/Backend_Coding_Standards on it
If I don't hear from anyone, I'll make these changes on Friday. If I have it
wrong, tell me so and I won't make the changes.
Thanks!
-gina
-----
Gina Likins
University Outreach
Open Source and Standards
11S133, Red Hat Tower
100 E. Davie St.; Raleigh, NC 27601
glikins(a)redhat.com
(919)890-8322 or internally 48322
----
11:59 p.m.
New subject: Possible documentation fixes - advice needed
Hello Gina,
On 05/20/2015 03:33 PM, Gina Likins wrote:
Hi all-
I am new to this, so please bear with me. I was researching oVirt, looking for
information on "developer guidelines," and I found some, but they weren't
all connected or linked iin from the same page.
I think I can fix that (and I've been given wiki permissions), but I want to make
sure I'm not doing something really stupid before I do.
What I think should happen is that this page:
http://www.ovirt.org/Backend_Coding_Standards
should have links to the following pages on it:
* http://www.ovirt.org/Vdsm_Coding_Guidelines
* http://www.ovirt.org/Infra_Bash_style_guide
* http://www.ovirt.org/Community_guidelines#Code_submission_guidelines
* http://www.ovirt.org/Building_oVirt_Engine/IDE --> see section about engine and
Checkstyle: "Make sure that you import the engine code formatter into eclipse before
starting development. The engine maven build uses checkstyle to check coding standards.
One of the standards checked is that the code should not contain tabs or trailing
whitespaces. Since eclipse inserts tabs by default for code formatting, you can end up
with a lot of compilation errors in command line maven build if you don't follow this
(and the next) step."
And this page: http://www.ovirt.org/DevProcess should have a link to
http://www.ovirt.org/Backend_Coding_Standards on it
If I don't hear from anyone, I'll make these changes on Friday. If I have it
wrong, tell me so and I won't make the changes.
From my point of view, looks good, the wiki is there to document the
project and to be updated as soon someone finds the need of improvement.
Specially, if this change will help others. I would say: fell free to
improve adding links to related topic, if someone believes it could be
in better shape, they can always improve based on your last
improvements. Without mention that wiki have the history recorded to
easily recover.
Have fun!
--
Cheers
Douglas
1:30 a.m.
New subject: Possible documentation fixes - advice needed
+1. Have at it.
We're sorely lacking in "I'm new here! How can I help?" type
documentation.
I've wanted to create a "Getting Started" type sequence for a while. Having
mentored two people up on the project, I had to do a lot of talking and not
enough pointing to documents.
----- Original Message -----
From: "Douglas Schilling Landgraf"
<dougsland(a)redhat.com>
To: "Gina Likins" <glikins(a)redhat.com>, devel(a)ovirt.org
Sent: Wednesday, May 20, 2015 4:59:46 PM
Subject: Re: [ovirt-devel] Possible documentation fixes - advice needed
Hello Gina,
On 05/20/2015 03:33 PM, Gina Likins wrote:
> Hi all-
>
> I am new to this, so please bear with me. I was researching oVirt, looking
> for information on "developer guidelines," and I found some, but they
> weren't all connected or linked iin from the same page.
>
> I think I can fix that (and I've been given wiki permissions), but I want
> to make sure I'm not doing something really stupid before I do.
>
> What I think should happen is that this page:
>
> http://www.ovirt.org/Backend_Coding_Standards
>
> should have links to the following pages on it:
> * http://www.ovirt.org/Vdsm_Coding_Guidelines
> * http://www.ovirt.org/Infra_Bash_style_guide
> * http://www.ovirt.org/Community_guidelines#Code_submission_guidelines
> * http://www.ovirt.org/Building_oVirt_Engine/IDE --> see section about
> engine and Checkstyle: "Make sure that you import the engine code
> formatter into eclipse before starting development. The engine maven build
> uses checkstyle to check coding standards. One of the standards checked is
> that the code should not contain tabs or trailing whitespaces. Since
> eclipse inserts tabs by default for code formatting, you can end up with a
> lot of compilation errors in command line maven build if you don't follow
> this (and the next) step."
>
> And this page: http://www.ovirt.org/DevProcess should have a link to
> http://www.ovirt.org/Backend_Coding_Standards on it
>
> If I don't hear from anyone, I'll make these changes on Friday. If I have
> it wrong, tell me so and I won't make the changes.
>
>
From my point of view, looks good, the wiki is there to document the
project and to be updated as soon someone finds the need of improvement.
Specially, if this change will help others. I would say: fell free to
improve adding links to related topic, if someone believes it could be
in better shape, they can always improve based on your last
improvements. Without mention that wiki have the history recorded to
easily recover.
Have fun!
--
Cheers
Douglas
_______________________________________________
Devel mailing list
Devel(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
9:23 a.m.
New subject: Possible documentation fixes - advice needed
Il 20/05/2015 21:33, Gina Likins ha scritto:
Hi all-
I am new to this, so please bear with me. I was researching oVirt, looking for
information on "developer guidelines," and I found some, but they weren't
all connected or linked iin from the same page.
I think I can fix that (and I've been given wiki permissions), but I want to make
sure I'm not doing something really stupid before I do.
What I think should happen is that this page:
http://www.ovirt.org/Backend_Coding_Standards
should have links to the following pages on it:
* http://www.ovirt.org/Vdsm_Coding_Guidelines
* http://www.ovirt.org/Infra_Bash_style_guide
* http://www.ovirt.org/Community_guidelines#Code_submission_guidelines
* http://www.ovirt.org/Building_oVirt_Engine/IDE --> see section about engine and
Checkstyle: "Make sure that you import the engine code formatter into eclipse before
starting development. The engine maven build uses checkstyle to check coding standards.
One of the standards checked is that the code should not contain tabs or trailing
whitespaces. Since eclipse inserts tabs by default for code formatting, you can end up
with a lot of compilation errors in command line maven build if you don't follow this
(and the next) step."
And this page: http://www.ovirt.org/DevProcess should have a link to
http://www.ovirt.org/Backend_Coding_Standards on it
If I don't hear from anyone, I'll make these changes on Friday. If I have it
wrong, tell me so and I won't make the changes.
+1, please do :-)
Thanks!
-gina
-----
Gina Likins
University Outreach
Open Source and Standards
11S133, Red Hat Tower
100 E. Davie St.; Raleigh, NC 27601
glikins(a)redhat.com
(919)890-8322 or internally 48322
----
_______________________________________________
Devel mailing list
Devel(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
3475
days inactive
3476
days old
4 comments
4 participants
participants (4)
-
Douglas Schilling Landgraf -
Gina Likins -
Greg Sheremeta -
Sandro Bonazzola