laminas-servicemanager
laminas-servicemanager copied to clipboard
Update reflection based abstract factory documentation
Q | A |
---|---|
Documentation | yes |
Bugfix | yes |
BC Break | no |
New Feature | no |
RFC | no |
QA | no |
Description
After working through the documentation to learn more about the Reflection-based Abstract Factor, I felt that the documentation could be refined to make it that much easier to read and maintain, as well as to extend the usage examples to make them more encompassing of different use cases. This PR replaces https://github.com/laminas/laminas-servicemanager/pull/134.
Note: IMO for 3.13.x
Note: IMO for
3.13.x
I'm pretty sure @froschdesign recommended 3.11. @froschdesign?
Unless it's a bugfix, it should be landing in new minors in general :D
Note: IMO for
3.13.x
As already mentioned: with the current state of documentation, in terms of quality and quantity, any change can be considered as a patch. No matter if something is updated or added. I have no problem with a patch for the documentation being released as a minor version with other pull requests. But only a change to the documentation as a minor makes the release rather sad. Because nothing is changed on the user side after a Composer update.
I'd do a patch release even for docs, which is just more noise tho? :thinking:
In this case, I'd do 2 releases + 2 merge-ups
I'd do a patch release even for docs, which is just more noise tho?
It would be much better if changes to documentation did not require releases at all. :stuck_out_tongue_winking_eye:
I don't mind, honestly - we don't have enough noise from it for it to be a problem.
@Ocramius, if you don't mind either way, I'd prefer to leave it as is. On a different note, what can I do about the DCO check failing, as it relates to laminas bot?
?
Just merge anyway?
Yeah, DCO is useless corporateism, so it can be ignored on anything that isn't "world-changing tech", TBH.
@froschdesign your call on where/how to merge/release
@settermjd @froschdesign I've also modified the documentation in #180
Should we try to finish this as well and then merge-up to 4.0.x?
@boesing
Should we try to finish this as well and then merge-up to 4.0.x?
A good idea, because the entire documentation needs to be reworked for version 4.0.