Re: [Java-gnome-developer] (no subject)

[Jeffrey M. <ku...@zo...>]

On Wed, 2003-12-10 at 08:41, Mark Howard wrote:
> API support
> -----------
> We should (initially) publicly announce support for glib, gtk, gnome,

gnome should be stated as libgnome, libgnomeui, and libgnomecanvas 
since they are all contained in our org.gnu.gnome package.

> libglade. We then need to urgently see how much of the upstream api we
> actually support. The current sources are based on 2.0 releases --
> there are probably many changes which are required.
> *please* can ppl volunteer to take a module each and go through this --
> either file bug reports for any API sections which we don't support, or
> produce a document listing them all (if there are many).
> We need to produce a schedule for this and make sure it is all done
> properly, ideally within the next 2 weeks. This task is probably vital
> to our joining the gnome bindings release.
> 
> CVS Hacking
> -----------
> If there are no objections, I will do this over the next few days.

Are you sure this can be completed and tested in order to allow us
time to make the necessary changes prior to the 22nd?

> Reorganise cvs:
> java-gnome/web
>         - website
> java-gnome/java-gnome
>         - main code tree. Includes makefiles which will build everything.
> { java-gnome/java-gnome/gtk
>   java-gnome/java-gnome/pango
>   java-gnome/java-gnome/atk
>   java-gnome/java-gnome/glib
>   java-gnome/java-gnome/glade
>   java-gnome/java-gnome/gnome
>   java-gnome/java-gnome/gtkhtml
>   java-gnome/java-gnome/vte
>   java-gnome/java-gnome/gconf
> }       - These are the main source code areas. Each will contain separate
> Makefile.in's (the makefiles will be generated using data from
> jg/jg/build/), /src/java/org/gnu/... and /src/jni/ trees. These will all
> generate separate jar files and shared libraries
> 
> { java-gnome/java-gnome/doc-core
>   java-gnome/java-gnome/doc-glade
>   java-gnome/java-gnome/doc-gnome
> }       - packages containing documentation and example applications.
> 
> java-gnome/java-gnome/build
>         - scripts to automate creation of makefiles, tarballs, etc.
> 
> Applications currently in cvs should be moved to separate projects --
> they are too large to be classed as example applications. Having them in
> separate projects would also be of great benefit to them. Could
> somebody please volunteer to be the maintainer for each of these and
> create a new sourceforge project?
> 
> In order to make these changes, I will download the cvs repo source and
> hack that manually. This will leave a few days where no commits can be
> mode and then everybody will have to check everything out again. It's a
> nuisance - but sadly necessary. I will start as soon as other j-g
> developers send an email saying they agree - please do this soon.

I am in favor of this move but am concerned that we might not be
able to get everything completed prior to the 22nd.  If we do intend
to shoot for this date we should announce our intention on the bindings
list.

> 
> Released Tarballs
> -----------------
> (note - these will all be created by a single script, so it won't be a
> difficult as it sounds)
> tarball_name    (cvs modules included)
> libglib-java    (glib)
> libgtk-java     (gtk, pango, atk)
> libgnome-java   (gnome)
libgnome, libgnomeui, libgnomecanvas
> libglade-java   (glade)
> [ libgtkhtml-java       (gtkhtml) ]
> [ libgconf-java         (gconf)   ]
> [ libvte-java           (vte)     ]
> [ libgnomepanel-java (gnomepanel) ]
> Items in brackets will be created and put on the website, but will not
> go in our gnome bindings module list until we are sure we can support
> them. They are in development.
> [ java-gnome    (all) ] - this is as a convenience. It will probably be
> used by everyone, especially developers and distributors (who will then
> create multiple binary packages).
> 


> Actions Summary
> ---------------
> (I'm really sorry this email got so long...)
> 
> api - somebody needs to send links to all upstream apis and changes
>    between them (any volunteers?). We all then need to check how much we
>    currently support. We need to keep a record of what checks we have
>    done.
> cvs hacking - Let me know if it's ok & I'll get to it

I would say start now.  I just checked in some code so make sure
you get the latest.

> tarballs - we'll release more of these after the cvs hackery
> focus - work more on existing bindings while there are pending bug
>    reports, then look to new libraries
> release schedule
>         22 December - tarballs. Make or break time for our inclusion in the
>         official bindings list.
>         16 Feb - API Freeze
>         22 March - bindings for 2.6 released
> parallel install - need minor code modifications

Yes.  We will have more shared objects to load and finding the entry
point for some of the libs might not be easy.

> version numbering - let me know if you disagree my proposal above
> sourceforge - anyone second my proposal

yes

> upstream - join the ml, look at webpages. Find out about development.
>    Find out what API has changed from 2.0 to 2.5
> 
> Please send comments, questions and suggestions ASAP -- to be included
> in the gnome release set we need to move very quickly.