Release manager

Hi,

The Ruby-GNOME2 project lacks human resources. For example,
we doesn’t release new version since 2006-12-29 even if we
keep developing.

We want a release manager who will do the following work:

  • You will try to build on supported platform that will be
    decided by you.
    (e.g. ruby >= 1.8.x, GTK+ >= 2.x.x, Linux, FreeBSD,
    Windows, MacOSX, …)
    Some people who aren’t a release manager but they have a
    supported platform will help you.

  • You will archive a new Ruby-GNOME2 package.

  • You will release the archived package on SF.net.
    (I have a release script for SF.net. It may help you.
    Cutter download | SourceForge.net)

  • You will announce the release on SF.net and related MLs.
    e.g.:
    http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-talk/231656

  • You will do the same work again after a few months ago.

We are waiting for your help!

Thanks,

kou

Hi,

I would like to participate.

The Ruby-GNOME2 project lacks human resources. For example,
we doesn’t release new version since 2006-12-29 even if we
keep developing.
Yes, it’s a shame.
Also I think the bindings are pretty stable now and maybe the version
0.16 may not “describe” the actual progress.

We want a release manager who will do the following work:

  • You will try to build on supported platform that will be
    decided by you.
    (e.g. ruby >= 1.8.x, GTK+ >= 2.x.x, Linux, FreeBSD,
    Windows, MacOSX, …)
    I have a i386 ubuntu linux machine here.

How do you test all the bindings ? Are there any automated tests
available? Sure I can test it with all the applications I have and use,
but they surely will not test every feature.

  • You will archive a new Ruby-GNOME2 package.
    Does it include precompiled binaries? The thing I don’t have here is a
    Windows machine. Anyone else would need to do binary packages for win32.

Best Regards,
Joachim G.

The Ruby-GNOME2 project lacks human resources. For example,
we doesn’t release new version since 2006-12-29 even if we
keep developing.

Jep, I also thought about this… From my point of view, we should
release (at least) tar balls every six month. Even if we couldn’t follow
the Gtk+ / GNOME release cycles with complete bindings, this will be a
good sign for the packagers of the destributions to release new packages
and to the “normal user” it will show, that ruby-gnome is still alive.

I have a i386 ubuntu linux machine here.

I have a PowerPc debian and an i386 debian setup here. For his i could
set up a build- and test bot. But…

How do you test all the bindings ? Are there any automated tests
available?

…this is a big problem. There is no testframework at all. I’m not that
much an expert in this, but i think that a usefull testframework is at
least as much work than the bindings itself.

Sure I can test it with all the applications I have and use,
but they surely will not test every feature.

  • You will archive a new Ruby-GNOME2 package.

IMHO that is not a special need. Cause SF does not make any backups (at
least they tell so) someone has to make regularey backups from all
data.

Cheers detlef

Detlef R. wrote:

Sure I can test it with all the applications I have and use,
but they surely will not test every feature.

  • You will archive a new Ruby-GNOME2 package.

IMHO that is not a special need. Cause SF does not make any backups (at
least they tell so) someone has to make regularey backups from all
data.

I think what he meant with this is:

  • check out a specific svn version
  • put new version number on it
  • make a tarball out of it (=archive a new package)

11 mar 2008 kl. 23.31 skrev Detlef R.:

Hi,

Glad to see this discussion come up. I’m relatively new to Ruby-Gnome2
but a long time contributer and maintainer on various GNOME modules.

I’m a bit curious as to whether it wouldn’t make sense to move the
infrastructure over to the GNOME/GTK+ infrastructure?

This will bring the project closer to the rest of the community, as
well as make it easier to get involved in the project if you are
already a GNOME/GTK+ contributor. As far as I know all of the
successful bindings are hosted on GNOME Subversion server, in GNOME
Bugzilla, release tarballs on the GNOME FTP etc.

I would personally be happy to assist in any way to make this happen
as well as try building on both Linux and Mac OS X (Intel and PPC).

Cheers and thanks to everyone who have brought the bindings to the
current level, your work is much appreciated.

Mikael H.

and to the “normal user” it will show, that ruby-gnome is still alive.

Windows, MacOSX, …)
much an expert in this, but i think that a usefull testframework
IMHO that is not a special need. Cause SF does not make any backups
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/


ruby-gnome2-devel-en mailing list
[email protected]
ruby-gnome2-devel-en List Signup and Options


