Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I'm using composer (in Symfony2 projects) and often get errors updating libraries.
Many libraries (most to my experience) use dev-master as version for their dependencies (or worse they use * ).
Whenever something is committed to the master branch you get to update the library, and the chances of an API change are higher as time goes by. What today in master is version 1.2.1 tomorrow could be 1.2.7, with no harm, and become later 1.7 or 2.x with sure incompatibilities.
My questions are
how did we get to this point? Is it a practice suggested from high profile sources?
what can I/we do to sensibilize the authors to this subject?
or
am I mad?
You are not mad.
It's a chicken and egg issue, until people tag more, others can not require tagged releases.
Nag everyone that has no tag or did not tag anything in six months (if the project is actively developed that is). I made an effort to tag all our bundles earlier this week, because I read a similar rant and I got reminded we still had only dev-master versions on most of them.
The solution really is education, and I will try to help a bit by pushing for best practices in composer docs. Not everyone has much experience with package management and many people don't realize how problematic this approach can be (until it's too late), so it's everyone's job to help by reminding them.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 11 months ago.
Improve this question
I need to upgrade PHP version of my project. It is PHP5.6 and I want to upgrade it to PHP8.1. I tried to search for such information but couldn't find it, thus, I want to ask. Is it better to upgrade directly from PHP5.6 to PHP8.1, or step by step (PHP5.6 -> PHP7.0, PHP7.0 -> PHP7.1, PHP7.1->PHP7.2 and etc until I reach PHP8.1)?
Upgrading step by step can help you to see what is deprecated by following the logs files and then review the code.
I have recently been made aware of this tool which ostensibly makes this process much easier. Note that I have not used it myself and as such can't speak to how well it works. It looks to be a FOSS project though which is good.
Website: https://getrector.org/
Github: https://github.com/rectorphp/rector
Updating manually as per the guides provided by vee will likely give you better understanding of the benefit each upgrade offers as well as maintaining full control over your project.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed last year.
Improve this question
I am looking for a solution for code management in the company.
We have a lot of projects that we work on on a daily basis. And sometimes two developers are required to work on the same project simultaneously.
An optimal situation for us is that each developer will have his local environment. And when he updates his code, the changes will be updated by all developers automatically.
And so virtually all developers will have the constantly updated version.
The problem with GIT is that the upload/download has to be manual, so the developer may forget to download a version.
We work in a PC environment.
Please, inspire me :)
My employer had this same problem, and came to the conclusion that there is only one way to handle it:
Teach your developers to use git properly. Ideally, teach them some kind of system for branching and merging, such as git-flow or GitLab Flow.
Some git tools can help you by automatically querying the server every 10 minutes to see if someone else has pushed new commits and prompt you to download them. (I think VSCode has this feature, but I don't remember for sure. Personally, I use SmartGit which also has this feature.)
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 2 years ago.
Improve this question
Sometimes a feature that I want to create for my laravel application already exists as a package.
It is easy to install them, but I am worried about their impact on the application performance.
What should I consider when choosing whether to install a package or develop a feature by myself?
It's personal preference at the end of the day.
Some packages are well written, optimized and maintained and this gives you so many benefits:
Reduced maintainence cost (i.e. you aren't 100% responsible for fixing the package code)
Decreased development time (i.e. you don't have to write it)
Increased functionality (i.e. they may have features you hadn't even thought of)
Other packages are poorly written, un-optimized and in some cases obsolete. These can have the opposite effect:
Increased maintainence cost (i.e. the author isn't neccesarily going to fix an issue)
Increased development time (i.e. you will probably have to learn their code base and fix issues yourself)
My advice would be to make sure that if it's a well respected author/company and their code base is activily being worked on (check github / npm / etc), then using the package will likely save you time and hassle in the long run.
You aren't likely to see any massive performance degredation by using composer packages over writing it yourself!
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
In silex's web page, it says that the stable version of siles is 1.3 but silex-skeleton uses version 2 of silex, is this recommended?
Silex 2.0 is not stable yet, in fact is a dev-master. The bigger problem is that a dev-master can change at any time. Unlike a stable version, it may be that one day you will do composer update and your application will stop working for some reason.
It is always preferable stable versions, but you can also developed you application in sync with the branch master of silex.
For your sake and the sake of your team don't do it.
I have made the mistake of putting one of my big projects back in time of Symfony2.0-alpha (or was it beta, not sure). The documentation was scarce, it was unstable for some use-cases - I wen't thought hell and back.
Projects are marked unstable for a reason - they should not be used in production until the devs make sable release.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
I wonder if Symfony 2.0 is stable enough to use?
Because I've never used Symfony before.
It seems that Symfony 2 is much better than the previous version and I don't want to relearn/recode everything some months from now.
When do you think it will be released?
Would it be a wise choice to use 2.0 now?
No.
Yes. http://symfony.com/download
http://symfony-reloaded.org/learn
Quote from above link:
Please note that Symfony 2 is not yet ready for production. The final release is planned for late 2010 and will only support PHP 5.3.2. In the meantime, we highly encourage you to use the current symfony 1.4 stable release for all your projects.
Symfony core team member here. No, Symfony2's not ready at all to be used in production, because it hasn't even reached the alpha state. As stated on the github page, things (especially the API) WILL change.
Furthermore, some components are not here yet, for example the Forms framework, so you would have to handle them by hand. Don't do that. But of course we'd be more than happy to get some feedback if you give it a try for a sandbox project of yours ;)
I would like to point out that we (www.exercise.com) are live and have been using Symfony 2 for a while now.
It has not been the most smooth experience (we try to stay up to date with the most recent sf2 branches on git, which is almost a full-time job for 1 person), but we have built a functioning site.
The largest hurdle right now to starting a project is the lack of documentation and examples online. So while it is possible to run a production site using Symfony 2, the framework still has a long ways to go until it can be used for a small project.
Yesterday at SymfonyLive 2011 (Twitter #sflive2011) Fabien said that the first Release Candidate will be March 2011.