I had made a note a while back that this could be a function of the
plugins site (the django part). Where a plugin author could go to the
page for their plugin and there would be a button to package the plugin
from repo, where it defaults to the current repo state but optionally
lets the author pick a specific tag to package. There could be a check
box to do it automatically based on commit but that is likely more
complicated. Personally I also dislike the complete auto solution
because in my workflow 1 commit does not equal a release, in fact
sometimes it's 10+ commits before a feature or bug is fixed and the in
between states are not usable. I always tag when something is usable for
release.
An alternate approach is to clean up an api on the plugins site that
lets various tools push a release to it. Then various desktop apps (a
plugin perhaps) or post commit scripts could be used to push the release
to the website.
Thanks,
Alex
On 12/28/2011 07:33 AM, Anita Graser wrote:
On Wed, Dec 28, 2011 at 1:21 PM, Alexander Bruy<[email protected]>wrote:
Hi,
I think new plugin repo should provide this functionality (maybe at
optional basis). Preparing archive and uploading it every time is a bit
uncomfortable.
+1 If the repetitive work of archiving+uploading a new version for every
bugfix could be avoided, I think many plugin developers will want to change
to this new infrastructure.
Regards,
Anita
2011/12/28 Paolo Cavallini<[email protected]>:
Hi all.
We (faunalia) have a script for autopackaging our python plugins. I know
others have
made the same. I think this is very useful, as it allows painless
frequent release of
new versions, and avoids common errors.
I think this should become part of standard infrastructure, applied by
default to
every plugin added to common repo.
Any thoughts?
--
Alexander Bruy
_______________________________________________
Qgis-developer mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/qgis-developer
