On Mon, 17 Mar 2008, Lorenzo Fiorini wrote: > What are we waiting for? For someone who will make it ;-)
> I suggest: > 1) to tag "now" the svn as beta4 Rather RC1 to decrease the time of release process. > 2) create zip/tgz tarball with the svn at beta4 We already have script for creating tgz archive with whole SVN source code automatically which packs _ONLY_ files which are in SVN repository so there is no risk that some local files will be packed too. Probably we should add sth like that for ZIP too or simply convert .tgz archive to .zip format. I can add option to current bin/pack_src.sh to create also .zip files ASAP. > 3) upload the zip/tgz > 4) immediately reopen the trunk to the developers This will not be such easy. We will have to wait for user input about new release. If sth will be wrong then we will have to fix it and release RC2 and repeat the process. When we fix all problems then last RC should be marked as 1.0 I think that to weeks periods before releases should be enough though it will depend on Harbour users and how actively they will test new binaries. When we release version 1.0 then we will create 1.0 branch and unblock SVN for next modifications. > 5) the packagers will use the zip/tgz to create the binaries when > they'll have time and the binaries will be uploaded when and if > they'll be ready They can also download from SVN code snapshot tagged by us even so it's not strictly necessary though for some people who do not have SVN or do not know SVN options it may help. We should only agree which build time options we want to set. Because using different regex library is compile time option only (different regex implementation supported by us use different API so it's not possible to make it only link time option without additional harbour libraries) then I suggest to chose current default one inside our core code. In *nixes builds (and others which can use hb* scripts, f.e. MinGW, DJGPP) FM statistic is user link time option but in others not so I suggest to create such RC builds with FM enabled (without HB_FM_STATISTICS_OFF macro) for better tests. In current SVN HB_EXTENSION is disabled by default. We should agree if we want to enable it for RC binaries. If yes then I suggest to change the default setting in hbsetup.ch. The last one optional extenssion which I know is used by Harbour users and not enabled by default is HB_PP_MULTILINE_STRING defined in hbsetup.h so we should also decide if we want to enable it or not. Then we can start release process ASAP. If there are some other important optional build macros then please ask. I would like to hear your opinion about default settings ASAP. best regards, Przemek _______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
