[Libusbx-devel] Keeping the 1.0.9rc3 tag

[Pete Batard]

OK, I'll keep the tag in then.

On 2012.03.24 00:29, Xiaofan Chen wrote:
> And I do not see a problem with public github. My view is that
> we should announce the project and release asap on the libusb
> mailing list to show people that they have an alternative.

I'd rather have a wiki and libusbx.org pointing to it before we do that 
(and with some substance to the wiki). Going public with half the stuff 
missing is not going to encourage people to use libusbx, and was the 
reason why I didn't want to officialize things before the 1.0.10 release.

Currently, I doubt we'll have much to present by the 1.0.9 release. 
Having a release tarball is fine an all, but it's only *one part* of 
what we need to do to be seen as a viable alternative to libusb. We'll 
also need to duplicate doxigen, set up a bug report system (trac? 
something else?) and finalize some other stuff. And with the target for 
the 1.0.9 tarball release being in about a week, I'm not currently 
counting on having all of that sorted out (realistically, it'll take us 
more than a week to get there). Thus, until we do, I'd refrain from 
announcing that we're going to replace anything, because it'll be 
exceedingly apparent that we aren't in a position to actually do so.

Or, to put it more simply - there's nothing worse or that will 
discourage people from using your project, when you are competing 
against a mature well established one, than announcing things 
prematurely. The first thing people will do is of course compare your 
offering with what they can have on the other side, and if you offer 
less features, even if you bridge the gap later on, you'll lose the 
people who checked your project a first time, and decided it was too 
unpolished/unfinished to use.

First impressions are critical. Until we've sorted a bit more than a 
1.0.9 tarball release, I don't think we're anywhere near to make a good 
first impression.

Regards,

/Pete