RE: FW: [Koha-devel] buildrelease for 1.3.0 => steve ?
Steve wrote:
On Fri, 20 Sep 2002, Eyler, Patrick wrote:
Paul asked:
Then, should I tag the version ? I think yes. Please confirm.
Yes, tag the release if you are going to release it publicly. This will allow us to see what has changed in CVS since it was released for bug confirmation, etc. We can also delete old tags after a certain time so they don't clutter up the CVS too much. For example, I deleted all of the release candidates for the 1.2.2 release after 1.2.2 went out.
where should I put my tar.gz when builded ? we planned not to release officialy it on sf, so where should I put it after testing install ?
Do we want to put it on sourceforge? I think that might be a good idea. We can also make release announcements on Freshmeat. I think that active, visible development of the 1.4 tree will draw even more developers into the fold.
I'd recommend putting it up on sourceforge. Put it under the koha-unstable package, I guess. Or do we want a new package for 1.3.x releases to separate them from the release candidates for the stable branch? Only the most recent file in a package will show up on the main sf.net/projects/koha/ page.
Let's build a 1.4-unstable package to put it in. I think the 1.2 series will likely continue to get some love until (at least) next summer (people will take a while to upgrade), and I'd like us to be able to support both trees in the interim.
Steve.
-pate
On Fri, 20 Sep 2002, Eyler, Patrick wrote:
Let's build a 1.4-unstable package to put it in. I think the 1.2 series will likely continue to get some love until (at least) next summer (people will take a while to upgrade), and I'd like us to be able to support both trees in the interim.
1.4-unstable should maybe be used for 1.4 release candidates? We should have a koha_1.3 package for the 1.3.x releases. Steve.
participants (2)
-
Eyler, Patrick -
Tonnesen Steve