Imendio AB, http://www.imendio.com

Joachim G. wrote:

Does it include precompiled binaries? The thing I don’t have here is a
Windows machine. Anyone else would need to do binary packages for win32.

Best Regards,
Joachim G.

Well, this is too bad for me. I am a windows user but I don’t have VC6
compiler to build the binary.

Am Dienstag, den 11.03.2008, 23:43 +0100 schrieb Joachim G.:

I think what he meant with this is:

  • check out a specific svn version
  • put new version number on it
  • make a tarball out of it (=archive a new package)

For this is no need. For packages just put a tag onto the svn branch and
that was it.

Hi,

In [email protected]
“Re: [ruby-gnome2-devel-en] Release manager” on Tue, 11 Mar 2008
19:45:42 +0100,
Joachim G. [email protected] wrote:

I would like to participate.

Thanks for your help!
I’ll give you some rights on SF.net. Could you tell me your
SF.net account?

How do you test all the bindings ? Are there any automated tests
available? Sure I can test it with all the applications I have and use,
but they surely will not test every feature.

No but I want to add some automated tests. Sample programs
will also help you.

  • You will archive a new Ruby-GNOME2 package.
    Does it include precompiled binaries? The thing I don’t have here is a
    Windows machine. Anyone else would need to do binary packages for win32.

It will be desired on Windows.

Thanks,

kou

Hi,

In 1205274719.3141.15.camel@datengrab
“Re: [ruby-gnome2-devel-en] Release manager” on Tue, 11 Mar 2008
23:31:59 +0100,
Detlef R. [email protected] wrote:

  • You will archive a new Ruby-GNOME2 package.

IMHO that is not a special need. Cause SF does not make any backups (at
least they tell so) someone has to make regularey backups from all
data.

I just wanted to say about making .tar.gz, .zip, .exe and so
on.

Thanks,

kou

Hi,

In [email protected]
“Re: [ruby-gnome2-devel-en] Release manager” on Tue, 11 Mar 2008
23:44:25 +0100,
Mikael H. [email protected] wrote:

I’m a bit curious as to whether it wouldn’t make sense to move the
infrastructure over to the GNOME/GTK+ infrastructure?

This will bring the project closer to the rest of the community, as
well as make it easier to get involved in the project if you are
already a GNOME/GTK+ contributor. As far as I know all of the
successful bindings are hosted on GNOME Subversion server, in GNOME
Bugzilla, release tarballs on the GNOME FTP etc.

It’s OK for me. If other contributors prefer it, we will
move to there.

But applying an account for GNOME infrastructure is a bit

bother for me…

I would personally be happy to assist in any way to make this happen
as well as try building on both Linux and Mac OS X (Intel and PPC).

It will be very helpful.

Thanks,

kou

On mer, 2008-03-12 at 22:50 +0900, Kouhei S. wrote:

well as make it easier to get involved in the project if you are
already a GNOME/GTK+ contributor. As far as I know all of the
successful bindings are hosted on GNOME Subversion server, in GNOME
Bugzilla, release tarballs on the GNOME FTP etc.

It’s OK for me. If other contributors prefer it, we will
move to there.

I’m not really a contributor given that I don’t even remember my last
commit, but I think it would be nice to get closer to GNOME, and it
would give visibility

But applying an account for GNOME infrastructure is a bit

bother for me…

It’s supposed to be easier now
http://blogs.gnome.org/ovitters/2007/09/29/mango-gone-live/

12 mar 2008 kl. 14.50 skrev Kouhei S.:

Hi,

This will bring the project closer to the rest of the community, as
well as make it easier to get involved in the project if you are
already a GNOME/GTK+ contributor. As far as I know all of the
successful bindings are hosted on GNOME Subversion server, in GNOME
Bugzilla, release tarballs on the GNOME FTP etc.

It’s OK for me. If other contributors prefer it, we will
move to there.

Wonderful, I got some pings yesterday in #gnome-ruby2 and on Jabber
from people who liked the idea.

But applying an account for GNOME infrastructure is a bit

bother for me…

I can help with getting accounts sorted out for people who need them.
And hopefully (as Pascal wrote in a reply), things are working better
these days.

Cheers,
Mikael H.


Imendio AB, http://www.imendio.com

Hi,

2008/3/12, Joachim G. [email protected]:

I’ll give you some rights on SF.net. Could you tell me your
SF.net account?

