0.2.9-RC1 - note about tags

[laurent....@gmail.com]

Hi,


I've installed 0.2.9-RC1 version.

After creating a tag, when I delete it, it says : "Are you sure you want to delete class of service 'Important'?"

Wouldn't it be "Are you sure you want to delete tag 'Important'?"

Except this, all is ok...

[jel...@gmail.com]

wow, you are testing the RC! Thank you! 

Good catch - posted a fix to github [1] - I will create a new RC soon containing this fix + some more.

[1]: https://github.com/jelkosz/kanbanik/commit/eeabb9af8961d4e8c0decb16085ea2831b00c670

[laurent....@gmail.com]

Thanks !

[jel...@gmail.com]

So I have created the RC2: https://sourceforge.net/projects/kanbanik/files/kanbanik-application-0.2.9-RC2.zip/download

If you could give it a try if you see any more bugs it would be nice.

Thanx

[laurent....@gmail.com]

ok, I'll do so.

I have a question.

I'm working with 0.2.8.

If I decide to use 0.2.9, will it be transparent or is there any database change (or anyting else) that could make it fail ?

[jel...@gmail.com]

On Friday, May 22, 2015 at 11:02:08 AM UTC+2, laurent....@gmail.com wrote:

ok, I'll do so.

I have a question.

I'm working with 0.2.8.

If I decide to use 0.2.9, will it be transparent or is there any database change (or anyting else) that could make it fail ?

It should work transparently - there is a database change (because of tags) but it should be done incrementally (noSQL can do this ;) ) so no migration scripts needed. I have updated my installs just by dropping in the new war file and everything worked.

But maybe try to backup your DB somewhere first if you have some data you don't want to loose.

[laurent....@gmail.com]

It should work transparently - there is a database change (because of tags) but it should be done incrementally (noSQL can do this ;) ) so no migration scripts needed. I have updated my installs just by dropping in the new war file and everything worked.

OK - worked transparently - no data lost - working in 0.2.9-RC2 now

A question about tags : when I put a tag, it's only visible/"choosable" on the item I've modified. If I open or create an item, tag list is empty and I have to create a new (eventually the same) tag.

Perhaps it's normal ?

[jel...@gmail.com]

yes, this is how is it designed (actually, this is the MMF (minimum marketable feature) for tags). 

I don't expect the tags being reused too much. For example if some task is blocked, than you will make a tag with name like "B" and a description why is it blocked. The name would be re-usable, the reason not. 

When it will start to be painful because the same tag will be reused in many tasks I may implement persistent tags, but I don't see to much reasons to do it so far...

[laurent....@gmail.com]

undertood !

thx