Re: Win32---what???
----- Original Message -----
From: "wolfgang fritz" <wolfritz at king.igs.net>
To: <EUPHORIA at LISTSERV.MUOHIO.EDU>
Sent: Sunday, August 20, 2000 12:43 AM
Subject: Win32---what???
> ...sigh, I can see it happening:
> My next little 'dinky' Win32Lib Tutorials description may go something
like
> this:
> ...works with David Cuny's win32lib version 0.45r.
> ...everything but ex99.exw works with Matt Lewis's unidentified 0.???
> version.
> ...crashes 'without reservation' in Joe Independent's version 0.69.
> ...tickles me pink with version 0.50 by Derek Parnell.
> ...re-formats your hard drive with version 0.HeHe by "The EVIL One".
>
> OpenSource *can* be such a 'bitch'...
> ( some of my friends wonder why? I deleted my Linux partition two years
ago?
> )
>
Yeah, I'm worried about this too. Its a bit like a market place environment,
you shop around and stick to the supplier that is the best for you. The
supplier that usually "wins" is the one that has the product that is
suitable, defect-free, and cost-effective. I'm trying very hard (its 3:20am
in Melbourne as I write this) to get the sourceforge version into that
state - but the initial workload is huge. Once we get it into shape for team
development, I will be strict about quality.
I've been asked about release strategies - here is my thinking on that...
Firstly, I don't have final say in this as it is a team collaboration.
However, I suspect that until it gets to v1.0, there will be many irregular
releases. Once it stablizes, and depending on the amount of change it
receives, a regular-ish schedule of three-monthly major upgrades (eg. v1.0
to v1.1) might be required. I suspect that major releases (v1.0 to v2.0)
would be done annually. There will probably be some organised, semi-official
beta program too. In between upgrades and major releases, I also suspect
that a monthly patch would be available (v1.0 to v1.0a) plus irregular
emergency fixes. The whole release schedule will be driven by the users
demands and the ability of the community to develop the product.
For now, I can foresee that a "stable" version will be available for
download at the current release level, from the project's web-site (still in
development). This is the one to which formal announcements of
patches/upgrades/releases are made. Also, the "bleeding edge" version will
be available for the adventurous. This will be the one that is
work-in-progress at sourceforge.net.
The current situation is that sourceforge.net has a bleeding edge version
and this is being made ready for its alpha release in about 1-2 weeks. An
alpha release (which I admit is an anomoly) is required this time because
the product has undergone a MASSIVE internal restructuring - while trying
hard not to break existing code using it. But, of course there will be some
errors made. After these artifact-bugs have been fixed, the beta version of
win32lib v.51 will be available for about 2 weeks. So the first next
official upgrade to v0.51 is expected around the end of September. I stress
most emphatically - if this does not suit you, please let me know now so I
can adjust my timetable.
Finally, these are *my* thoughts on the subject. I haven't discussed this
with the team yet. I'm sure we'll get on to this topic and make a decision
during the next 2 weeks. So it could all change. The team's release strategy
will be announced to the email list shortly.
----
cheers,
Derek Parnell
Melbourne, Australia
|
Not Categorized, Please Help
|
|
