qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Huston" <shus...@riverace.com>
Subject RE: Release Schedule
Date Fri, 27 Feb 2009 18:45:12 GMT
> -----Original Message-----
> From: Alan Conway [mailto:aconway@redhat.com] 
> Steve Huston wrote:
> >>> The dates for each phase would be as follows:
> >>>
> >>> End of Development : 2009-03-02
> >>> End of Feature Freeze : 2009-03-16
> >>> Release : 2009-03-27
> >>>   
> >> This was the last set of dates Martin had put up for 0.5 
> release. I 
> >> suspect that
> >> it is still worth putting a 0.5 as quite a lot of fixes have 
> >> been made 
> >> since M4.
> >>
> >> Are we still on for freeze on Monday?
> >> Feature Freeze     March  02nd
> >> RC                       March  23rd (and branch trunk)
> > 
> > I'd like to get the new build scheme in for M5, based on cmake -
> > not sure I'll have a first cut in by Monday, but it would 
> be next week
> > sometime. I think that in order for that to be in M5, though,
> > need some group discussion after getting a chance to test drive it
> > bit.
> > 
> > Thoughts?
> > 
> I'm keen to get it in but it will need some advance warning 
> so people can try it in different environments. There may be some
> teething problems and there are 
> significant downstream build systems that will be affected.

Right, good points. We'll take another look at this when the trunk
thaws out again.

> Ideally we want it to have the same "API" (./bootstrap; ./configure 
> --with-same-options; make), 
> where bootstrap and configure are wrappers to the new system.

The cmake system generates Makefiles (and Visual Studio projects,
etc.) from which a regular 'make' is done. Think of cmake replacing
bootstrap and configure. There are similar ways to specify options and
such, and it ends up a pretty direct and simple few commands, even
though they're cmake and make instead of bootstrap, configure, and

We're also keeping tabs on what other projects are doing around cmake
now that the KDE project recently switched to cmake. There's some best
practices being developed; one is at Fedora dealing with building
rpms: http://fedoraproject.org/wiki/Packaging/cmake


Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org

View raw message