Re: [Bashburn-info] 3.0 Beta 1
Brought to you by:
bashburn
From: Markus K. <mar...@on...> - 2008-10-07 13:12:11
|
Anders Lindén wrote: > On Tuesday 07 October 2008 02:10:43 you wrote: > >> Anders Lindén schrieb: >> >>> So guys, I'm thinking I'll release 3.0 beta1 tonight or tomorrow. If >>> anyone feels that's a bad idea let me know, otherwise I'll do it. I'll >>> include the English, Swedish and German translation because as >>> > far as I > >>> know those are the ones updated. >>> We've tested this thing pretty good so I feel good releasing a >>> > beta to > >>> hunt down any hard to find bugs that might still be there. >>> >> Ok, Anders. Big marking as beta I think would be ok. So we could >> > get > >> more people for testing - and since there is a "rule" to release often >> in open source development, this may also a point. >> >> Ahh - Anders you can look to the Swedish translation. I have added >> > the > >> variable >> >> bb_main_menu=MAIN >> >> in file "BashBurn.lang" for main-menue header text printing. >> > Translate it > >> to swedish if necessary. >> >> >> >> By the way - did you removed the link to the svn web-interface on >> > the > >> bashburn website? I cna't find it anymore. I think it would be nice to >> > have > >> it there, or don' t think so? >> >> Markus >> > > Alright Markus, I'll add and translate that. > No I haven't removed that link from the web page. It's located under > downloads -> webSVN > > Anders, we have a small problem with Beta 1! I have done yesterday some changes in the trunk (also the mentioned swedish language updating). Now I saw you have not moved all files for the release 3.0 from 'trunk' to 'release' shortly before you created the release-package. I should had tell you this - so you thought that there was no major changes in the trunk since you created the release branch. In my humble opinion I think it would be good if we use following process to make a release and to avoid such things in future: 1. Like you did - tell others per mailing list shortly before release whether it is ok to create a release for the main developers, and tell the short time period in which the creation is planned. 2. Then lock the trunk branch (via "svn lock") and move ALL files from trunk to release. 3. Create package from release tree. 4. Unlock trunk branch. Is this a way? However, Anders now we can maybe in near future release beta 2. Hehe - before we got installed beta 1, it is already outdated. If we would be a company we could make much money and users would be impressed about the dynamic of improvements. ;-) Markus |