releases reorganization
With the beta release of 3.2 EL6 rpms, I had to re-organize the releases area a bit. Previously, the stable, beta, and alpha directories were symbolic links to the top level 3.2 or 3.1 directories. Because EL6 is part of 3.2, but not considered "stable" yet, I needed a way to handle that. The result: Top level 3.1, 3.2, 3.3, etc directories contain src, iso, rpm, and tools directories. The rpm directory will contain *all* distributions that are available for that release, whether beta, alpha, or stable. releases ├── 3.2 │ ├── iso │ ├── rpm │ │ ├── EL │ │ │ └── 6 │ │ │ ├── i686 │ │ │ ├── noarch │ │ │ ├── repodata │ │ │ │ └── repomd.xml │ │ │ ├── SRPMS │ │ │ └── x86_64 │ │ └── Fedora │ │ ├── 17 -> ../../../3.1/rpm/Fedora/17 │ │ ├── 18 │ │ │ ├── i686 │ │ │ ├── noarch │ │ │ ├── repodata │ │ │ │ └── repomd.xml │ │ │ ├── SRPMS │ │ │ └── x86_64 │ │ └── 19 -> 18 │ ├── src │ └── tools The beta, alpha, and stable symlinks are now real directories containing symlinks for iso src and tools. The rpm directory contains symlinks to the appropriate stable release for the version. releases └── stable ├── iso -> /var/www/html/releases/3.2/iso ├── rpm │ └── Fedora │ ├── 17 -> /var/www/html/releases/3.1/rpm/Fedora/17 │ └── 18 -> /var/www/html/releases/3.2/rpm/Fedora/18 ├── src -> /var/www/html/releases/3.2/src └── tools -> /var/www/html/releases/3.2/tools releases ├── beta │ ├── iso -> ../3.2/iso │ ├── rpm │ │ ├── EL -> ../../3.2/rpm/EL │ │ └── Fedora -> ../../3.2/rpm/Fedora/ │ ├── src -> ../3.2/src │ └── tools -> ../3.2/tools I've made these changes already due to requests from some developers who couldn't find the EL6 rpms under 3.2. If we want to change this model, then let me know. Otherwise, I'll add this documentation to the wiki. Mike
Hello Mike, I think that we should split the nightly between two: 1. nightly stable - the next z stream candidate. 2. nightly next - the next minor candidate. This will enable user to fetch pre-releases of z streams easily when setting up nightly repository. Currently as all going into same directory, having nightly repository pulls next minor with all its issues. What do you think? Alon ----- Original Message -----
From: "Mike Burns" <mburns@redhat.com> To: "infra" <infra@ovirt.org> Sent: Monday, March 18, 2013 3:02:27 PM Subject: releases reorganization
With the beta release of 3.2 EL6 rpms, I had to re-organize the releases area a bit. Previously, the stable, beta, and alpha directories were symbolic links to the top level 3.2 or 3.1 directories. Because EL6 is part of 3.2, but not considered "stable" yet, I needed a way to handle that. The result:
Top level 3.1, 3.2, 3.3, etc directories contain src, iso, rpm, and tools directories. The rpm directory will contain *all* distributions that are available for that release, whether beta, alpha, or stable.
releases ├── 3.2 │ ├── iso │ ├── rpm │ │ ├── EL │ │ │ └── 6 │ │ │ ├── i686 │ │ │ ├── noarch │ │ │ ├── repodata │ │ │ │ └── repomd.xml │ │ │ ├── SRPMS │ │ │ └── x86_64 │ │ └── Fedora │ │ ├── 17 -> ../../../3.1/rpm/Fedora/17 │ │ ├── 18 │ │ │ ├── i686 │ │ │ ├── noarch │ │ │ ├── repodata │ │ │ │ └── repomd.xml │ │ │ ├── SRPMS │ │ │ └── x86_64 │ │ └── 19 -> 18 │ ├── src │ └── tools
The beta, alpha, and stable symlinks are now real directories containing symlinks for iso src and tools. The rpm directory contains symlinks to the appropriate stable release for the version.
releases └── stable ├── iso -> /var/www/html/releases/3.2/iso ├── rpm │ └── Fedora │ ├── 17 -> /var/www/html/releases/3.1/rpm/Fedora/17 │ └── 18 -> /var/www/html/releases/3.2/rpm/Fedora/18 ├── src -> /var/www/html/releases/3.2/src └── tools -> /var/www/html/releases/3.2/tools
releases ├── beta │ ├── iso -> ../3.2/iso │ ├── rpm │ │ ├── EL -> ../../3.2/rpm/EL │ │ └── Fedora -> ../../3.2/rpm/Fedora/ │ ├── src -> ../3.2/src │ └── tools -> ../3.2/tools
I've made these changes already due to requests from some developers who couldn't find the EL6 rpms under 3.2. If we want to change this model, then let me know. Otherwise, I'll add this documentation to the wiki.
Mike _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
On 03/26/2013 12:15 PM, Alon Bar-Lev wrote:
Hello Mike,
I think that we should split the nightly between two:
1. nightly stable - the next z stream candidate. 2. nightly next - the next minor candidate.
This will enable user to fetch pre-releases of z streams easily when setting up nightly repository. Currently as all going into same directory, having nightly repository pulls next minor with all its issues.
What do you think?
I have no strong objections other than the fact that I don't think we should be making so many changes in the released branches that require constantly updating packages in a nightly. If you think it's necessary, I don't object, though. As for the setup, this is more in Eyal and Ofer's domain I think. They maintain the deployment of rpms from jenkins into the nightlies. Mike
Alon
----- Original Message -----
From: "Mike Burns" <mburns@redhat.com> To: "infra" <infra@ovirt.org> Sent: Monday, March 18, 2013 3:02:27 PM Subject: releases reorganization
With the beta release of 3.2 EL6 rpms, I had to re-organize the releases area a bit. Previously, the stable, beta, and alpha directories were symbolic links to the top level 3.2 or 3.1 directories. Because EL6 is part of 3.2, but not considered "stable" yet, I needed a way to handle that. The result:
Top level 3.1, 3.2, 3.3, etc directories contain src, iso, rpm, and tools directories. The rpm directory will contain *all* distributions that are available for that release, whether beta, alpha, or stable.
releases ├── 3.2 │ ├── iso │ ├── rpm │ │ ├── EL │ │ │ └── 6 │ │ │ ├── i686 │ │ │ ├── noarch │ │ │ ├── repodata │ │ │ │ └── repomd.xml │ │ │ ├── SRPMS │ │ │ └── x86_64 │ │ └── Fedora │ │ ├── 17 -> ../../../3.1/rpm/Fedora/17 │ │ ├── 18 │ │ │ ├── i686 │ │ │ ├── noarch │ │ │ ├── repodata │ │ │ │ └── repomd.xml │ │ │ ├── SRPMS │ │ │ └── x86_64 │ │ └── 19 -> 18 │ ├── src │ └── tools
The beta, alpha, and stable symlinks are now real directories containing symlinks for iso src and tools. The rpm directory contains symlinks to the appropriate stable release for the version.
releases └── stable ├── iso -> /var/www/html/releases/3.2/iso ├── rpm │ └── Fedora │ ├── 17 -> /var/www/html/releases/3.1/rpm/Fedora/17 │ └── 18 -> /var/www/html/releases/3.2/rpm/Fedora/18 ├── src -> /var/www/html/releases/3.2/src └── tools -> /var/www/html/releases/3.2/tools
releases ├── beta │ ├── iso -> ../3.2/iso │ ├── rpm │ │ ├── EL -> ../../3.2/rpm/EL │ │ └── Fedora -> ../../3.2/rpm/Fedora/ │ ├── src -> ../3.2/src │ └── tools -> ../3.2/tools
I've made these changes already due to requests from some developers who couldn't find the EL6 rpms under 3.2. If we want to change this model, then let me know. Otherwise, I'll add this documentation to the wiki.
Mike _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
_______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
On 03/27/2013 08:46 AM, Mike Burns wrote:
On 03/26/2013 12:15 PM, Alon Bar-Lev wrote:
Hello Mike,
I think that we should split the nightly between two:
1. nightly stable - the next z stream candidate. 2. nightly next - the next minor candidate.
This will enable user to fetch pre-releases of z streams easily when setting up nightly repository. Currently as all going into same directory, having nightly repository pulls next minor with all its issues.
What do you think?
I have no strong objections other than the fact that I don't think we should be making so many changes in the released branches that require constantly updating packages in a nightly. If you think it's necessary, I don't object, though.
As for the setup, this is more in Eyal and Ofer's domain I think. They maintain the deployment of rpms from jenkins into the nightlies.
perhaps instead of nightly-stable, how about something like updates-testing? Mike
Mike
Alon
----- Original Message -----
From: "Mike Burns" <mburns@redhat.com> To: "infra" <infra@ovirt.org> Sent: Monday, March 18, 2013 3:02:27 PM Subject: releases reorganization
With the beta release of 3.2 EL6 rpms, I had to re-organize the releases area a bit. Previously, the stable, beta, and alpha directories were symbolic links to the top level 3.2 or 3.1 directories. Because EL6 is part of 3.2, but not considered "stable" yet, I needed a way to handle that. The result:
Top level 3.1, 3.2, 3.3, etc directories contain src, iso, rpm, and tools directories. The rpm directory will contain *all* distributions that are available for that release, whether beta, alpha, or stable.
releases ├── 3.2 │ ├── iso │ ├── rpm │ │ ├── EL │ │ │ └── 6 │ │ │ ├── i686 │ │ │ ├── noarch │ │ │ ├── repodata │ │ │ │ └── repomd.xml │ │ │ ├── SRPMS │ │ │ └── x86_64 │ │ └── Fedora │ │ ├── 17 -> ../../../3.1/rpm/Fedora/17 │ │ ├── 18 │ │ │ ├── i686 │ │ │ ├── noarch │ │ │ ├── repodata │ │ │ │ └── repomd.xml │ │ │ ├── SRPMS │ │ │ └── x86_64 │ │ └── 19 -> 18 │ ├── src │ └── tools
The beta, alpha, and stable symlinks are now real directories containing symlinks for iso src and tools. The rpm directory contains symlinks to the appropriate stable release for the version.
releases └── stable ├── iso -> /var/www/html/releases/3.2/iso ├── rpm │ └── Fedora │ ├── 17 -> /var/www/html/releases/3.1/rpm/Fedora/17 │ └── 18 -> /var/www/html/releases/3.2/rpm/Fedora/18 ├── src -> /var/www/html/releases/3.2/src └── tools -> /var/www/html/releases/3.2/tools
releases ├── beta │ ├── iso -> ../3.2/iso │ ├── rpm │ │ ├── EL -> ../../3.2/rpm/EL │ │ └── Fedora -> ../../3.2/rpm/Fedora/ │ ├── src -> ../3.2/src │ └── tools -> ../3.2/tools
I've made these changes already due to requests from some developers who couldn't find the EL6 rpms under 3.2. If we want to change this model, then let me know. Otherwise, I'll add this documentation to the wiki.
Mike _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
_______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
----- Original Message -----
From: "Mike Burns" <mburns@redhat.com> To: "Alon Bar-Lev" <alonbl@redhat.com> Cc: "infra" <infra@ovirt.org>, "Eyal Edri" <eedri@redhat.com>, "Ofer Schreiber" <oschreib@redhat.com> Sent: Wednesday, March 27, 2013 2:47:41 PM Subject: Re: releases reorganization
On 03/27/2013 08:46 AM, Mike Burns wrote:
On 03/26/2013 12:15 PM, Alon Bar-Lev wrote:
Hello Mike,
I think that we should split the nightly between two:
1. nightly stable - the next z stream candidate. 2. nightly next - the next minor candidate.
This will enable user to fetch pre-releases of z streams easily when setting up nightly repository. Currently as all going into same directory, having nightly repository pulls next minor with all its issues.
What do you think?
I have no strong objections other than the fact that I don't think we should be making so many changes in the released branches that require constantly updating packages in a nightly. If you think it's necessary, I don't object, though.
As for the setup, this is more in Eyal and Ofer's domain I think. They maintain the deployment of rpms from jenkins into the nightlies.
perhaps instead of nightly-stable, how about something like updates-testing?
I am not peaky in names... :) We probably need two nightly jobs, and some setup of the cron job at the host...
Mike
Mike
Alon
----- Original Message -----
From: "Mike Burns" <mburns@redhat.com> To: "infra" <infra@ovirt.org> Sent: Monday, March 18, 2013 3:02:27 PM Subject: releases reorganization
With the beta release of 3.2 EL6 rpms, I had to re-organize the releases area a bit. Previously, the stable, beta, and alpha directories were symbolic links to the top level 3.2 or 3.1 directories. Because EL6 is part of 3.2, but not considered "stable" yet, I needed a way to handle that. The result:
Top level 3.1, 3.2, 3.3, etc directories contain src, iso, rpm, and tools directories. The rpm directory will contain *all* distributions that are available for that release, whether beta, alpha, or stable.
releases ├── 3.2 │ ├── iso │ ├── rpm │ │ ├── EL │ │ │ └── 6 │ │ │ ├── i686 │ │ │ ├── noarch │ │ │ ├── repodata │ │ │ │ └── repomd.xml │ │ │ ├── SRPMS │ │ │ └── x86_64 │ │ └── Fedora │ │ ├── 17 -> ../../../3.1/rpm/Fedora/17 │ │ ├── 18 │ │ │ ├── i686 │ │ │ ├── noarch │ │ │ ├── repodata │ │ │ │ └── repomd.xml │ │ │ ├── SRPMS │ │ │ └── x86_64 │ │ └── 19 -> 18 │ ├── src │ └── tools
The beta, alpha, and stable symlinks are now real directories containing symlinks for iso src and tools. The rpm directory contains symlinks to the appropriate stable release for the version.
releases └── stable ├── iso -> /var/www/html/releases/3.2/iso ├── rpm │ └── Fedora │ ├── 17 -> /var/www/html/releases/3.1/rpm/Fedora/17 │ └── 18 -> /var/www/html/releases/3.2/rpm/Fedora/18 ├── src -> /var/www/html/releases/3.2/src └── tools -> /var/www/html/releases/3.2/tools
releases ├── beta │ ├── iso -> ../3.2/iso │ ├── rpm │ │ ├── EL -> ../../3.2/rpm/EL │ │ └── Fedora -> ../../3.2/rpm/Fedora/ │ ├── src -> ../3.2/src │ └── tools -> ../3.2/tools
I've made these changes already due to requests from some developers who couldn't find the EL6 rpms under 3.2. If we want to change this model, then let me know. Otherwise, I'll add this documentation to the wiki.
Mike _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
_______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
participants (2)
-
Alon Bar-Lev -
Mike Burns