Comments on: FireStats 1.2.4-stable http://blog.firestats.cc/33 FireStats - the blog Mon, 18 Oct 2010 05:23:48 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: omry http://blog.firestats.cc/33/comment-page-1#comment-4989 omry Sat, 30 Jun 2007 14:29:24 +0000 http://blog.firestats.cc/33#comment-4989 Hi Allan Currently this usage of the repository is not supported. the current release flow is: * each major version change (1.x -> 1.y) gets a branch for bug fixes. * when a new version is released, an ant build file is executed, which do some manipulation (version numbers and more), and produce the target archive which contains only what’s appropriate for users. * I didn’t tag the recent versions (although I should have), but this tag would not have been on build output, but rather on the code in the branch the build was ran on. I will consider creating a release section that will contain what you asked in future versions. (IE, http://svn.firestats.cc/releases/1.2.5-stable) about development files in the repo: the repository is a tool that supposed to help in the development, that’s why I think eclipse files are perfectly reasonable to be there. Hi Allan
Currently this usage of the repository is not supported.
the current release flow is:
* each major version change (1.x -> 1.y) gets a branch for bug fixes.
* when a new version is released, an ant build file is executed, which do some manipulation (version numbers and more), and produce the target archive which contains only what’s appropriate for users.
* I didn’t tag the recent versions (although I should have), but this tag would not have been on build output, but rather on the code in the branch the build was ran on.
I will consider creating a release section that will contain what you asked in future versions.
(IE, http://svn.firestats.cc/releases/1.2.5-stable)
about development files in the repo:
the repository is a tool that supposed to help in the development, that’s why I think eclipse files are perfectly reasonable to be there.

]]> By: Allan Odgaard http://blog.firestats.cc/33/comment-page-1#comment-4983 Allan Odgaard Sat, 30 Jun 2007 10:10:12 +0000 http://blog.firestats.cc/33#comment-4983 I want to checkout the svn repository directly to wp-content/plugins so that I can easier up/downgrade and inspect changes. Looking at the repository (at http://svn.firestats.cc/trunk/firestats/) I am not 100% sure that this is really supported ATM though. E.g. there are no tags corresponding to release versions and some of the files refer to SVN-VERSION, which I assume gets substituted for the actual version when you make a release “build”. The repository also has a few files, like the Eclipse stuff, which probably should not go into the public repository. So here’s a request for making the public repository useable for this purpose. So presumably when you make a stable build, you’d svn mkdir tags/1.2.4-stable (or similar) and svn cp the files included in that build to this tag, then perform the SVN-VERSION substitution. That way rather than download, unzip, and move the files to wp-content/plugins I’d do: svn co http://svn.firestats.cc/tags/1.2.4-stable/firestats And when you release 1.2.5-stable, I can update as simple as: svn switch http://svn.firestats.cc/tags/1.2.5-stable/firestats This will even preserve local changes, and also makes it easy for me to ask for a diff between 1.2.4 and 1.2.5 and possibly downgrade if 1.2.5 gives me a problem. I want to checkout the svn repository directly to wp-content/plugins so that I can easier up/downgrade and inspect changes.

Looking at the repository (at http://svn.firestats.cc/trunk/firestats/) I am not 100% sure that this is really supported ATM though.

E.g. there are no tags corresponding to release versions and some of the files refer to SVN-VERSION, which I assume gets substituted for the actual version when you make a release “build”.

The repository also has a few files, like the Eclipse stuff, which probably should not go into the public repository.

So here’s a request for making the public repository useable for this purpose.

So presumably when you make a stable build, you’d svn mkdir tags/1.2.4-stable (or similar) and svn cp the files included in that build to this tag, then perform the SVN-VERSION substitution.

That way rather than download, unzip, and move the files to wp-content/plugins I’d do:

svn co http://svn.firestats.cc/tags/1.2.4-stable/firestats

And when you release 1.2.5-stable, I can update as simple as:

svn switch http://svn.firestats.cc/tags/1.2.5-stable/firestats

This will even preserve local changes, and also makes it easy for me to ask for a diff between 1.2.4 and 1.2.5 and possibly downgrade if 1.2.5 gives me a problem.

]]> By: Oleg http://blog.firestats.cc/33/comment-page-1#comment-3227 Oleg Sun, 20 May 2007 06:43:37 +0000 http://blog.firestats.cc/33#comment-3227 Already, FireStats in Russian? Already, FireStats in Russian?

]]>