RT 3.4.1 expected in one week

So far, the response to RT 3.4 has been pretty good. So far, there’s
nothing that’s an all-out showstopper, but there are a few small issues
we’d like to fix in a patch release fairly soon.

The following are already fixed:

* Some URL paths weren't prefixed with RT::WebPath
* A few warnings needed to be quieted down
* SelectOwner widgets displayed "Nobody" twice

The following are on our list for 3.4.1:

* Hungarian translation was accidentally removed
* Several display issues when using non-English
  languages on RT's homepage
* Additional upgrade notes about migrating from RT 2.0
  to RT 3.4

* Possible additional small bugfixes.


Anyone else have a pet issue with 3.4.0 that they want to see
fixed before 3.4.1?


Jesse

Do we have a projected ship date for 3.4.1, yet?

Brent B. Powers
Manager, Information Technology
Department of Pathology
Columbia University

Do we have a projected ship date for 3.4.1, yet?

Yesterdayish. I still need to add some notes about upgrading from RT
2.0, but some customer work has taken precedence. “Soon”

Anyone else have a pet issue with 3.4.0 that they want to see
fixed before 3.4.1?

Jesse, did you see my patch to add /WIDTH to Elements/TicketList? I didn’t
see a reply, don’t know if it fell through the cracks. Is that worth spending
a few minutes to hack in to 3.4.1?

I sent it to you directly, probably should have sent it to rt-devel.

-jd

Anyone else have a pet issue with 3.4.0 that they want
to see
fixed before 3.4.1?

Jesse, did you see my patch to add /WIDTH to
Elements/TicketList? I didn’t see a reply, don’t know if it
fell through the cracks. Is that worth spending a few minutes
to hack in to 3.4.1?

I sent it to you directly, probably should have sent it to
rt-devel.

Actually, to rt-bugs@fsck.com. Really, 3.4.1 is just for bugfixes and
cleanups. Rather than a /WIDTH attribute, what about using /STYLE to
do width with CSS?

Jesse, did you see my patch to add /WIDTH to
Elements/TicketList? I didn’t see a reply, don’t know if it
fell through the cracks. Is that worth spending a few minutes
to hack in to 3.4.1?

I sent it to you directly, probably should have sent it to
rt-devel.

Actually, to rt-bugs@fsck.com. Really, 3.4.1 is just for bugfixes and
cleanups. Rather than a /WIDTH attribute, what about using /STYLE to
do width with CSS?

Ok, rt-bugs.

I can’t claim to understand CSS enough to have an opinion one way or the
other. I’ll rehash what I did for those on rt-users:

We have added a couple of custom fields to the main page for privileged
users[*] as well as a new table (stalled tickets via Elements/MyStalls, for
one) the columns on the main page were all out of whack. One table would have
our custom fields at one spot, the other table would have it somewhere totally
different depending on how long the Subjects were. My little /WIDTH hack told
Elements/TicketList to insert WIDTH tags in to the

and made the three
tables’ columns line up perfectly from top to bottom. It gave things a nice
clean, consistant look.

I’m sure CSS is the more “2005 way” of doing the same thing, and I’d be game
for that. It’s not worth burning any midnight oil for, but if it would be
easy to hack in (in a more elegent fashion that my original approach) I’d take
it.

-jd