See inline On Thu, 2013-01-10 at 10:07 -0500, Alon Bar-Lev wrote: > Hello All, > > Just to clarify some terms.... as I got some feedback of confusion. > > oVirt is an UPSTREAM project, it is the source origin (manufacturer).
Agreed > > Fedora is a DOWNSTREAM to oVirt, it is a distribution that provides the oVirt > product. Agreed, in general (except for ovirt-node which is an exception) > > Red Hat Enterprise Linux is DOWNSTREAM to oVirt, it is a distribution that > provides the oVirt product. ACK > > Debian is, well, you got the point. > > Fedora (as distribution) is in some sense UPSTREAM to Red Hat Enterprise > Linux, however, this relationship has no impact of oVirt. > > Regards, > Alon Bar-Lev > > ----- Original Message ----- > > From: "Alon Bar-Lev" <[email protected]> > > To: "Mike Burns" <[email protected]> > > Cc: "arch" <[email protected]> > > Sent: Thursday, January 10, 2013 3:11:58 PM > > Subject: Re: [vdsm] ATTN: Project Maintainers: Code Freeze/Branch/Beta > > Build deadlines > > > > Hello Mike and all, > > > > I am little confused with the release engineering of oVirt. > > > > Let me describe what I know about the release engineering of an > > upstream project, and please tell how we are different and why. > > > > 1. Downstream schedules are not relevant to upstream project and vise > > versa. Usually, yes, but we made the call to support F18 as the primary OS for oVirt 3.2. Given that, we couldn't really release 3.2 before F18 was released. > > > > 2. Upstream project releases its sources and optionally binaries in > > milestones. Again, I agree, except for the fact that we're targeting F18 as the primary release we're supporting for 3.2. > > > > 3. Milestone are determine by upstream project and upstream project, > > and has several standard, for example: > > > > package-2.0.0_alpha > > package-2.0.0_alpha1 > > package-2.0.0_beta > > package-2.0.0_beta1 > > package-2.0.0_beta2 > > package-2.0.0_rc > > package-2.0.0_rc1 > > package-2.0.0_rc2 > > package-2.0.0_rc3 > > package-2.0.0_rc4 > > package-2.0.0 > > > > Or: > > > > 1.99.1 > > 1.99.2 > > 1.99.3 > > 1.99.4 > > 2.0.0 > > > > 4. Binaries are built over the *source tarball* released at the > > milestones. The important artifact is the source tarball, it is the > > source of all good and evil. > > > > 5. Downstream may adopt / modify / re-write packaging but it will use > > the release source tarball at their choice of milestone, probably it > > won't adopt pre-release version. > > > > In case of oVirt, I do understand the the release schedule is tight > > between fedora and oVirt as it is the only supported distribution. > > However, I do expect that the sources will have similar to the above > > cycle, and the formal build will be produced out of the sources. Yes, I agree. Long term, once we get stable enough on multiple distros, I'd definitely want to move toward a model where we are releasing just src tarballs, and distro maintainers update the packages based on the new upstream source. I just don't think we're at that stability level yet. Mike > > > > Alon > > > > ----- Original Message ----- > > > From: "Mike Burns" <[email protected]> > > > To: "arch" <[email protected]> > > > Cc: "engine-devel" <[email protected]>, "vdsm-devel" > > > <[email protected]>, "node-devel" > > > <[email protected]> > > > Sent: Thursday, January 10, 2013 3:07:58 AM > > > Subject: [vdsm] ATTN: Project Maintainers: Code Freeze/Branch/Beta > > > Build deadlines > > > > > > (Sorry for cross posting, trying to ensure I hit all the relevant > > > maintainers) > > > > > > If you are the primary maintainer of a sub-project in oVirt, this > > > message is for you. > > > > > > At the Weekly oVirt Meeting, the final devel freeze and beta dates > > > were > > > decided. > > > > > > Freeze: 2013-01-14 > > > Beta Post: 2013-01-15 > > > > > > Action items: > > > > > > * You project should create a new branch in gerrit for the release > > > * You should create a formal build of your project for the beta > > > post > > > * Get the formal build of your project into the hands of someone > > > who > > > can > > > post it [1][2] > > > > > > These should all be done by EOD on 2013-01-14 (with the exception > > > of > > > ovirt-node-iso) [3] > > > > > > Packages that this impacts: > > > > > > * mom > > > * otopi > > > * ovirt-engine > > > * ovirt-engine-cli > > > * ovirt-engine-sdk > > > * ovirt-guest-agent > > > * ovirt-host-deploy > > > * ovirt-image-uploader > > > * ovirt-iso-uploader > > > * ovirt-log-collector > > > * ovirt-node > > > * ovirt-node-iso > > > * vdsm > > > > > > Thanks > > > > > > Mike Burns > > > > > > [1] This is only necessary if the package is *not* already in > > > fedora > > > repos (must be in actual fedora repos, not just updates-testing or > > > koji) > > > [2] Communicate with mburns, mgoldboi, oschreib to deliver the > > > packages > > > [3] ovirt-node-iso requires some of the other packages to be > > > available > > > prior to creating the image. This image will be created either on > > > 2013-01-14 or 2013-01-15 and posted along with the rest of the > > > Beta. > > > > > > _______________________________________________ > > > vdsm-devel mailing list > > > [email protected] > > > https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel > > > > > _______________________________________________ > > Arch mailing list > > [email protected] > > http://lists.ovirt.org/mailman/listinfo/arch > > _______________________________________________ Arch mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/arch
