Getting ready for a release

2007-09-04 Thread Pavel Tsekov
Hello,

As it has been discussed on the mailing list a new release of MC is long 
overdue. So... I plan to release a new version of MC by mid October. This gives 
us about a month (till the end of September) for final testing, bug reporting, 
fixing, updating translations and other related tasks - the last two are to be 
used by translators to update the MC translation. I hope that everyone 
interested will participate in this process so that we can finally release a 
new version.

There are three full weeks by the end of September which can be used to release 
at most 3 pre-releases and give each a week of testing and polishing (depending 
on the user feedback). I am going to wait till the end of this week for your 
suggestions on how to use the remaining three weeks and make a plan according 
to them, then I'll publish the first pre-release on Monday. This reminds me 
that we have another problem to solve -
how are we going to number the new release ? Please, share your thoughts on 
that too.

-- 
GMX FreeMail: 1 GB Postfach, 5 E-Mail-Adressen, 10 Free SMS.
Alle Infos und kostenlose Anmeldung: http://www.gmx.net/de/go/freemail
___
Mc-devel mailing list
http://mail.gnome.org/mailman/listinfo/mc-devel


Re: Getting ready for a release

2007-09-04 Thread Oswald Buddenhagen
On Tue, Sep 04, 2007 at 10:57:42AM +0200, Pavel Tsekov wrote:
 how are we going to number the new release ?
 
4.7. no exaggerated humbleness, please.

-- 
Hi! I'm a .signature virus! Copy me into your ~/.signature, please!
--
Chaos, panic, and disorder - my work here is done.
___
Mc-devel mailing list
http://mail.gnome.org/mailman/listinfo/mc-devel


Re: Getting ready for a release

2007-09-04 Thread Egmont Koblinger
On Tue, Sep 04, 2007 at 10:57:42AM +0200, Pavel Tsekov wrote:

 how are we going to number the new release ?

/me votes for 4.6.2. As far as I followed the development, there's nothing
really brand new huge or conceptual change that would make calling it 4.7
reasonable, it only contains plenty of small bugfixes.

Being a maintainer of a distro what I see is that by now every Linux
distribution that matters has switched to using UTF-8, and mc is amongst the
really very very few packages that still need to be patched to work
correctly in such environments. (I think mc is the only one where lack of
utf-8 support is immediately seen by the users and makes it nearly unusable
in such systems). Hence distros will still have to patch mc for UTF-8, just
as they did with 4.6.1. It also implies that users won't be able to simply
download and compile and use this brand new mc - they'll have to wait for
their distributors to update the package, which probably don't happen
immediately due to the work required on their side.

So IMHO UTF-8 support out of the box is a must for the version named 4.7.


-- 
Egmont
___
Mc-devel mailing list
http://mail.gnome.org/mailman/listinfo/mc-devel


Re: Getting ready for a release

2007-09-04 Thread Denys Vlasenko
On Tuesday 04 September 2007 10:18, Oswald Buddenhagen wrote:
 On Tue, Sep 04, 2007 at 10:57:42AM +0200, Pavel Tsekov wrote:
  how are we going to number the new release ?
  
 4.7. no exaggerated humbleness, please.

4.7.0.

Fixes can go to stable 4.7.x,
big changes to eventual 4.8.0...
--
vda

___
Mc-devel mailing list
http://mail.gnome.org/mailman/listinfo/mc-devel


Re: Getting ready for a release

2007-09-04 Thread Pavel Tsekov
 Original-Nachricht 
 Datum: Tue, 4 Sep 2007 14:43:53 +0200
 Von: Egmont Koblinger
 An: Pavel Tsekov
 Betreff: Re: Getting ready for a release

 Being a maintainer of a distro what I see is that by now every Linux
 distribution that matters has switched to using UTF-8, and mc is amongst
 the
 really very very few packages that still need to be patched to work
 correctly in such environments. (I think mc is the only one where lack of
 utf-8 support is immediately seen by the users and makes it nearly
 unusable in such systems).

Lack of UTF-8 support is a big minus on the part of MC, but I think that
your statement is a bit overestimated. It's more like MC is not following the 
latest trend, IMO.

 Hence distros will still have to patch mc for UTF-8, just
 as they did with 4.6.1. It also implies that users won't
 be able to simply download and compile and use this brand new mc -
 they'll have to wait for their distributors to update the package,
 which probably don't happen immediately due to the work required on
 their side.

MC on all major distros comes with the UTF-8 patch. MC in CVS is not 
different than the snapshots most of the distros use to build their
packages - maybe there are some who stick to the 4.6.1 release though.

 So IMHO UTF-8 support out of the box is a must for the version named 4.7.

I haven't looked at the UTF-8 patch recently (but I will) so I cannot
comment it. Do you think that UTF-8 patch 'as is' is the right way to
implement UTF-8 for MC ? And what about ncurses - it is my opinion 
that it must not be dropped in favor of S-Lang...

-- 
Pt! Schon vom neuen GMX MultiMessenger gehört?
Der kanns mit allen: http://www.gmx.net/de/go/multimessenger
___
Mc-devel mailing list
http://mail.gnome.org/mailman/listinfo/mc-devel


Re: Getting ready for a release

2007-09-04 Thread Denys Vlasenko
On Tuesday 04 September 2007 09:57, Pavel Tsekov wrote:
 Hello,
 
 As it has been discussed on the mailing list a new release of MC is long 
 overdue. So... I plan to release a new version of MC by mid October. This 
gives us about a month (till the end of September) for final testing, bug 
reporting, fixing, updating translations and other related tasks - the last 
two are to be used by translators to update the MC translation. I hope that 
everyone interested will participate in this process so that we can finally 
release a new version.

I am currently watching this Google tech talk:

http://kernel.org/doc/video.html

April 19, 2007 Release Management in Large Free Software Projects - Martin 
Michlmayr (Debian)

ABSTRACT: Time based releases are made according to a specific time interval, 
instead of making a release when a particular functionality or set of 
features have been implemented. This talk argues that time based release 
management acts as an effective coordination mechanism in large volunteer 
projects and shows examples from seven projects that have moved to time based 
releases: Debian, GCC, GNOME, Linux, OpenOffice, Plone, and X.org.

Direct link to video: 

http://video.google.com/videoplay?docid=-5503858974016723264


Maybe it will be interesting to you too.
--
vda
___
Mc-devel mailing list
http://mail.gnome.org/mailman/listinfo/mc-devel


Re: Getting ready for a release

2007-09-04 Thread Alexander Kriegisch
Hi!

 April 19, 2007 Release Management in Large Free Software Projects

I cannot do much on the C programming side (I am rather into Java, shell
and a few other things, but just in case you are interested in agile
project management: I am a Certified Scrum Master (cf. my web site,
http://scrum-master.de) and might be able to offer free services to your
project, depending on my clients, ongoing commercial projects and
coaching classes I am involved in.

Pavel, this is not supposed to turn into a sales pitch thing, so if you
are interested at all, send a private e-mail so we can discuss this
off-line.

Regards
--
Alexander Kriegisch
___
Mc-devel mailing list
http://mail.gnome.org/mailman/listinfo/mc-devel