Paul B. Gallagher wrote:
Philip Chee wrote:
On 18/07/2011 12:50, Philip Chee wrote:
On 18/07/2011 10:46, Rostyslaw Lewyckyj wrote:
All right, then where does the developer council/
governing body publish the details of the planned
changes to be introduced in the next release, so that
interested users can make their comments known
**early** aka **during pre-release**.
(and then how closely do they follow/stick to
these published plans?)
:) :) :) :) ......
For the 2.1 development process:
<https://wiki.mozilla.org/SeaMonkey:Features:2.1 >
<https://wiki.mozilla.org/SeaMonkey/Features/2.2 >
<https://wiki.mozilla.org/SeaMonkey/Features/2.3 >
And the fortnightly Tuesday meeting notes of course.
<https://wiki.mozilla.org/SeaMonkey/StatusMeetings >
This looks helpful, thanks.
However, after v. 2.1 we see only a couple of new features added,
nothing about modifications or deletions. Pretty sketchy stuff.
A visitor to the 2.1 link gets a great big long list of changes
already made,
Cast in frozen code.
But. Leaving aside bug fixes, which of the remaining items are items
forced by Mozilla: Gecko, FF, and TB changes.
And which are freely SM.
but looking forward to the v. 2.2 and 2.3 pages has very little to
respond to.
But supposedly, all the feature changes have already been decided,
and coded, and therefore could be described in detail.
After all from what some have written, they are already now coding
2.5, and 2.2 - 2.4 are in the testing stages!
If you're planning to move or take away our cheese, we still
don't know about it.
Succintly stated! :)
We, users, can not influence the product. All we can do is
offer our opinions after the fact and choose to stay or leave.
--
Rostyk
_______________________________________________
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey
