Tickets and milestones

[Paul Scott]

When adding a ticket, please take note of the milestone dropdown!

Not everything that needs to be fixed should go to the framework-x.x.x
milestone. (I know that things get fixed there, but ja, lets try keep cool)

Case in point (not getting fingerpointy or anything, so please no
offense meant!) is ticket #3547...

This is a problem with a patch on the test module (tbl_test). The patch
is trying to add an already there column to a table. This is NOT a
modulecatalogue problem, modcat is only as strong as it's weakest link!

PLEASE be careful when committing patches etc. Please also remember to
claim issues that don't belong somewhere else to fix them. Keep our
codebase "audit" as clean as you can. Remember, this is your legacy as a
developer! It is your CV as an intern and it is your baby as a senior!

If a user is kind enough to create a ticket, please acknowledge it. Also
please put it in the right place (milestone) and fix it with the HIGHEST
priority! Keep the user informed on list and be cool about it. This
means that even if it is a bullshit ticket (whining or just a user
error) thank the user and reply decently. If it is due to user error,
then please think about better tickets to generate to fix the UI so that
the error doesn't occur again.

OK, I have now moved this onto like 3 topics, so excuse me, but please
follow the rules. ;)

--
-- Paul

http://www.paulscott.za.net/
http://twitter.com/paulscott56
http://avoir.uwc.ac.za

[Derek Keats]

I logged that one, and I realise the error is module specific, but
the ease with which modules can break module catalogue is, I think,
a module catalogue bug...maybe. If the column is already there, how did it get
there? Should module catalogue not be able to see it and not try to
create it? But then that could introduce other bugs I suppose.

Off the topic of the specific milestone, there are a
bunch of these things, some of them over a month old.
It should be something that the module owners fix, but they just
get reported and ignored. How do we solve this? We have sites
needing updating, and no way to update them.
It is way too common.

d

This communication is intended for the addressee only. It is confidential. If you have received this communication in error, please notify us immediately and destroy the original message. You may not copy or disseminate this communication without the permission of the University. Only authorized signatories are competent to enter into agreements on behalf of the University and recipients are thus advised that the content of this message may not be legally binding on the University and may contain the personal views and opinions of the author, which are not necessarily the views and opinions of The University of the Witwatersrand, Johannesburg. All agreements between the University and outsiders are subject to South African Law unless the University agrees in writing to the contrary.

[Paul Scott]

Derek Keats wrote:
> there? Should module catalogue not be able to see it and not try to
> create it? But then that could introduce other bugs I suppose.

We could make modulecatalogue more fault tolerant, but that is a very
different ticket. The only drawback to that is the
customException/errors module situation. I made that really tolerant of
misuse/abuse/unuse and it is less effective than it could be. It still
gives the USER a slightly better experience, but the code quality in
some modules has taken a dip because of it. If we do the same with
modulecatalogue, we will spend more time on peer review and less on
other things. This will have to happen.

>
> Off the topic of the specific milestone, there are a
> bunch of these things, some of them over a month old.
> It should be something that the module owners fix, but they just
> get reported and ignored. How do we solve this? We have sites
> needing updating, and no way to update them.
> It is way too common.

That is YAHP (Yet Another Human Problem) that we need to address as a
COMMUNITY. The operative word being community here. We cannot even think
about other stuff until the bugs and then the more minor issues are
solved! Bugs and major issues take priority always! That must be mantra!