Release manager

Kouhei_S · March 14, 2008, 3:40pm

Hi,

In [email protected]
“Re: [ruby-gnome2-devel-en] Release manager” on Fri, 14 Mar 2008
15:07:26 +0100,
Joachim G. [email protected] 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.

OK, the release manager.

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

I think so but I want you to search ChangeLog because I want
you to add contributer names even if their contribution is
very small. It may be small but contribution itself is very
big for us.

Those changes are all made by you or other contributors?

Maybe me. If you find other contributor names in ChangeLog,
please add them to NEWS.

Thanks,

kou

Kouhei_S · March 19, 2008, 3:47pm

Kouhei S. wrote:

Those changes are all made by you or other contributors?

Maybe me. If you find other contributor names in ChangeLog,
please add them to NEWS.

Kouhei,

Please take a short look on updated NEWS file before I finally tag
current trunk as 0.17.0.

I hope I didn’t miss anything/anybody.

Thanks!

Kouhei_S · March 15, 2008, 3:20am

Hi,

In [email protected]
“Re: [ruby-gnome2-devel-en] Release manager” on Wed, 12 Mar 2008
15:08:01 +0100,
Mikael H. [email protected] wrote:

move to there.

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

Is there any auto-build support on the GNOME infrastructure?

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.

Thanks.
If we decide to move to the GNOME infrastructure, could you
help the Ruby-GNOME2 subversion repository migration?

–
kou

Kouhei_S · March 19, 2008, 4:00pm

On Wed, Mar 19, 2008 at 03:47:43PM +0100, Joachim G. wrote:

Those changes are all made by you or other contributors?

Maybe me. If you find other contributor names in ChangeLog,
please add them to NEWS.

Please take a short look on updated NEWS file before I finally tag
current trunk as 0.17.0.

I hope I didn’t miss anything/anybody.

My 2 cents:
Since Ruby/GStreamer was dropped from the project in the 0.16.0 release,
I wouldn’t mention the main change for it anymore. It is confusing.
I would remove 15–17 too, since it is addressed to Sjoerd specifically

Rest seems fine.

Regards,
Paul

–
PhD Student @ Eindhoven | email: [email protected]
University of Technology, The Netherlands | JID: [email protected]

Kouhei_S · March 19, 2008, 4:00pm

Hi,

In [email protected]
“Re: [ruby-gnome2-devel-en] Release manager” on Wed, 19 Mar 2008
15:47:43 +0100,
Joachim G. [email protected] wrote:

Those changes are all made by you or other contributors?

Maybe me. If you find other contributor names in ChangeLog,
please add them to NEWS.

Please take a short look on updated NEWS file before I finally tag
current trunk as 0.17.0.

I hope I didn’t miss anything/anybody.

I prefer to Masao’s format like:

Ruby/GLib
- Support GLib±2.10 APIs. [Kouhei S., Masao M.]
- Fix segfaults related GC with signal handlers. [Guillaume
  Cottenceau, K
  ouhei Sutou]
  …
Ruby/ATK
- Support ATK-1.12 APIs. [Masao M.]
…

But it’s OK for now. This is the first release for us. We
can improve our release process step by step.

Supported version information may be useful.

I find a important change for convenience notation:

glib/ChangeLog:
2007-08-08 Kouhei S. [email protected]

      * src/rbgobj_enums.c: supported convenience GEnum and GFlags
      notation. e.g.:
        GLib::UTF8.normalize(utf8, GLib::NormalizeMode::NFD)
        ->
        GLib::UTF8.normalize(utf8, :nfd)

        key_file.load_from_data(data,
                                GLib::KeyFile::KEEP_COMMENTS |
                                GLib::KeyFile::KEEP_TRANSLATIONS)
        ->
        key_file.load_from_data(data, [:keep_contents,

:keep_translations])

Thanks,

kou

Kouhei_S · March 19, 2008, 6:16pm

Please take a short look on updated NEWS file before I finally tag
current trunk as 0.17.0.

Back in last summer, I began adding missing 2.12 GTK+ symbols. The
2.12 version of GTK+ was not released, so I used this form of macro:

#if GTK_CHECK_VERSION(2,11,0)

