|
From: John V. <jv...@ia...> - 2003-06-24 19:04:56
|
> > Personally, I'm inclined to a package change even at this time, before our >> first public release. Well, we've been talking about a release _tomorrow_, >> but I wouldn't mind delaying it till next week to be able to incorporate the > > package name change - if the whole group decides to apply it. Speaking as a lurker who is eagerly awaiting the first release with documentation and someone who has released open source software before, hold off a few days and make the changes first. In my experience, the most important thing for a successful release is: 1. Good docs, especially docs with examples to common problems in the problem domain. 2. Stable code. You really want to be ready when the first wave of potential developers visits, because if they are turned off they won't come back for the next release. John |