Re: Release procedure

2005-06-07 Thread Pavel Tsekov
Hello, On Mon, 6 Jun 2005, Leonard den Ottolander wrote: Hello Miguel, On Mon, 2005-06-06 at 22:58, Miguel de Icaza wrote: I have made a tarball of the current trunk release and fixing a few issues in make distcheck, the question that remains is: what version should we use? Please

Re: Release procedure

2005-06-07 Thread Pavel Tsekov
Hello, On Mon, 6 Jun 2005, Roland Illig wrote: We continue to use the 4.6.xx family name. I think it might be time to change one of those numbers to identify the changes done since the 4.6.0 release in a more significant way. I would prefer 4.7. (Just to leave the long past of 4.6.*

Re: Release procedure

2005-06-07 Thread Miguel de Icaza
Hello, Please use MC_4_6_1_PRE for the release of 4.6.1. Then we can use HEAD for 4.6.2 and onwards. I second that. Sounds good. ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel

Re: Release procedure

2005-06-07 Thread Miguel de Icaza
Hello, I have made a tarball of the current trunk release and fixing a few issues in make distcheck, the question that remains is: what version should we use? What did you fix? Make distcheck was broken, look at the dist-hook target, it would not build with VPATH/different prefixes.

Re: Release procedure

2005-06-07 Thread Miguel de Icaza
hello, I have a tarball made from the branch: http://primates.ximian.com/~miguel/mc/tar.mc-4.6.1-pre5a.tar.gz I can rename this to 4.6.1 if people want. Miguel. ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel

Re: Release procedure

2005-06-07 Thread Pavel Tsekov
Hello, On Tue, 7 Jun 2005, Miguel de Icaza wrote: hello, I have a tarball made from the branch: http://primates.ximian.com/~miguel/mc/tar.mc-4.6.1-pre5a.tar.gz The right link is: http://primates.ximian.com/~miguel/mc/mc-4.6.1-pre5a.tar.gz

Re: Release procedure

2005-06-07 Thread Jindrich Novy
Hello Leonard, mc-devel, On Mon, 2005-06-06 at 23:34 +0200, Leonard den Ottolander wrote: Hello Miguel, On Mon, 2005-06-06 at 22:58, Miguel de Icaza wrote: I have made a tarball of the current trunk release and fixing a few issues in make distcheck, the question that remains is: what

Re: Release procedure

2005-06-07 Thread Roland Illig
Jindrich Novy wrote: --- mc-4.6.1a/src/widget.c.fixes2005-06-06 15:08:52.202559824 +0200 +++ mc-4.6.1a/src/widget.c 2005-06-06 15:08:29.120068896 +0200 @@ -2363,7 +2363,7 @@ buttonbar_set_label_data (Dlg_head *h, i void buttonbar_set_label (Dlg_head *h, int idx, const char *text,

Re: Last TODO items before release [was Re: Release procedure]

2005-06-07 Thread Leonard den Ottolander
On Tue, 2005-06-07 at 20:02, Leonard den Ottolander wrote: Before releasing 4.6.1 there are a few things to be done: - Backporting gcc-4 signedness fixes I understand many of the developers doubt the quality of the warnings from gcc-4, and hence the fixes proski created for them. We can look at

Re: Release procedure

2005-06-07 Thread William Scott Lockwood III
wget http://primates.ximian.com/~miguel/mc/tar.mc-4.6.1-pre5a.tar.gz --14:28:46-- http://primates.ximian.com/%7Emiguel/mc/tar.mc-4.6.1-pre5a.tar.gz = `tar.mc-4.6.1-pre5a.tar.gz' Resolving primates.ximian.com... 130.57.169.34 Connecting to primates.ximian.com[130.57.169.34]:80...

Re: Last TODO items before release [was Re: Release procedure]

2005-06-07 Thread Roland Illig
Leonard den Ottolander wrote: Roland fixed a memory leak in HEAD but he doesn't know where again g. I have thoroughly check the changes to mcedit, where I assumed the memory leak to have been. The only things I found were two instances where I had replaced use of the catstrs() function with

RE: Release procedure

2005-06-06 Thread David Martin
___ Join Excite! - http://www.excite.com The most personalized portal on the Web! ---BeginMessage--- Hmm, I hope to have the Spanish translation up to date by now. I think that most translator are part time or even little time collaborators and

Re: Release procedure

2005-06-06 Thread Miguel de Icaza
Hello, Roland, I like your proposal, for a major release version. But I got the feeling that we could go back to bi-weekly releases, so with a quick release schedule, translators just need to make sure they can catch the next train if their translations are not available. I have

Re: Release procedure

2005-06-06 Thread Roland Illig
Roland Illig wrote: day 0 (translator's prerelease) * Set the version number in configure.ac to ${dotted_version}-translators. DON'T commit configure.ac. I have removed this item from my local copy. There's no need to have a version number in a translator's prerelease. I have also

RE: Release procedure

2005-06-06 Thread Leonard den Ottolander
Hello David, On Mon, 2005-06-06 at 17:55, David Martin wrote: I think that most translator are part time or even little time collaborators and some/most of them may have problems with this tight scheduling. On the other hand, I know that scheduling is a must. ... Is it possible to open the

Re: Release procedure

2005-06-06 Thread Roland Illig
Miguel de Icaza wrote: Hello, Roland, I like your proposal, for a major release version. But I got the feeling that we could go back to bi-weekly releases, so with a quick release schedule, translators just need to make sure they can catch the next train if their translations are not

Re: Release procedure

2005-06-06 Thread Leonard den Ottolander
Hello Miguel, On Mon, 2005-06-06 at 22:58, Miguel de Icaza wrote: I have made a tarball of the current trunk release and fixing a few issues in make distcheck, the question that remains is: what version should we use? Please use MC_4_6_1_PRE for the release of 4.6.1. Then we can use HEAD