RE: [Firebird-devel] damn gbak Win32 error

[Leyne, S. <sl...@at...>]

Ded,

Thanks for the explaination of the background of Dmitry's posting.

>  "The more FB moves from IB the worse it works. Lets forgot=20
> about it, go
> back to IB5.6 or FB 9.4 and wait for IB6.5., they never stop
> experiments."

Obviously, those are comments we need to react/address.


>   Dmitry is main IB/FB supporter in Russia. He first started=20
> to promote
> FB and makes it now, he is under heavy pressure of this kind on forums
> and, I suppose, at work. I must say that enough amount of rational
> people (and me among them) tries to help Dmitry in=20
> discussions with this
> really heavy situation, but we also think that time period from
> relatively stable 9.4 became too long. It's difficult to keep oneself
> from using new builds knowing that old ones contain bugs that=20
> bother you
> and are fixed.

Yes, the fact that 0.9-4 was around for so long has been noted as an
issue by the Admin's

> Especially viewing "Release Build (1.0.0Beta2)" link on
> www.firebirdsql.com. There were unpleasant new bugs in this build and
> what? Efforts where concerned on fixing them in following?=20
> No, on adding
> new functionality. My opinion is: it's time to stop adding new
> functionality and make new stable build where old bugs are=20
> fixed and new ones are not added.=20

I agree, but we need people to help invest some time in tracking down
the bugs.  This is ugly work.  The only person who was really 'invested'
himself in that is Claudio.

Working on new features is always more fun. ;-)


>   Sorry, I'll mix replies to Claudio and Sean in one post.

Fine with me.


> CV>I hope that nobody is using these interim builds in production.
>=20
>   I was surpised by one post on ib-support on Tuesday:
> =20
> >> which version of firebird is stable?
> >All of the versions are stable, as much as anything can be.

That was my posting, and at the time I meant it.  What surprised you?


> DK> If nobody cares, and want cash or profit for his work, what
> DK> we are doing here?
>=20
> SL>WOA!  None of the work done to-date has been motivated by a profit
> SL>motive.  Accordingly, it is *very* unfair to suggest that motive.
>=20
>   Maybe I'm old cynic, but I don't trust on projects where is'nt any
> profit motives, usually such projects are a childish play and=20
> can't live
> long. I think you wanted to say that nobody here want money=20
> for his work
> just now and have hope to get some profit, direct or indirect, in the
> future.

I would suspect more indirect, since only Borland can really directly
profit, in a significant way, from the sale of the engine itself.


> SL> Why isn't
> SL>that developer joining the project and contributing here=20
> -- he would
> SL>seem to be just the type of member we are looking for?
>=20
>   As far as I know, he couldn't attract your attention to his efforts.
> He says that he suggested one time an idea and code for it's=20
> achievement
> but it was'nt noticed. Some time later it appeared in the FB code but
> without mention his name (it can be coincidence, good ideas often come
> more than into one head). Don't know, maybe he was'nt=20
> persistent enough, maybe language problems.=20

Can we get the name of the individual?  When did he try to contact us?
What has the change he submitted?


> BTW, what is the way for developer who made
> some noticeable changes into code for own purposes and want=20
> this changes
> to be included into general stream? I mean not a bug report or feature
> request but really noticeable changes.

In general, I would think that an approach which involves this list at
the start of the process (before coding) would be the most successfull.
A simple posting saying, "I've been thinking about doing this..." (along
with some outline of the approach to be used) would be the best starting
point.

Otherwise, issue/problems, raised after the fact, with the approaches
used could make the change 'unsuitable' for inclusion in the general
stream -- this is a situation I think most of us would hate to see.

I want to emphasize that we don't want to control the development, just
make sure that it will 'fit in'.


Sean