[Typo3] CURIFSUB - hiding access restricted (hidden) menu items ???

[Michael Stucki]

Hello Michael,

>> Still, there are 223 open core bugs and although some of them are already
>> fixed and only waiting for being approved and merged into the core, it's
>> still a huge list of untouched bugs.
> 
> Fortunately (or not?), there are a lot of nobugs, dups and wontfixes
> which can be sorted out without coding. There's a lot of effort at the
> moment to reduce these and really leave prepared patches to Ingmar and
> Stucki and the other devs.

ACK. By the way, thanks for your very good support so far, Michael!

> Unfortunately, there are also really old half-open (e.g. acknowledged,
> or pending) bugs that have to be checked for relevance, possibly by the
> people they are assigned to.

The 223 bugs (thanks to Ingmar, there are now only 220 of them :-)) include
all acknowledged and pending bugs. Furthermore there are 81 resolved and 67
closed bugs in the "TYPO3 Core" category. (Do you have access to the
statistics page? I have but I don't know if it's a public page...)

> I think the current system of bugtracking should work, because if you
> change the priority or add a bugnote, the thing gets up to the top of
> the list.

Exactly. Therefore, a bug which is at the end of the sorted list seems not
to be important to be fixed (to be clear: it's not unimportant, it's simply
less urgent).

>> Btw, I think we should organize a bug-squashing party before the next
>> major release, just like the extension review weekend which is in
>> planning stage... :-)
> 
> This is great idea, I don't know if I could come in person, but maybe
> doing such a session with IRC seems to work as well, e.g. in python or
> gentoo.

Never drunk a beer over IRC ;-)

Obviously that's not the same. I like the presence of some other people and
really like meeting some cute folks which you only knew from the mailing
lists...

> PS: I'd really like a -bugs discussion list, because some things, like
> the notorious Opera stuff (spread across half a dozen bugs) should be
> discussed and lists work better for this purpose.

Absolutely. I also thought about that. Will set it up tonight, but it will
be a closed list only for the updaters (e.g. you!) of the bugtracker.

Regards, michael
-- 
Want support? Please read the list rules first: http://typo3.org/1438.0.html