Hi, I have decided to use Subversion for my now 4-weeks old vncviewer plugin because according to Hosting Plugins Tutoria <https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins>l usage of Jenkins Subversion repository is still a valid way of plugin distribution.
The idea "simply abandon" something which is valid today from one day to the next is not a good one. Provided there is a consensus amongst the Jenkins core maintainers to drop the Subversion repo (is that really the case??) I would split the issue into several steps: 1. Update Hosting Plugins Tutoria <https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins>l, don't offer Subversion for hosting of *new* plugins 2. Create simple migration how-to for existing plugins which would make the migration easier for git newbies 3. After long enough (6 months ?) grace period for migration of existing plugins "simply abandon the Subversion repo" Am Mittwoch, 22. April 2015 14:59:58 UTC+2 schrieb Jesse Glick: > > >> Confusingly, when github.com/jenkinsci was created, we also mirrored > those subdirectories as Git repositories. Naturally people have since > then submitted GitHub PRs and in some cases pushed to the Git repo > while the Subversion repo was active, meaning the plugin is > effectively forked. This is a freaking mess. > > I think we should simply abandon the Subversion repo, meaning creating > a new commit that deletes everything, and then removing write access, > and request plugin authors to use GitHub. If they insist on using > Subversion (and not via the bridge to Git), they can use some other > hosting site, but the plugin should not be considered “hosted on > jenkins-ci.org”. > > Ideally some final check would be done for outstanding changes in svn > that did not make it into Git for whatever reason. > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/8643f06c-7f84-4b40-b802-927f1eed5c48%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
