Tuesday 6 September, vers 16h, Matteo Settenvini dactylographia :

> 1.  ( ) text/plain          (*) text/html           
> 
> 
> Tobias Toedter ha scritto:
> 
> On Monday 05 September 2005 19:19, you wrote:
> 
> [..]
> 
> PS: next time, can we have a little more time before the release? I
> got Mathieu notice via email on Thursday, and afaik Savane1.0.8 has
> been rolled out on Friday (at least by looking at the News items on
> gna.org).
> There weren't a lot of strings to translate, that's true, but I was
> away from my keyboard during the weekend, so I couldn't update the
> po file.
> 
> Yes, I think this would be highly desirable. Unfortunately, I can't
> do anything about that, because Mathieu is solely in the position to
> release a new version of Savane. So, we should talk to him about
> this issue. Are you subscribed to the mailing list
> [EMAIL PROTECTED] We should discuss the topic there, in my
> opinion.
> 
> Okay, I'm crossposting this to savane-dev-i18n, so that Mathieu and
> the others can read this.
> 
> Perhaps a "string freeze" of one week would be sensible.
> 
> Yes, I would vote to wait both a weekend and a couple of working
> days before making the release, unless it's a really important one
> (e.g. fixing critical security issues) and it can't wait. So freeze
> should last 3-4 days at least, I guess. Else, please state clearly
> when the release will be made, and people will know how much time
> they have left in order to update their translations...

I dont think it is *really* important to establish so strict rules in
the current situation.

With such rules, there would be in fact no 1.0.8 and no release until
october, or maybe until december. 

I would have waited if it was possible, but it was not, it's as simple
as that, and I think better that this release was made that not at
all (because it's not possible to devote time to make a release in the
next coming weeks). 

I think it's the first time I make a release so fast after announcing
it, it's not a new way to do things, it's just that I had no choice,
apart not making a release at all. And I think best that more people
test the few new features included in 1.0.8 than just keep on 1.0.7,
even if it means that some new strings wont be translated.

Its also hard to promise a real string freeze, as Tobias knows well,
it's usually when people write the translation that they find lot of
typos and very questionable wordings...


> However, there's a next chance for your updates to get into that
> release, because a small (but very annoying) error has been
> discovered shortly afterwards. It will be fixed with the generation
> of new tarballs, replacing the old tarballs for 1.0.8. I'm sure
> Mathieu will include the updated Italian translation as well.
> 
> To Mathieu: as a side note, please don't deliver the new release
> with the same tarball name, people and distros that store md5sum of
> packages won't be particularly happy. Use "1.0.8.1" instead, or
> something like that. You probably already knew that, but I just like
> being boring :-).

As discussed and until someone find something better, it will be
1.0.8+1, because it wont be a release but only a repackaging. 

I think at some point I'll write down some instructions on how to do a
repackaging so any confirmed developer of Savane can take the
opportunity to do a repackaging by himself, if he thinks it
necessary. It's not complicated but it has to be done in a coherent
way each time. Also, a list of acceptable changes for a repackaging
should be made up (well, apart from packaging bugfixes and
translations, I dont think anything fits).


-- 
Mathieu Roy

  +---------------------------------------------------------------------+
  | General Homepage:           http://yeupou.coleumes.org/             |
  | Computing Homepage:         http://alberich.coleumes.org/           |
  | Not a native english speaker:                                       |
  |     http://stock.coleumes.org/doc.php?i=/misc-files/flawed-english  |
  +---------------------------------------------------------------------+

Reply via email to