nano-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Nano-devel] GNU nano 2.1.2


From: Jordi Mallach
Subject: Re: [Nano-devel] GNU nano 2.1.2
Date: Thu, 26 Jun 2008 17:27:36 +0200
User-agent: Mutt/1.5.18 (2008-05-17)

On Thu, Jun 26, 2008 at 11:07:08AM -0400, Chris Allegretta wrote:
> Im (more than) a little rusty here, but do we need that kind of coordination
> for the unstable series?
> 
> I honestly don't remember if there was some agreed-on process for
> synchronizing prior to a release, so perhaps now is a good time to revisit
> that process regardless.  Where were before and will that serve our needs
> now?

Well, we only track the unstable series now, so if synchronisation needs
to happen, it needs to happen with 2.1.x releases. If nothing goes very
wrong, there should be no string changes to 2.0.x, so we can forget
about that in terms of localisation -- Benno has fixed a few
long-standing TP bugs so now it'll be possible to send updates to 2.0.x
and not interfere with the latest version offered for "nano".

But anyway, if we automate the process, there's nothing to coordinate:
just before a release, we fetch whatever there is in the TP with rsync,
and create the tarball with that. Sending Benno
(address@hidden) an email to notify would be a nice
detail too, so he installs the template.

Automating this, or at least adding it to your pre-tar.gz generation
process (write NEWS, etc) would enable you to release without depending
on anyone, translators would have their latest files in the releases and
AFAICT, everyone would be happy. Me specially, one thing less to do! :)

Jordi
-- 
Jordi Mallach PĂ©rez  --  Debian developer     http://www.debian.org/
address@hidden     address@hidden     http://www.sindominio.net/
GnuPG public key information available at http://oskuro.net/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]