Development/Bugs: Moving to SVN & Trac

  • ResolvedPlugin Author Aubrey Portwood

    (@aubreypwd)


    8 years ago

    I’ve been developing this plugin via Github, but I’ve hated developing it in two places Github/Git and Trac/SVN, so I’m just going to stick to Trac from now on.

    – New Tickets
    – All Tickets
    – New Ticket

    This is also a bit of an experiment with Trac and using the resources on wp.org more.

Viewing 1 replies (of 1 total)
  • Plugin Author Aubrey Portwood

    (@aubreypwd)

    Err, after some review of plugin guidelines, it appears this is not possible:

    14. Frequent commits to a plugin should be avoided.

    The SVN repository is a release repository, not a development one. All commits will trigger a regeneration of the zip files associated with the plugin, so only code that is ready for deployment (be that a stable release, beta, or RC) should be pushed to SVN. Including a descriptive and informative message with each commit is strongly recommended. Frequent ‘trash’ commit messages like ‘update’ or ‘cleanup’ makes it hard for others to follow changes. Commits that only tweak minor aspects of the plugin (including the readme) cause undue strain on the system and can be seen as gaming Recently Updated lists.

    So this will not be the case going forward.

Viewing 1 replies (of 1 total)
  • The topic ‘Development/Bugs: Moving to SVN & Trac’ is closed to new replies.