Paul McNett wrote:
> I think that fc should be a separate project. Make a svn branch wx_release or 
> something, and keep it up to date with the latest-known-stable revision. Then 
> have 
> Robin make a svn:externals definition for floatcanvas pointing to that 
> branch, and 
> when it is time for a new wxPython release, his build script just needs to do 
> an svn 
> update.

That may work out fine -- I'm having trouble remembering what the 
advantages are of using the wxPython 3rd party SVN. I think Robin has a 
svn:external from wx.lib to the 3rd Party branch anyway.

> Keeping it separate makes for a much more focused ticket tracking system, 
> wiki, and 
> mailing list.

It would be nice to keep those better integrated.

>> Can we have Christian's TRAC point to the wxPython 3rd party SVN?
> 
> Come to think of it, I don't think Trac supports that.

darn.

> I'd be happy to host floatcanvas's trac, svn, and mailing list, but don't 
> want to 
> step on anyone's toes.

Thanks. I may just take you up on that. I don't think anyone's toes are 
in danger. Do you know how hard it is to move an archive of email from 
one Mailman instance to another (you would use mailman, yes?)

>> Another option is to put it on sourceforge of google code or something 
>> like that.
> 
> I don't know why I resist such options, but I do.

Me too.

-Chris


-- 
Christopher Barker, Ph.D.
Oceanographer

Emergency Response Division
NOAA/NOS/OR&R            (206) 526-6959   voice
7600 Sand Point Way NE   (206) 526-6329   fax
Seattle, WA  98115       (206) 526-6317   main reception

[email protected]
_______________________________________________
FloatCanvas mailing list
[email protected]
http://mail.mithis.com/cgi-bin/mailman/listinfo/floatcanvas

Reply via email to