Why composer.phar needs to be updated after 60 days? -


i want understand that, why composer.phar file needs updated after 60 days?

why composer.phar needs updated after 60 days?

composer doesn't need updated after 60 days. update recommended after time!

why 60 days?

i can't speak core developers on decision, can give educated guess:

composer used shorter frequency recommending updates during development , alpha stages. former message warning: development build of composer on 30 days old. recommended update.... users recommended pull updates in short frequency stay on latest, bleeding-edge version. short update frequency allows users report bugs , issues project. results in fast feedback , development cycle fast roll-outs of new versions address urgent issues.

now, composer released stable time increased 60 days, because (i guess) fast feedback cycle no longer needed. reflects project no longer in pre-release/alpha development mode, has stabilized. stats might lie, might take @ issue tracker find massive amount of closed tickets , few open ones: 120 open 3,356 closed issues (02-06-2016).


Comments

Popular posts from this blog

ios - RestKit 0.20 — CoreData: error: Failed to call designated initializer on NSManagedObject class (again) -

java - Digest auth with Spring Security using javaconfig -

laravel - PDOException in Connector.php line 55: SQLSTATE[HY000] [1045] Access denied for user 'root'@'localhost' (using password: YES) -