Because the rest of the bindings normally check for the stable version
(e.g. check for “2,10,0” for example), I think my 2,11,0 checks might
be changed to 2,12,0 for the sake of orthogonality - but I’m not
changing it for the moment, waiting for comments.

Also, the NEWS file doesn’t mention the fact that rg2 now partially
supports new symbols in 2.12 (GtkRecentAction, GtkTextBuffer,
GdkDisplay, GtkTreeViewColumn, GtkStock, GtkWidget, GtkScaleButton,
GtkTreeView, GtkVolumneButton,
GtkTooptop and GtkTextMark only). Is it intentional because the
support is only partial, or maybe just something forgotten?

Before tagging to 0.17.0, do you want to call for tests? It might be
less painful to fix bugs in trunk rather to do it both in trunk and in
the branch; as for myself, I have recently checked the SVN, and found
nothing wrong with it so far.

Finally, I think the personal message to Sjoerd has little to do in
the NEWS file, because that file is meant to be read by all developers
using rg2. It is too specific/personal for the NEWS file.

–
Guillaume C. - Guillaume Cottenceau

Kouhei_S · March 19, 2008, 8:04pm

Guillaume C. wrote:

Also, the NEWS file doesn’t mention the fact that rg2 now partially
supports new symbols in 2.12 (GtkRecentAction, GtkTextBuffer,
GdkDisplay, GtkTreeViewColumn, GtkStock, GtkWidget, GtkScaleButton,
GtkTreeView, GtkVolumneButton,
GtkTooptop and GtkTextMark only). Is it intentional because the
support is only partial, or maybe just something forgotten?

In my opinion, this should belong to the NEWS file (which is WIP of
course). Because I guess this is not the only feature missing credit in
the NEWS file, could you please add that and your ideas to the file?

Before tagging to 0.17.0, do you want to call for tests? It might be
less painful to fix bugs in trunk rather to do it both in trunk and in
the branch; as for myself, I have recently checked the SVN, and found
nothing wrong with it so far.

Everything works for me at in current trunk, but please do some tests
too before we release 0.17.

If possible I need someone who can test it on the win32 platforms. It
compiles on mingw, but I couldn’t install on another windows machine
yet.
I’ll try again later, but working with Windows consumes much more time
on many tasks.
We may consider to release windows binaries separately when this is
blocking the release, which shouldn’t wait more than 2 weeks from now
(unless we find some mayor bugs meanwhile).

Finally, I think the personal message to Sjoerd has little to do in
the NEWS file, because that file is meant to be read by all developers
using rg2. It is too specific/personal for the NEWS file.

Was just copy+pasted by me from post by Kouhei. I think this should be
removed in news file too.

Kouhei_S · March 19, 2008, 4:15pm

Kouhei S. wrote:

Ruby/GLib

Support GLib±2.10 APIs. [Kouhei S., Masao M.]

Fix segfaults related GC with signal handlers. [Guillaume
Cottenceau, K
ouhei Sutou]
…

Ruby/ATK

Support ATK-1.12 APIs. [Masao M.]

…

Yes, but I’m not the Maintainer and there are a lot of changes. I for
myself cannot decide for each change which will make it to the NEWS
file; for this I would require to know the changes in detail.

We can keep the old format for next releases. As I suggested, please
update the NEWS file for changes in upcoming versions if you do big or
noticeable changes, including contributors.

Supported version information may be useful.

Did anything change?

I find a important change for convenience notation:

glib/ChangeLog:
2007-08-08 Kouhei S. [email protected]

      * src/rbgobj_enums.c: supported convenience GEnum and GFlags
      notation. e.g.:
        GLib::UTF8.normalize(utf8, GLib::NormalizeMode::NFD)
        ->
        GLib::UTF8.normalize(utf8, :nfd)

        key_file.load_from_data(data,
                                GLib::KeyFile::KEEP_COMMENTS |
                                GLib::KeyFile::KEEP_TRANSLATIONS)
        ->
        key_file.load_from_data(data, [:keep_contents,

:keep_translations])

Ok, I’ll add it.

Kouhei_S · March 19, 2008, 10:29pm

The Ruby-GNOME2 project lacks human resources.

Hi there,

although I do not know C and thus will always be rather
limited in my ability to help, I will try my best to help
with the wiki (documentation) effort and similar.

