Release testing and the relationship between 'bzr selftest' and plugins

[Jelmer Vernooij]

Am 16/03/12 17:11, schrieb Vincent Ladeuil:
>
>     >> The osx installer (and the windows installer too AFAIK) has a script to
>     >> download from a branch (tip) or a tag or a revid, so it's just a matter
>     >> of providing either a branch (during betas) or a tag for stable
>     >> releases.
>     > We still had out of date plugins in the installer, though.
>
> Yeah, the process is still not polished enough :-/
>
> Ideally, at least osx and windows, should share their scripts (or
> release definitions) so we can update it in a single place. 
>
> More and people are submitting merge proposals just for bumping which
> version of a plugin should be packaged.

> I think that's the good trend and we should probably help it becoming
> the official way to get packaged.
Do you mean that plugin authors should submit updates to the installers?
I've updated the versions of bzr-svn/bzr-git in the installers a couple
of times, but I would really rather stay away from this. It takes time
(and releasing already takes up enough time) and I don't have the
environment to test my changes in.


Cheers,

Jelmer

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 900 bytes
Desc: OpenPGP digital signature
URL: <https://lists.ubuntu.com/archives/bazaar/attachments/20120316/e5f0800a/attachment.pgp>