Managing plugin releases

> -----Original Message-----
> From: Tim Williams [mailto:williamstwgmail.com]
> Sent: Wednesday, 26 July 2006 8:41 PM
> To: devforrest.apache.org
> Subject: Re: Managing plugin releases
> 
> On 7/26/06, Ross Gardler <rgardlerapache.org> wrote:
> > Tim Williams (JIRA) wrote:
> > > Discussed here to:
> > > http://marc.theaimsgroup.com/?t=115257903800001&a
mp;r=1&w=4
> > >
> > > I still agree with what I proposed in that
mail.  

Me too.

I actually like
> Ross' suggestion too but only if we move towards
better
> packaging/managing/releasing of plugins.

Me too.

> >
> > What do you think is needed?
> 
> o) Independent/PMC managed releases

Separating forrest collective written plugins from
contributed plugins?

Would there be a 'entire collection' packaged zip
containing every released
plugin?


> o) Improved versioning - externally identifiable.  So
that users might
> be able to uninstall v0.3 of a plugin and reinstall 0.2
of a plugin.
> I'm talking about manually not automagically.

I agree, would the externally identifiable mean a naming
convention to
include the version number and compatible forrest version
number?

> o) Combined with the above, improved manually
downloading of plugins.

Agree again, perhaps having them prettied up on the main
site as downloads
Rather than from a directory index.

Gav...

> 
> I reckon that's it.  Just to fill that gaps that will
be left by not
> shipping them with the binary basically.
> --tim
> 
> 
> --
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.1.394 / Virus Database: 268.10.4/399 -
Release Date: 7/25/2006

On 7/26/06, Gav.... <brightoncomputersbrightontown.com.au> wrote:
>
>
> > -----Original Message-----
> > From: Tim Williams [mailto:williamstwgmail.com]
> > Sent: Wednesday, 26 July 2006 8:41 PM
> > To: devforrest.apache.org
> > Subject: Re: Managing plugin releases
> >
> > On 7/26/06, Ross Gardler <rgardlerapache.org> wrote:
> > > Tim Williams (JIRA) wrote:
> > > > Discussed here to:
> > > > http://marc.theaimsgroup.com/?t=115257903800001&a
mp;r=1&w=4
> > > >
> > > > I still agree with what I proposed in
that mail.
>
> Me too.
>
> I actually like
> > Ross' suggestion too but only if we move towards
better
> > packaging/managing/releasing of plugins.
>
> Me too.
>
> > >
> > > What do you think is needed?
> >
> > o) Independent/PMC managed releases
>
> Separating forrest collective written plugins from
contributed plugins?

I consider any plugin that exists in our SVN to be a
"forrest plugin"
regardless of how it got there, it now carries an apache
license.

> Would there be a 'entire collection' packaged zip
containing every released
> plugin?

I don't feel strongly about this either way but probably
not because
it would create a versioning nightmare I think.  One would
never know
which version of the various plugins they are getting, etc.

> > o) Improved versioning - externally identifiable. 
So that users might
> > be able to uninstall v0.3 of a plugin and
reinstall 0.2 of a plugin.
> > I'm talking about manually not automagically.
>
> I agree, would the externally identifiable mean a
naming convention to
> include the version number and compatible forrest
version number?

Just the plugin version I think - let docs handle the rest.

--tim