ZeosLib 7.0 Stable, any time soon?

[Pitfiend]

I'm wondering when a stable release will be available. Also, if we can have a list of improvements over 6.x series. Honestly, I'm still developing with delphi 2007 + ZeosLib 6.6.6 a combination I found very stable and reliable. I use it with Mysql, SQLite and some ADO too.

Edit: Any chance it will keep compatibility with older Delphi?

[EgonHugeist]

Pitfiend,

MDeams did assamble the first Zeos7 stable preview releases which are available on the zeos.firmos download section. Zeos7 is more stable then 6.6.x ever was trust me on that. Zeos 7 had a lot of problems to fullfill the support for the Full-Unicode IDE's which i've solved (most parts i think) on the testing-egonhugeist branch. We did broke with Kylix and older compilers than Delphi7. All others are still supported. I personally did fix a lot of bugs (can't count them any more!)

Waiting for project manager MDeams. I also have the same question and i'm worried about the trunk and testing branches. Here i see no way for a stable release..

Michael

[Pitfiend]

Cool! when I said older Delphi, I meant pre-unicode ones, mainly because I'm hooked to D2007. My employer has no interest in purchase a new version, so I have to work with what we have. It's good to know that you'll try to keep compatibility. IMHO, ZeosLib is by far better than the database components shipped with Delphi, old and new ones.

[ism]

We must wait a couple of months, if the error is not, then releasing

[EgonHugeist]

ism,

that's right! Here is an sniped from the original founder of Zeos, Sergey Seroukhov, and the rules he proposed for Alpha, Beta, Gamma, Stable:

Our first priority must be a stable product. You can't win the race trying to implement every new feature that apears on the horizon- especially if you develop a product that needs to run on several operating systems, several compilers and against several databases. A software product that isn't stable is high sophisticated junk!

I'd suggest the traditional way of ZeosLib development:

Step 1: Identify the key features that will improve the usability of ZeosLib for most users within every supported database and that can be developed in a few month. Keep this as the development goal for a new version branch. Publish this feature list and a schedule to the public.

Step 2: Code like hell and ensure that all internal QA tests have passed without errors before releasing the first alpha version.

Step 3: After release of the first alpha, freeze the feature list and do only bug fixing. Keep in touch with the users. All team members should read forum messages regarding the alpha frequently to see where people have difficulties. Those difficulties and reported errors should be addressed ASAP.

Step 4: Release a beta within some weeks. Developers may start new branch now, but first priority is still fixing the bugs if new ones arise.

Step 5: Release a gamma (release candidate) if no new errors are reported for at least two weeks.

Step 6: Release the stable version if no new errors are reported for at least one month. Release patch releases if necessary.

I hope all do now understand, why i try to clearify what a bug is and what are feature requests. Second why i'm trying to win the race agains the reported bugs and ignore features... I want to see the stable state!!

Michael

[mdaems]

Beta has just been released. See announcement on front page of the portal.