incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mattmann, Chris A (388J)" <>
Subject Re: Basing Apache releases on releases from incubating projects
Date Wed, 01 Dec 2010 18:14:03 GMT
Hi Joe,

>>  than going to some other OSS provider and then  coming here 
>> later.
> You're confused about the whole point of releases at Apache.
> They aren't necessarily meant to offer any promises about
> stability or suitability for a given purpose, they are simply
> meant as a means of getting the code out the door in a formal
> and responsible way (given that we *are* a corporation).  Too
> many projects fail to release alpha and beta quality
> code, and that's not the org's, nor the Incubator's, fault.

Not sure I'm confused, just poking actually, but near the end of my poking.

Question: if podlings fail to make a release, but still have code checked into our Apache
SVN and say they've went through a code grant, they've done ICLAs for all the committers,
and everything looks OK, but the community dies, then how can folks depend on that code if
it's got some nice features they want to include? What's the barrier there? The code is in
our SVN, it's licensed using our license, there's been some diligence to check it (but maybe
not full, etc.), etc.

Anyhoo a lot of this is moot if the person is just willing to work the process to try and
help make the podling release. But that doesn't work in all cases. There are some communities
I can push on/help/etc., as much as I can, and they still won't make the release, that's just
the nature of the beast. 


Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message