The symfony plugin section only lists plugins that are released under a license similar to the symfony one. This does not mean you cannot release a plugin under another license (the GPL license for example), but then, you will have to host them in your own PEAR channel.
The following licenses are accepted: MIT, BSD, LGPL, and PHP.
As soon as you upload a version of your plugin on the website, someone can install it. Now, if you change a file, this user must be able to upgrade. And to be able to upgrade, symfony will look for a newer version of your plugin. So, you must release a new version by incrementing the version of the plugin.
To sum up, if you have uploaded a version that you want to "replace", delete it and re-upload a new one with a greater version number.
The creation of new SVN repositories are done by a bot. But the bot is a bit lazy, as he only works on the hour mark. The great news is that he works days and nights. So, be patient as you won't have to wait very long.
The changes of SVN credentials are done by a bot. But the bot is a bit lazy, as he only works on the hour mark. The great news is that he works days and nights. So, be patient as you won't have to wait very long.
When you upload your plugin, symfony parses the package.xml file and try to find a <changelog> section like this one:
<!-- ... -->
<license uri="http://www.symfony-project.org/license">MIT license</license>
* someone fix that (#1234)
* me done this
<!-- ... -->