Read and respond to this message at:
https://sourceforge.net/forum/message.php?msg_id=7238653
By: pboy
Hi all,
we are reaching a kind of "point of no return" in the deveolment process of
a standards compliant version of APLAWS.
It is becoming rather difficult and cumbersome to keep backwards compatibility
to the current ccm script based installation and proprietary runtime system.
So we have to decide. There are 3 options, I suppose:
1. We create a release 1.0.5 branch now, where we keep backwards compatibility
on
the current devel status. We bump the versioin number of trunk, presumably
to
6.8 (following a Red Hat numbering schema) to indicate a remarkable change
(and
an upcomming switch to 7 = APLAWS 2).
2. We create a trunk-ng branch and try to devel both in parallel
3. We silently discard backwards compatibility and just proceed.
I suppose:
3. would be the worst alternative.
2. may currently exceed the development resources of the community.
1. seems the best way. If there will ever be a real 1.0.5 release depends on
the demand and efforts of the community. We at Bremen will skip such a version
and concentrate on a fully standards compatible release, may be 1.1. Nevertheless
we could contribute: release notes, updated installation manual, and - of course
- bug fixing. We can not contribute to testing. Maybe we can contribute rpm
creation.
Please comment! We have to make a (community based) decision.
Peter
______________________________________________________________________
You are receiving this email because you elected to monitor this forum.
To stop monitoring this forum, login to SourceForge.net and visit:
https://sourceforge.net/forum/unmonitor.php?forum_id=368401
|