[PATCH][Fwd: Re: Xterm window title enhancement to hostname:/path II.]

2005-06-06 Thread Jindrich Novy
Hello mc-devel, I haven't noticed any objection against this patch and many people consider it helpful. Any chance to see it committed? Thanks, Jindrich -- Jindrich Novy [EMAIL PROTECTED], http://people.redhat.com/jnovy/ The worst evil in the world is refusal to think. ---BeginMessage---

Release procedure

2005-06-06 Thread Roland Illig
To prepare the upcoming release of mc, I reviewed the file maint/RELEASE_PROCEDURE and complete rewrote it. The main changes are: * Translations are updated _before_ a release * The CVS gets tagged with a release * A new CVS branch is created for the release The CVS branch will be used to

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: New Maintainer for MC Project?

2005-06-06 Thread Pavel Machek
Hi! * Tell the Leadership that thanks, but no thanks. ... If meritocracy is the rule I think we should decide this on merits, don't you? Which means you shouldn't decide this all by yourself. I would like to get some input from others as well. I agree with Miguel here...

Re: New Maintainer for MC Project?

2005-06-06 Thread Pavel Machek
Since it is not my policy to argue with fools, that's all I will say along those lines. Learn to use email, thanks. Pavel ___ Mc-devel mailing list

Re: New Maintainer for MC Project?

2005-06-06 Thread Roland Illig
Miguel de Icaza wrote: * You exhibit the behavior of many people who have no ideas whatsoever about the project but like big titles. Public Relations Coordinator, the leadership, and Project Manager. * Tell the Leadership that thanks, but

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