[Springframework-developer] Package names

[Ken K. <kk...@kk...>]

I suppose we could deploy whatever docs and examples we have on the 
website and actually release early to mid next week. It's not likely 
anyone at the symposium will be downloading while they're actually 
attending. If we take that approach, it would be best to commit to a 
release date and announce it at the symposium and on the website.

Ken
 
John VanDyk wrote:

>>  > 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
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: INetU
> Attention Web Developers & Consultants: Become An INetU Hosting Partner.
> Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
> INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>
>