Re: [Ekiga-devel-list] Improving the GNOME experience : request for help

["David Corking" <lists dcorking com>]

On 6/8/07, Elijah Newren <newren gmail com> wrote:
> On 6/7/07, Damien Sandras <dsandras seconix com> wrote:
> > However, maintaining the project asks much time, and coding asks even
> > more time, so I would like to request help for one specific task :
> >
> > 1) Prepare tarballs in case of release : ie Ekiga, OPAL and PWLIB
> > tarballs
> > 2) Test them (do at least minimal tests)
> > 3) Upload to GNOME.org
> > 4) Mail packagers
> > 5) Build a repository
>
> Just thought I'd mention this: Basic instructions for 1, 3, and 4 for
> modules in general are available at
> http://live.gnome.org/MaintainersCorner/Releasing (those instructions
> work for all the modules I've released, though perhaps ekiga, opal,
> and pwlib having additional issues).  I'm not sure what 5 means.

Thanks Elijjah - I copied that link into the Ekiga wiki for our future
reference.

For (5) I wrote: "The Ekiga Release Manager should make a repository
of contributed binary packages, such as RPMs and DEBs, available to
the webmaster of ekiga.org"

http://wiki.ekiga.org/index.php/Release_Manager

When I get my SVN account, I still won't be touching the sources (even
the changelog and news files) until I know I can do it to the
satisfaction of the established developers - my job will relate to the
tarballs and the announcements.

On the subject of announcements:
a - do all the packagers track one of ekiga-list and
gnome-announce-list, or are their other addresses that need cc'd?
b - is it now deprecated to cross-post to the release-team list ?

David