Oh no - I wouldn't want it to be immediate - I'm saying it should wait until all the minimal ASF requirements have been met. Once they have been met, we do a release as quickly as we can. If this takes us two days after import, then great. If it takes 1 week, ok. I'm just saying as fast as possible, assuming we have the requirements taken care of. This would 1) get us familiar with how to do an ASF release and 2) establish a nice *stable* baseline from which all subsequent ASF releases can be made.
Does that sound like a good idea? On Fri, Sep 5, 2008 at 10:48 AM, Emmanuel Lecharny <[EMAIL PROTECTED]>wrote: > Hi Les, > > I'm wondering if it's important to release under Apache immediately after > the code import, until we have meet some minimal requirements (headers, > notices, etc). The initial injection of code in the SVN repo will be like a > tag, and if we have nightly builds, the the project can be downloaded. > > thoughts ? > > > Les Hazlewood wrote: > >> After I get 0.9.0 out (the last non-apache release), I'd like to do a >> 0.9.1 >> release. >> The only difference is that the 0.9.1 release would be an official Apache >> release - all the license headers would be in place, the proper >> NOTICE/README files are located appropriately, etc. >> >> In essence, there would be zero difference in code or functionality with >> 0.9.0, it would just be an Apache release. >> >> I'm thinking this is a good idea because it would get one Apache release >> under our belt without having to worry about functionality - a >> test-but-not-quite-test run, so to speak. It would also look good to have >> an initial *stable* release available to the rest of the Apache community. >> >> Is this a good idea? Any opinions? >> >> >> > > > -- > -- > cordialement, regards, > Emmanuel Lécharny > www.iktek.com > directory.apache.org > > >
