[RFC] Release 1.0

[Thinkscape]

Dear @ezimuel @weierophinney and contributors: I think it's long overdue that we released version 1.0 of ZFTool. Any suggestions or counter arguments ?

[gianarb]

Beautiful proposal 👍
There are a lists of little PR, someone can merge it and tag this tool?
For example:

• Wrong init_autoloader.php file name #95
• [WIP] Write configuration when creating a controller #80
• Standardized the request params initialization #81

Thanks for your job!

[weierophinney]

Honestly, @ezimuel and I have been discussing a complete rewrite, using zf-console as the basis. The rationale is:

• The approach to have this work both standalone and as a module within a ZF2 application has not worked out; we've had a number of lingering issues we cannot resolve that occur when you move from one use case to the other.
• Being structured as a module leads to a number of difficulties:
  • Builds have to essentially create a ZF2 skeleton, inject zftool as a module, and then package the whole lot in order to create a PHAR file. This is tremendous overkill - the PHAR is easily 5x bigger than it needs to be in order to deliver the functionality.
  • Mapping commands to controllers is relatively unintuitive, particularly when we get to things like the "create" command (it handles 4 unrelated types of resources).

The combination of these things has meant we've not had many people capable of providing new features, and have often run into problems when integrating new features.

Basing this off of zf-console would:

• reduce the number of dependencies
• simplify the build process when creating a standalone PHAR
• still allow composition inside an existing application (but instead of exposing itself via the application's MVC layer, its code would be detached from the application, removing the issues we currently have)
• hopefully simplify maintenance and creation of new tasks

In short: I don't think the current code base is anywhere near stable, and would rather we scrap it and start over with a new architecture.

[gianarb]

Hi! @weierophinney thanks for your job! The future of this project? will be forgotten, deleted?
Could we tag it and proceed to big refactoring?

[weierophinney]

@gianarb again, I don't want to tag this as stable, as it's not. It won't be forgotten -- we need to figure out where it fits in with the other dozen or more priorities we're juggling at the moment, though.

[gianarb]

oh yes 1.0.0 is not a good tag because ZFTool is not ready for it.. 👍

[Thinkscape]

How about I tag it 0.1.0 for now ?

Rewrite aside, I believe the expectation is easier and predictable composer-based installation (see i.e. #22)

[gianarb]

0.1.0 👍 where is the problem?

[weierophinney]

@Thinkscape go ahead and tag as 0.1.0 -- that will be a strong indication that we do not consider it stable, but allow people to pin to release versions.

[Thinkscape]

https://github.com/zendframework/ZFTool/releases/tag/v0.1.0

[gianarb]

Thanks 🎉