On Fri, Aug 31, 2012 at 1:24 PM, Chiradeep Vittal <[email protected]> wrote: > > > On 8/31/12 9:57 AM, "Wido den Hollander" <[email protected]> wrote: > >> >> >>On 08/31/2012 06:12 PM, Chip Childers wrote: >>> Looking for feedback here... >>> >>> As I stated in an earlier email, I'm not going to be able to do the >>> release candidate build today. However, I'm willing to do it on >>> Tuesday (unless there are objections, or someone else wants to do it >>> today). >>> >>> As for the process itself, I believe these are the steps that need to >>> be taken (this assumes that we have created / refreshed the 4.0 >>> branch): >>> >>> 1) pull a clean copy of the branch source tree >>> 2) git archive --format zip --output ~/cloudstack-src-4.0.0RC1.zip 4.0 >>> 3) git archive 4.0 | tar -czf cloudstack-src-4.0.0RC1.tar.gz >>> 4) build the RPM and DEB packages (I might not be able to do this one >>> for the first round... we might have to stick with the source distro >>> first) >>> 5) sign everything >>> 6) commit the artifacts to the ASF dist svn repo >>> >>> To do the RPM and deb builds, I assume we need to run those processes >>> from an appropriate build server for each type. I can use a Fedora >>> and Ubuntu VM for it in the short term. Am I right or wrong about >>> that requirement (haven't tested yet). >>> >> >>I think you are probably right there. >> >>I've been building the Ubuntu packages for myself lately, works fine. >> >>I'm using: >> >>$ dpkg-buildpackage >> >>I also have Ubuntu 12.04 systems set up to build these packages, so I'm >>happy to build them if requested. >> >>Wido >> >>> I created a dev build distribution directory here: >>> https://dist.apache.org/repos/dist/dev/incubator/cloudstack >>> >>> Source material that I'm using: >>> >>>https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+Maintai >>>ners+Guide >>> http://www.apache.org/dev/release.html >>> http://httpd.apache.org/dev/release.html >>> >>> We will also want the cloudstack project site to include a download >>> page that uses the ASF mirrors correctly. After I get the first build >>> out there, I'll update that page as well. >>> >>> -chip > > The RC build will have both OSS and non-OSS enabled? > >
IMO, it shouldn't. We aren't going to be able to distribute those packages. However, if someone wants to test against it, they would use the source RC and build with the non-OSS libraries. Any disagreements? -chip
