Hi Lorenzo,
Consequently, I think we should to the release
rather quickly, since the feature set is stable by
now, and no major bugs are known. Fixing the rest
can always be done in the 1.0 RC branch.
I agree, but if we think that MT will come soon we should release a
beta4 not an RC.
An RC cycle will take time and for me RC means only bug fix.
The RC fixing cycle can go (should go in fact) in parallel
with next version development. There is no point, or technical
reason for idling to wait until 1.0 Final.
It's not about features but about resources:
we'll have to wait for the final release of the 1.0 to add MT or start
a branch for 1.1 but the past has shown that keeping in sync two
branches is not so easy and not so useful since if programmers know
that there is sth more to come and they'll skip 1.0 for 1.1.
Ideally, if we have a stable state (which we believe
we have now), there is no need to do large scale fixing
in 1.0 branch. The critical fixes can be applied using few
resources, moreover this task can be done by _other ppl_
doing the actual fixes on the main branch. It's a matter
of selection and merge.
The "world" will compare Harbour 1.0 with other solutions and we know
how important is the "first look".
First look should rather be stable than full of potentially
rushed-in features IMO; it's a development platform after all :)
And MT doesn't look like a one week feature, next version is
not just about MT even.
We are not a company but I think we all want Harbour be as successful
as possible.
More users means more developers and longer life and more users and
more programmers and...
That's exactly why we should release.
I'm heading for today's repository tag done by Phil.
This is not a blocking one, but something which will
allow start implementing next version stuff while
still fixing bugs in 1.0 branch for an RCn -> 1.0 Final.
Brgds,
Viktor
_______________________________________________
Harbour mailing list
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour
