libvisual-devel

[Libvisual-devel] libvisual nebulus

[Dennis S. <sy...@yo...>]

Heya everyone!

I've imported libvisual-nebulus into sf.net libvisual CVS under the
module (suprise!) libvisual-nebulus.

Duilio would you care to check it out and see if it's release ready as
it is right now ? we might want to add some EXTRA_DIST stuff here and
there. 


I'd like to do a release this weekend, I would be really happy if
people could check and see if the new libvisual build tree is
doing well. Duilio what needs to be done before we can do a new
release ?


Thanks,
Dennis

[Libvisual-devel] nebulus plugin

[Duilio J. P. <dp...@fc...>]

> Duilio would you care to check it out and see if it's release ready as
> it is right now ? we might want to add some EXTRA_DIST stuff here and
> there. 

It is right. Not only the repository, but the distro package too.
I have submitted some little work, take a look.

> Duilio what needs to be done before we can do a new
> release ?

Check all the packages (not our working copies, but the distro
packages from scratch). Remember you must --enable all plugins
before to make dist.

However, give one more day to check XMMS plugin. Another issue
you must focus on this release, are the feedback mechanisms.
You must say exactly how you want the report bugs must be, 
and create categories accordingly on the sf.net site.

This release must be as stable as possible. Of course it will
have the well known bugs, but despite of them, it must compile
everywhere and it must work, and the people must know there
is work in progress here.

After that, I think we must focus on the most important TODO:
the versioning system.
If we don't resolve this, on every new release of the library
will be needed a plugins/nebulus/xmms-plugin release also,
which is too hard to maintain.


Duilio.

Re: [Libvisual-devel] nebulus plugin

[Dennis S. <sy...@yo...>]

On Fri, 2004-06-25 at 00:08 -0300, Duilio Javier Protti wrote:
> Check all the packages (not our working copies, but the distro
> packages from scratch). Remember you must --enable all plugins
> before to make dist.
> 
> However, give one more day to check XMMS plugin. Another issue
> you must focus on this release, are the feedback mechanisms.
> You must say exactly how you want the report bugs must be, 
> and create categories accordingly on the sf.net site.
What would be the best place to notice about this, the README ?


> This release must be as stable as possible. Of course it will
> have the well known bugs, but despite of them, it must compile
> everywhere and it must work, and the people must know there
> is work in progress here.
Agree on that.


> After that, I think we must focus on the most important TODO:
> the versioning system.
> If we don't resolve this, on every new release of the library
> will be needed a plugins/nebulus/xmms-plugin release also,
> which is too hard to maintain.
Yep that is a important item, I haven't really thought about how
we could implement this, but whatever we do we have do this
right on the first time.

Thanks,
Dennis