Wouldn't this be better served by creating a script that fetches a
stable version of each product and prividing a place where they can
be
downloaded from?
It keeps you from having to customize yet allows you to have a fixed
point to work around.
Then, you can update portions of it as needed.
This is always better served when there are stable versions being
distributed, which is currently the 1.x version of Harbour.
And when 2.x is released, you once again have a stable version to
work
with.
With that in mind, would a better solution be to move quickly as
possible to a stable 2.0 Harbour release? This would be good for all
parties involved. Grabbing an unstable version of Harbour to make
some
other process stable is very work intensive and counterproductive
in the
long run.
Hi,
Is time to Harbour 2.0 stable release?
There's a whatsnew doc to be completed, and I won't
be able to complete it anytime soon. (already spent
quite some time to process part of it, but the
change list is quite huge)
We'd also need to start making platform tests.
Since the set of supported platforms is much wider
now than with 1.x, we should make some priorities.
We should decide whether we want to wait for HBQT to
finalize. Probably not.
Next, someone will need to make the final release
binaries. For me, only the windows release takes
two complete days (not working days, two complete
days), seeing the zero amount of supporters with
beta3 and relatively low amount of downloads, I
don't feel extremely inclined to dedicate that much
resources to it yet another time.
IOW, we need volunteers to help on some of these
jobs, the code itself is ready for an RC, or even
a final.
Finally: Does anyone have anything else pending?
[ Some more from my pending list:
- ChangeLog rename to CHANGES
- postinst further cleanup (can be done after the release though)
- type cleanup (definitely after a release)
- dir layout standardization as proposed by Przemek.
(probably after a release, since the job looks big with
lot of testing involved)
- hbmk2 autodetection reform (probably after release) ]
Brgds,
Viktor
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