Personally I use SVN checkouts of ruby-gnome and I am very
happy with them so far. I do compile gtk/glib/atk etc… from
source, which also means that sometimes things break here
(like glib-2.16.1 makes a few problems compared to 2.14.4
here for me) so my plattform is not very stable -
sometimes I break ruby-gnome too accidentally, especially
gtksourceview related. ( I <3 gtksourceview )

I think I would not be able to be a reliable maintainer due to
several reasons, but I try my best to help out others.

A Sidenote: Maybe if there are a handful of people interested
in a channel specifically aimed for ruby and gnome/gtk? for
ruby and qt/kde it exists on freenode called #kde-ruby
(But we have the much better specific ruby documentation,
thanks to the wiki and all the people who worked on it )

Kouhei_S · March 19, 2008, 10:40pm

Hi,

In [email protected]
“Re: [ruby-gnome2-devel-en] Release manager” on Wed, 19 Mar 2008
22:29:20 +0100,
Marc H. [email protected] wrote:

The Ruby-GNOME2 project lacks human resources.

although I do not know C and thus will always be rather
limited in my ability to help, I will try my best to help
with the wiki (documentation) effort and similar.

Great!
I’ll send you an account for write access to the Wiki.

Personally I use SVN checkouts of ruby-gnome and I am very
happy with them so far. I do compile gtk/glib/atk etc… from
source, which also means that sometimes things break here
(like glib-2.16.1 makes a few problems compared to 2.14.4
here for me) so my plattform is not very stable -
sometimes I break ruby-gnome too accidentally, especially
gtksourceview related. ( I <3 gtksourceview )

If you find some compile errors, please report them.

I think I would not be able to be a reliable maintainer due to
several reasons, but I try my best to help out others.

If you need write access to the Subversion repository, I’ll
add you to the developers. If you want to work on
documentation in the Subversion repository (e.g. updating
NEWS, README and so on), you need write access.

Thanks,

kou

Kouhei_S · March 19, 2008, 10:43pm

Hi,

In [email protected]
“Re: [ruby-gnome2-devel-en] Release manager” on Thu, 20 Mar 2008
06:38:17 +0900 (JST),
Kouhei S. [email protected] wrote:

Marc H. [email protected] wrote:

The Ruby-GNOME2 project lacks human resources.

although I do not know C and thus will always be rather
limited in my ability to help, I will try my best to help
with the wiki (documentation) effort and similar.

Great!
I’ll send you an account for write access to the Wiki.

Marc, could you tell me your E-mail address?

Thanks,

kou

Kouhei_S · March 19, 2008, 11:27pm

On Wed, Mar 19, 2008 at 10:29:20PM +0100, Marc H. wrote:

A Sidenote: Maybe if there are a handful of people interested
in a channel specifically aimed for ruby and gnome/gtk? for
ruby and qt/kde it exists on freenode called #kde-ruby
(But we have the much better specific ruby documentation,
thanks to the wiki and all the people who worked on it )

On GIMPNet/GNOMENet, there is the #ruby-gnome2 channel.
See also:
http://ruby-gnome2.sourceforge.jp/hiki.cgi?irc

Paul

–
PhD Student @ Eindhoven | email: [email protected]
University of Technology, The Netherlands | JID: [email protected]

Kouhei_S · March 19, 2008, 11:48pm

Hi,

In [email protected]
“Re: [ruby-gnome2-devel-en] Release manager” on Wed, 19 Mar 2008
16:15:00 +0100,
Joachim G. [email protected] wrote:

Supported version information may be useful.

Did anything change?

For Ruby/Poppler, 0.6.2 was supported:

poppler/ChangeLog:
2007-11-11 Kouhei S. [email protected]

      * README: updated supported poppler-glib version: 0.5.2 -

0.6.2.

For Ruby/GTK+, Guillaume said about it. (The status page(*)
on the Wiki isn’t updated yet.)

(*) http://ruby-gnome2.sourceforge.jp/hiki.cgi?Status+of+Ruby%2FGTK

Thanks,

kou

Kouhei_S · March 19, 2008, 11:50pm

Hi,

In [email protected]
“Re: [ruby-gnome2-devel-en] Release manager” on Wed, 19 Mar 2008
18:15:32 +0100,
“Guillaume C.” [email protected] wrote:

