Get latest news about linnworks, issues, upcoming updated...

[linn_systems]

Well we have finally submitted to a social network frenzy. Find our news feed on twitter.

http://twitter.com/linnworks

p.s. While most people use twitter to report exciting news about toast making and who is going out with whom. We will only report latest issues, known bugs, notices of upcoming updates and upcoming developments. Sorry - no general chatter - so you won't find out what colour of socks I am wearing.

[Mark2356]

For those of us who are not used nor interested in following what socks people are wearing can you tell me if I go through the hassle of signing up with twitter will it automatically email me if you make updates or do I have to be logging in - in which case why is this different from the forum?

Why can the forum not send me an email newsletter when there is an alert - like a product update.

[linn_systems]

twitter will email you, it can also deliver it to your phone instantly. HTC and iPhones have very good twitter apps, new phones also do - although not as good.

Twitter is better than emailing because it's a single point information share, our users can point each other to a specific posts on the twitter and it has very extensive application base (phones, emails, forums, news feeds etc).

p.s. very sorry for making you sign up with twitter - I have been resisting it in everyway I can - its time to surrender the guns and follow the crowd.

[Mark2356]

In case it helps others

I have signed up for the Twitter RSS feed which can be picked up by my Thunderbird email application

[Mark2356]

Can you explain how what I think you call minor updates occur.

Do you announce them via twitter/this forum

Do they just take place automatically with no intervention on our part - does linnworks reboot or maybe I am barking up the wrong tree.

I am asking because our printing went off today and we have changed nothing so are a bit baffled.
(The left margin seemed to get bigger)

[linn_systems]

We don't normally release any functional changes in the system in minor updates. Minor updates are primerly for bix fixes and backend data structure changes. These are release whenever the problems occure/found and generally have the description of the update in the update panel when you start up the software (you can expand the information by double clicking on the update line)

[Mark2356]

Once an update has been installed is it possible to go somewhere and see what has been changed

[linn_systems]

we don't keep a complete change log for every minor update. Throught out the month some updates will be made and then when we release monthly update we publish the complete list in the News section.

[Mark2356]

Do you think you should publish what has been changed.

What is the cost v benefit of keeping us informed and up to date ?

[Mark2356]

I have been thinking about this some more after tonight 3 minor updates were applied.

What have they improved or fixed - well other than about 2 or 3 words on each I am not sure. And now I have clicked yes I cannot get back to find out.

Some of us make an effort to feed back bugs and issues - being kept in touch and able to know what has been changed helps us to do this - if that is you want us to do ?

The time to document an overview of the change - maybe a couple of sentences - is not much in the scale of the time to produce and implement the fix and if it also helps us to feed back then you will actually get that time back. For example sometimes one bug fix or minor change can produce another issue - when (not if) that time that happens you will easily get the time back spent making small updates to the web or the forum on what has been done and keeping us informed. Since it will easier for us if you are keeping us informed for us to keep you informed. It is in both sides interest.

I think you are behind what has become standard practise based on good reason.