- marked as enhancement
- marked as minor
Create a standard tool for distributing releases
Issue #82
open
Idea is derived from python: posting package to pypi is as easy as python setup.py register
(to register new package or new version of a package in python package index) and python setup.py sdist upload
. It would be good to create a tool that, based on addon-info.json
and README
, Intro
section of help file or the whole help file, will upload plugin on www.vim.org, creating new script page if necessary.
Non-optional features:
- Adding
scriptnumber
key toaddon-info.json
when first uploading a plugin. - Using
README
or help file (whole or only first section) to update description on each upload. - Using template installation detail suggesting containing instructions on how to use plugin managers, officially supported by vimcommunity. Should also contain information about dependencies.
- Triggering immediate vim-pi database update on successful upload (both initial and update).
- Creating and uploading archive containing necessary plugin files. (Needs an extension to addon-info.json to filter those files).
- Updating version number in
addon-info.json
.
Optional additional features:
- Generating README out of the whole help file or just its Intro section.
- If configured adding release tags to VCS and/or releases to bitbucket (github issue tracker has nothing like this).
- If configured committing changes to addon-info.json and README.
- Registering new www.vim.org user from command-line.
- Triggering immediate vim-scripts update. Needs assistance with their teams.
- Creating ebuilds, rpm specs, deb-src packages, rpm/deb packages and similar things used in various distributions. Guess initially this will be limited to ebuilds only.
Comments (1)
-
reporter - Log in to comment