My account name is ‘jglauche’

I’ve added your account to the project members.

It’s OK for me. If other contributors prefer it, we will
move to there.
fine by me.

At least, the next release (soon?) will be done on SF.net.

Thanks,

kou

Kouhei S. wrote:

At least, the next release (soon?) will be done on SF.net.

Is there any pending work in current trunk? (r2843)

If not, I can release the 0.17.0, at least the source-releases shortly.
Seems to work fine for me.

Kouhei, will it be possible for you and the main dev team to keep News
file in trunk with the most important/summarized news updated? I could
parse all the Changelog files and put them into the news file, but the
that’ll gonna be huge amount of changes since last release.

Kouhei S. wrote:

Thanks for your help!
I’ll give you some rights on SF.net. Could you tell me your
SF.net account?

My account name is ‘jglauche’

It’s OK for me. If other contributors prefer it, we will
move to there.
fine by me.

How do you test all the bindings ? Are there any automated tests
available? Sure I can test it with all the applications I have and use,
but they surely will not test every feature.

No but I want to add some automated tests. Sample programs
will also help you.
Sounds good. I have a bunch of programs which can be used for “reality”
testing also. But a more extended automated test platform would be very
very helpful.

Is there anyone who can help me on the win32 binaries?

Kouhei S. wrote:

And some important bug fixes and new features will be found
in ChangeLog. I hope that you include contributer names of
the next release in NEWS. It’s very important.
Yes, no problem. Just if you do something big, write in what is done and
the contributor name into NEWS file and commit it.

I think it’s less work than searching all the Changelog files for big
changes upon every release.

Those changes are all made by you or other contributors?

Am Freitag, den 14.03.2008, 22:28 +0900 schrieb Kouhei S.:

(* Ruby/GStreamer: Worked with GStreamer >= 0.10.x but doesn’t
completed yet.)

Does this mean, that GStreamer is now a part of RubyGnome again? If so:
nice!

Cheers, detlef

Hi,

In [email protected]
“Re: [ruby-gnome2-devel-en] Release manager” on Wed, 12 Mar 2008
22:04:28 +0100,
Joachim G. [email protected] wrote:

Is there any pending work in current trunk? (r2843)

There is no pending work for the next release.
All works will be done after the next release.

Kouhei, will it be possible for you and the main dev team to keep News
file in trunk with the most important/summarized news updated? I could
parse all the Changelog files and put them into the news file, but the
that’ll gonna be huge amount of changes since last release.

Here are important changes that are remembered now:

  • Ruby/GLib: Improved main loop polling. I hope this
    changes will work well (no polling) on Windows too but I
    can’t test it.

  • Ruby/GLib: Improved callback handling from non Ruby
    thread. I hope this changes will work well on Windows
    too but I can’t test it.

    This changes breaks API. Sjoerd, you need to call
    rbgutil_start_callback_dispatch_thread() in your
    GStreamer bindings. Sorry.

(* Ruby/GStreamer: Worked with GStreamer >= 0.10.x but doesn’t
completed yet.)

(* Ruby-GNOME2 can be builded with ruby 1.9.0 but doesn’t
work well.)

And some important bug fixes and new features will be found
in ChangeLog. I hope that you include contributer names of
the next release in NEWS. It’s very important.

Thanks,

kou

Hi,

In 1205504139.13720.29.camel@datengrab
“Re: [ruby-gnome2-devel-en] Release manager” on Fri, 14 Mar 2008
15:15:39 +0100,
Detlef R. [email protected] wrote:

(* Ruby/GStreamer: Worked with GStreamer >= 0.10.x but doesn’t
completed yet.)

Does this mean, that GStreamer is now a part of RubyGnome again? If so:
nice!

It will be true but it may not be true in the next
release. Because it’s not completed yet, the release manager
may decide that the next release doesn’t include it.

Thanks,

kou

Hi,

In 1205330733.8213.23.camel@plop
“Re: [ruby-gnome2-devel-en] Release manager” on Wed, 12 Mar 2008
15:05:33 +0100,
Pascal T. [email protected] wrote:

But applying an account for GNOME infrastructure is a bit

bother for me…

It’s supposed to be easier now
Mango gone live – Olav Vitters

I knew that. I want to use ‘kou’ for account name because
it’s my account name that I always use. But I can’t use
that. (Yes, this is a small problem.)

Thanks,

kou