Because the rest of the bindings normally check for the stable version
(e.g. check for “2,10,0” for example), I think my 2,11,0 checks might
be changed to 2,12,0 for the sake of orthogonality - but I’m not
changing it for the moment, waiting for comments.

Please change.

Thanks,

kou

Kouhei_S · March 22, 2008, 1:09pm

15 mar 2008 kl. 03.20 skrev Kouhei S.

Hi,

Sorry for slow reply, was traveling during the week.

This will bring the project closer to the rest of the community, as

Is there any auto-build support on the GNOME infrastructure?

I’m not sure if there are but I can’t recall I’ve seen that, it might
be possible to setup though.

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.

Thanks.
If we decide to move to the GNOME infrastructure, could you
help the Ruby-GNOME2 subversion repository migration?

I can definitely help get the right people involved, I don’t have the
admin rights to do the job myself though.

Cheers,
Micke

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

Kouhei_S · March 23, 2008, 11:12am

Hi,

In [email protected]
“Re: [ruby-gnome2-devel-en] Release manager” on Sat, 22 Mar 2008
13:07:25 +0100,
Mikael H. [email protected] wrote:

Sorry for slow reply, was traveling during the week.

No problem.

Is there any auto-build support on the GNOME infrastructure?

I’m not sure if there are but I can’t recall I’ve seen that, it might
be possible to setup though.

Ruby-GNOME2 supports some GTK+ versions. If we can check
building with all supported version, it will be very useful.

If we decide to move to the GNOME infrastructure, could you
help the Ruby-GNOME2 subversion repository migration?

I can definitely help get the right people involved, I don’t have the
admin rights to do the job myself though.

OK. Thanks!

–
kou

Kouhei_S · March 25, 2008, 12:58pm

On Fri, Mar 14, 2008 at 10:28:44PM +0900, Kouhei S. wrote:

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

I just checked out the new ruby-gnome2 from SVN to see what my bindings
needed
to change to work with them… Only to discover that suddenly and
completely
seperate from my ruby-gstreamer0.10 bindings the Ruby/GStreamer stuff
has been
updated to 0.10…

This is a big WASTE of effort. It seems they have mostly redone the work
i
already did a few years ago. Now i don’t really care if other people
waste
their time, but i don’t like to waste my time on doing the same things
as
others.

Having two seperate gstreamer 0.10 bindings is just ridicoulous and
stupid. Not
only is it bad for users (2 bindings, which one should be used). It
again
wastes developer effort (which we’re already short on), and the new
updated
bindings are likely to repeat bugs that i’ve fixed a long time ago in
mine. I
had a quick look in the source and i can easily point out various issues
that i
fixed a long time ago.

IMHO we should get the two efforts merged ASAP (There should be only
ever have
been one effort in the first place, but oh well)… What was the
rationale of
doings this anyways, i’m pretty sure people know about my bindings. And
i’d hope
the ruby-gnome2 team doesn’t have NIH syndrome.

Now i’ve initially done my bindings outside of the main tree because of
various
reasons discussed a long long time ago. The main reason for that still
exists,
i think it’s very bad from a release management pov. that all the
modules are
tied together. Releasing everything as seperate lean packages has the
advantage
of making releases much easier to do and much less effort for
distributions.
Unless that’s changed my opinion will stay the same: I think that it is
in
the gstreamer bindings best interest to keep seperate from the main
bunch.

If we can change to a more sane releases and release everything as
seperate package, i’m happy to merge my bindings back into the main
repository.
In which case i guess i’ll just have to live with the sf’s horrible
bugtracking
system (unless we move to gnome, hint hint). If not, then oh well,
that’s live.
but we should stop wasting eachothers time by doing the same work and
find some
middleground to get stuff merged.

Very much unamused,
Sjoerd

The function of the expert is not to be more right than other people,
but to be wrong for more sophisticated reasons.
– Dr. David Butler, British psephologist

Kouhei_S · March 25, 2008, 4:07pm

On Tue, Mar 25, 2008 at 11:17:45PM +0900, Kouhei S. wrote:

hope the ruby-gnome2 team doesn’t have NIH syndrome.

NIH syndrome?

I tried to contribute your bindings (not the bindings in the
Ruby-GNOME2 repository) and submitted a patch two years
ago. But the patch was derelict until two days ago. So I
understood your bindings are not maintained. This is the
reason why I started to updated Ruby/GStreamer.

