Re: Repo layout. We really need to make the call by Tuesday 2012/7/24.

From: "Robert Middleswarth" <robert(a)middleswarth.net&gt; To: "infra" <infra(a)ovirt.org&gt; Sent: Friday, July 20, 2012 5:50:02 PM Subject: Repo layout. We really need to make the call by Tuesday 2012/7/24. The current repo layout will have to change some to support the 3.1 release that might be happening on the 25th. We are going to have to move stuff around to archive the 3.0 release as well as setup the 3.1 release in my option we can do it one of two ways. 1) Create an archive folder and just copy 3.0 to it well we do the 3.1 release and keep the same structure we have now. 2) Redo the layout to something that will long term support version and be less confusing to people using the project. Personally I think this is a good time to redesign. The existing 3.0 repo files are going to break when we move things around for the 3.1 release and we are going to need to make sure everything is in place. Since we are going to have to disrupt thing already why not do a full clean-up instead of just patch the current layout. Our current layout. release/[stable|beta|nightly]/[binary|fedora|RHEL|src]/[16|17|18] I recommend we switching to the following structure. release/[3.0|3.1|3.2|stable|testing]/[nightly|beta|released]/[tools|fedora|RHEL|src]/[16|17|18|rawhide]

With symlinks for stable and testing point to the current version for each. I also suggest a symlink called release/fedora-ovirt-latest.rpm that points to the latest ovirt-release-*.rpm file.

Inside each version there will be a repo file that enables released disables beta & nightly. Since each repo file will simple reference everything by version number each new release wont break old releases. What does everyone think? Thanks Robert _______________________________________________ Infra mailing list Infra(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/infra