Hi Sky Diver
http://tiddlywiki.com in the HelloThere tiddler there is a link to 
ReleaseHistory 
tiddler.

TW5 is in beta stage. We want it to get better and better and so it does. I 
find the best thing we can do is upgrading and cope with the changes little 
by little following the discussions here in the group.
After upgrading lots are experiencing little problems, other problems due 
to changes only show themselves in use and is delved with. Thats is one of 
the ways TW5 will get better and better.
I do not think it would be possible for anyone to anticipate every way a 
user will try to use his/her TiddlyWIki.
As the development goes on also the documentation will grow and get better.

Remember the discussions is not all about problems due to upgrading. lots 
of ideas are discussed and examples shown. Lots and lots to learn from.

Birthe


Den tirsdag den 29. april 2014 10.10.47 UTC+2 skrev Sky Diver:
>
> Thanks Jeremy,
>
> I actually cloned the github repo but couldn't find any release notes (nor 
> could I find any at github.com/TiddlyWiki/tiddlywiki).
> Following you response I searched http://tiddlywiki.com/ and found "Notes 
> for upgrading to 5.0.8-beta".
>
> This is the only release notes I could find. The title and newline issues 
> are mentioned there, but the shift from "[is[current]tagging[]]" to "[all[
> current]tagging[]]" is not there.
>
> Are there any more release notes I should follow when upgrading from 5.0.6 
> to 5.0.10?
>
> Thank you.
>
> On Tuesday, April 29, 2014 10:33:31 AM UTC+3, Jeremy Ruston wrote:
>>
>> Hi Sky
>>
>> > However, I don't think that a successful upgrade should be the result 
>> of a long forum discussion, rather via documentation.
>>
>> All that's happened is that 5.0.6 was released at the beginning of 
>> January; you're upgrading through 4 versions, some of them with 
>> incompatible changes. The issues you ran into were I think all listed in 
>> the release note; it's just that there were rather a lot of release notes 
>> to read through by the time you got round to upgrading.
>>
>> Best wishes
>>
>> Jeremy.
>>
>>
>>
>>
>>
>>
>> On Tue, Apr 29, 2014 at 1:29 AM, Sky Diver <[email protected]> wrote:
>>
>>> Thanks UBi,
>>>
>>> Changing the title as you suggested does fix this issue.
>>> However, I don't think that a successful upgrade should be the result of 
>>> a long forum discussion, rather via documentation.
>>>
>>> The way I'm familiar with is upgrading using release notes.
>>> I looked around and, while I did find the change logs, I couldn't find 
>>> any release notes.
>>> Please let me know if I'm missing them.
>>>
>>> Thank you.
>>>
>>> On Monday, April 28, 2014 12:17:56 PM UTC+3, UBi wrote:
>>>>
>>>> Hi Sky Diver,
>>>>
>>>> starting with 5.0.8-beta, SiteTitle and SiteSubtitle were replaced by 
>>>> $:/SiteTitle and $:/SiteSubtitle. What do you mean by "title not being 
>>>> imported"? Does SiteTitle get imported but doesn't work as expexted? Then 
>>>> prepending it's name with '$:/' should work.
>>>>
>>>> Uwe
>>>>
>>>> Am Montag, 28. April 2014 01:18:19 UTC+2 schrieb Sky Diver:
>>>>>
>>>>>
>>>>> - I'd also like to understand if the title not being imported is a bug 
>>>>> of a feature (although I have a good guess).
>>>>>
>>>>>  -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "TiddlyWiki" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to [email protected].
>>> To post to this group, send email to [email protected].
>>> Visit this group at http://groups.google.com/group/tiddlywiki.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> -- 
>> Jeremy Ruston
>> mailto:[email protected]
>>  
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

Reply via email to