I haven’t had a lot of time for them that’s true and i never made a lot
of time
because there weren’t big issues with them. Otoh still you could have
asked me
about my plans first before starting a new effort (i would have been
very happy
to give you svn access). And even that is not so bad, but you really
should
have pulled my bindings into the repository instead of ignoring
everything i
already did. And thus set yourself up to hit the same issues that are
already
fixed in my bindings. I can already tell you that the in the current
state
Ruby/Gstreamer will get deadlocks and potentially crashes if used for
anything
but a non-trivial program.

ruby-gstreamer0.10 might be undermaintained, but at least it’s a stable
base to
build upon.

If we can change to a more sane releases and release everything as seperate
package, i’m happy to merge my bindings back into the main repository.

If you want to release it as a separate package, you can do.

I’m interested in what your ideas are here. Does this mean you agree
with not
including Ruby/Gstreamer in ruby-gnome2 release but have it go seperate.
Or do
include it in the big ruby-gnome2 release, but also allow it to seperate
releases inbetween ?

But Ruby/GStreamer may depend on unreleased Ruby/GLib.

It shouldn’t be a big problem to have Ruby/Gstreamer and/or
ruby-gstreamer0.10
always working with the last release version of Ruby/GLib…

Sjoerd

The biggest difference between time and space is that you can’t reuse
time.
– Merrick Furst

Kouhei_S · March 26, 2008, 12:21pm

Hi,

In [email protected]
“Re: [ruby-gnome2-devel-en] Release manager” on Tue, 25 Mar 2008
16:06:26 +0100,
Sjoerd S. [email protected] wrote:

have pulled my bindings into the repository instead of ignoring everything i
already did.

Your bindings have several problems to use in the
Ruby-GNOME2 Project Team: Non-consistent coding style, low
Ruby/GLib integration (e.g. rbgst_new_gstobject), out of
Ruby-GNOME2 Project’s naming convention and so on.

         And thus set yourself up to hit the same issues that are already
fixed in my bindings. I can already tell you that the in the current state
Ruby/Gstreamer will get deadlocks and potentially crashes if used for anything
but a non-trivial program.

Please tell us them.

And please tell us a feature list that your bindings has
but ours doesn’t have.

If we can change to a more sane releases and release everything as seperate
package, i’m happy to merge my bindings back into the main repository.

If you want to release it as a separate package, you can do.

I’m interested in what your ideas are here. Does this mean you agree with not
including Ruby/Gstreamer in ruby-gnome2 release but have it go seperate. Or do
include it in the big ruby-gnome2 release, but also allow it to seperate
releases inbetween ?

I prefer to the later if Joachim says OK.

Ruby/GStreamer’s version number will be like the followings:

0.17.0: with Ruby-GNOME2 0.17.0 release
0.17.1: separated release. It will depend on Ruby/GLib 0.17.0.
0.17.2: separated release. It will depend on Ruby/GLib 0.17.0.
…
0.18.0: with Ruby-GNOME2 0.18.0 release
0.18.1: separated release. It will depend on Ruby/GLib 0.18.0.
0.18.2: separated release. It will depend on Ruby/GLib 0.18.0.
…

Thanks,

kou

Kouhei_S · March 26, 2008, 1:00pm

Kouhei S. wrote:

I’m interested in what your ideas are here. Does this mean you agree with not
including Ruby/Gstreamer in ruby-gnome2 release but have it go seperate. Or do
include it in the big ruby-gnome2 release, but also allow it to seperate
releases inbetween ?

I prefer to the later if Joachim says OK.

We can pack the gstreamer from current trunk into the release for now.
It’s experimental, not stable.

Which version you chose to officially support is up to Kouhei. For
releasing with the package it need to be maintained and should become
complete and stable in near future.

Release manager

Thanks,

But applying an account for GNOME infrastructure is a bit

bother for me…

Supported version information may be useful.

Thanks,

Supported version information may be useful.

Thanks,

Thanks,

Supported version information may be useful.

Thanks,

Thanks,

But applying an account for GNOME infrastructure is a bit

bother for me…

Very much unamused, Sjoerd

Sjoerd

Thanks,

Very much unamused,
Sjoerd