[hunchentoot-devel] New release 0.8.4
No technical changes. This release just fixes some version numbers I botched yesterday. Sorry, Edi.
Dear Edi: What upgrade strategy do you recommend in following Hunchentoot updates? E.g. should I update every time your announce a fix, only when major version number changes, etc. (that also depends on my paranoia, I know :). The reason I'm asking that is because, to the best of my knowledge, there is no 'update' feature in asdf-install - as an lazy Ubuntu user, I'm too used to 'apt-get update'. My understanding is that updating asdf packages (eps. when some dependecies have also changed) is a complicated procedure - that's why it's better to perform it only for 'critical' things. What is your perspective on that? Bets regards, Victor. On 4/8/07, Edi Weitz <edi@agharta.de> wrote:
No technical changes. This release just fixes some version numbers I botched yesterday.
Sorry, Edi. _______________________________________________ tbnl-devel site list tbnl-devel@common-lisp.net http://common-lisp.net/mailman/listinfo/tbnl-devel
On Mon, Apr 09, 2007 at 01:05:57PM -0500, Victor Kryukov wrote:
Dear Edi:
What upgrade strategy do you recommend in following Hunchentoot updates? E.g. should I update every time your announce a fix, only when major version number changes, etc. (that also depends on my paranoia, I know :).
The reason I'm asking that is because, to the best of my knowledge, there is no 'update' feature in asdf-install - as an lazy Ubuntu user, I'm too used to 'apt-get update'. My understanding is that updating asdf packages (eps. when some dependecies have also changed) is a complicated procedure - that's why it's better to perform it only for 'critical' things.
What is your perspective on that?
In my experience, upgrading is not a big deal. If your site works fine, there's not really a compelling reason to upgrade. (I still have some sites running tbnl-0.3, from early 2005). If you have problems, upgrading to the latest version is not generally a difficult process. The fear of upgrading can be a bigger obstacle than actually upgrading. Zach
On Mon, 9 Apr 2007 14:15:27 -0400, Zach Beane <xach@xach.com> wrote:
In my experience, upgrading is not a big deal. If your site works fine, there's not really a compelling reason to upgrade. (I still have some sites running tbnl-0.3, from early 2005). If you have problems, upgrading to the latest version is not generally a difficult process. The fear of upgrading can be a bigger obstacle than actually upgrading.
What Zach says. FWIW, I /try/ to adhere to the following policy: - Every functional change is mentioned in the ChangeLog file, "cosmetic" changes and otherwise irrelevant re-organizations sometimes aren't. - For Bugfixes and "small" changes, only the patch version number is released (for example from 0.8.3 to 0.8.4), for new functionality or bigger changes the minor version is bumped (for example from 0.7.3 to 0.8.0). The major version number will only be increased once I'm confident that the library is fairly stable - expect this to take more time. - I try to be backwards-compatible if possible. Incompatible changes will be explicitly announced. HTH, Edi.
Is it really complicated? My understanding was that you can just asdf-install again, and it will install the new version of Hunchentoot and update the symlink to the .asd file. Then, you can just delete the old version. I don't know anything about dependencies, though, or if it works the same way on setups other than SBCL on Gentoo. -austin -- Austin Haas Pet Tomato, Inc. http://pettomato.com On Mon Apr 09 13:05 , Victor Kryukov wrote:
Dear Edi:
What upgrade strategy do you recommend in following Hunchentoot updates? E.g. should I update every time your announce a fix, only when major version number changes, etc. (that also depends on my paranoia, I know :).
The reason I'm asking that is because, to the best of my knowledge, there is no 'update' feature in asdf-install - as an lazy Ubuntu user, I'm too used to 'apt-get update'. My understanding is that updating asdf packages (eps. when some dependecies have also changed) is a complicated procedure - that's why it's better to perform it only for 'critical' things.
What is your perspective on that?
Bets regards, Victor.
On 4/8/07, Edi Weitz <edi@agharta.de> wrote:
No technical changes. This release just fixes some version numbers I botched yesterday.
Sorry, Edi. _______________________________________________ tbnl-devel site list tbnl-devel@common-lisp.net http://common-lisp.net/mailman/listinfo/tbnl-devel
tbnl-devel site list tbnl-devel@common-lisp.net http://common-lisp.net/mailman/listinfo/tbnl-devel
Scribit Victor Kryukov dies 09/04/2007 hora 13:05:
The reason I'm asking that is because, to the best of my knowledge, there is no 'update' feature in asdf-install - as an lazy Ubuntu user, I'm too used to 'apt-get update'.
Hunchentoot has made its way into Debian recently, I suppose it should appear in the universe section also. Natively, Pierre -- nowhere.man@levallois.eu.org OpenPGP 0xD9D50D8A
"Victor Kryukov" <victor.kryukov@gmail.com> writes:
The reason I'm asking that is because, to the best of my knowledge, there is no 'update' feature in asdf-install - as an lazy Ubuntu user, I'm too used to 'apt-get update'.
I can relate to that, and that's one of the reasons why I wrote "ediware"[1]. I just "darcs pull" new patches in the hunchentoot tree and ASDF picks the changes up, recompiling the necessary bits. [1] http://common-lisp.net/~loliveira/ediware/ -- Luís Oliveira http://student.dei.uc.pt/~lmoliv/
participants (6)
-
Austin Haas -
Edi Weitz -
Luis Oliveira -
Pierre THIERRY -
Victor Kryukov -
Zach Beane