On Sat, 23 Jan 2010 12:33:18 +0100
Julien Valroff <[email protected]> wrote:

> Le samedi 23 janvier 2010 à 12:12 +0100, Julien Valroff a écrit :
> > Hi,
> > 
> > Le samedi 23 janvier 2010 à 12:31 +0200, Dudi Goldenberg a écrit :
> > > Hello list,
> > > 
> > >  
> > > 
> > > I have just upgraded to the latest version from kirya.net repos
> > > (dspam_3.9.0-1~pre2_i386.deb and friends).
> > > 
> > >  
> > > 
> > > Now I don’t get Hebrew in the web UI, also – I seem to have lost
> > > the ability to select users from the drop box.
> > > 
> > I am to blame as previous packages were based on git HEAD. This
> > feature will be part of an upcoming release (maybe 3.9.1, I am not
> > sure).
> > > 
> > > Even if I set encodings manually to _any_ set of Hebrew, including
> > > UTF-8, it's still a no go.
> > > 
> > Try and set: 
> > $CONFIG{'HISTORY_HTMLIZE'} = "no";
> > 
> > in /etc/dspam/webfrontend.conf
> 
> Re-reading your email, I think I had misunderstood it.
> 
> Do you mean the webui isn't translated into Hebrew?
> 
> Strange as the Hebrew templates are shipped in the dspam-webfrontend
> package. I have no problem when I set Firefox preferred language to
> Hebrew, the Webui is translated.

Yes, the translation is in the tarball.

> Check your webfrontend.conf file is based on the one shipped with the
> package, as some changes were made between 3.9.0 and current git
> (previous packages being based on git, my bad).

We have a few branches in git:

- MASTER which is the cutting edge, were all commits go
- and the RELENG branches, which we use to cut the releases from.

You might notice in the commit logs that there is a MFM filed (which
has a value of N days - the interval that change is supposed to stay in
MASTER for real-world testing before being merged down in RELENG
branches).
MASTER --(maybe)--> RELENG_3 --(maybe)--> RELENG_3_9 --(maybe)--> RELENG_3_9_1

When the release engineering process for a new release is started, the
RELENG_M_n_u is created. Periodically, things are merged in this
branch, from which the release will eventually be made. At some point
(a few days before the first alpha) we declare a feature freeze for
this branch, and from that point only bug-fixes go in in this branch,
while development of new things may continue in upper branches; for
example, there are some new things in RELENG_3_9 and RELENG_3_9_1 that
were committed to late in 3.9.0 release process to make it in 3.9.0.
Once 3.9.0 was released, no commit goes in RELENG_3_9_0, which is
frozen when it was tagged with 3_9_0R.

So if you want to track the thing that will become the next release,
track RELENG_3_9_1. If you want more, track the upper branches
(RELENG_3_9 or 3). If you want cutting edge, track MASTER.

Generally, all RELENG_M_m_u branches must compile and run stably,
RELENG_M_m should, while MASTER may.


HTH,

-- 
IOnut - Un^d^dregistered ;) FreeBSD "user"
  "Intellectual Property" is   nowhere near as valuable   as "Intellect"
FreeBSD committer -> [email protected], PGP Key ID 057E9F8B493A297B

Attachment: signature.asc
Description: PGP signature

------------------------------------------------------------------------------
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
_______________________________________________
Dspam-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspam-user

Reply via email to