> -----Original Message----- > From: Chip Childers [mailto:[email protected]] > Sent: Thursday, September 06, 2012 11:21 AM > To: [email protected] > Subject: Re: Can we combine the work going on for builds in master and > maven-waf? > > Alex - Gotcha. I'll start testing the build in master for now, and > will wait to do it in 4.0. > > Edison - I've got things ready to create the RC for source, but was > waiting for the build to be sorted before dealing with the binary > portion. I have a clean CentOS VM ready to build the OSS RPMs.
Both 4.0 and master is ready to go, "./waf rpm" will build rpms under ./artifacts/rpmbuild/RPMS/x86_64 I am testing DEB now. > > On Thu, Sep 6, 2012 at 2:07 PM, Alex Huang <[email protected]> > wrote: > > > > > >> -----Original Message----- > >> From: Chip Childers [mailto:[email protected]] > >> Sent: Thursday, September 06, 2012 11:03 AM > >> To: [email protected] > >> Subject: Can we combine the work going on for builds in master and > maven- > >> waf? > >> > >> Can we combine the work going on for builds in master and maven-waf? > >> > >> At this point, I'm personally confused about which branch (master of > >> maven-waf) is the one that we are all looking at to stabilize the > build. > >> > >> Should we pick one? > > > > Chip, > > > > I revived 4.0 branch to be the stable release branch. Edison has > been getting things working on master and merging it over to 4.0 branch > when it works. We're also getting Jenkins going on the 4.0 branch. > All QA builds will be coming from the 4.0 branch. Maven-waf can be > done in parallel and when it's ready, we'll evaluate whether it should > go into 4.0 branch. > > > > --Alex > >
