[JDEV] Transport Authors Please Read -- Jabber 1.3+, etc...

[Lazarus Long]

On Wed, Nov 22, 2000 at 10:12:21PM -0500, David Waite wrote:
  
 > Are you planning to port/maintain MIO back on  the 1.2.x series,
 > or maintain separate branches for MIO and non-MIO transports (for bug
 > fixes) ? I'm very nervous that many people have barely been able to get
 > the server working (much fewer the transports), and you are now moving
 > on to a new incompatible series.

Exactly!

I fear however, the answer may again be a resounding "No, we don't care
about you."  Those choosing to run the stable server got royally screwed
with the release of the 1.2 server.  As soon as 1.2 was released, the
support just-plain-stopped *for* server 1.2 apparently, and moved on to
(unstable) 1.3 (as ludicrous as that seems.)

Back on November 14th, I said:
 
 > How about those us us who run stable, not cvs versions of things?
 > When will there be a version which will work with the (just-released)
 > stable server 1.2?  (We waited long enough for 1.2 to be released,
 > this wait for a compatible irctrans is an additional aggravation.
 > Please don't tell us we need to wait for server 1.4.)

And he replied:

 > and to me, Server developemnt comes first, above all else..You all may
 > feel differently, but that's my take... =]

I guess there's "no time" to care about those of us attempting to run
stable server 1.2.  The Jabber project is apparently only targeted
toward those who are among the "eleet" 1.3 development team, at least
that is the impression conveyed.  (I'll believe otherwise when I see an
irctrans that works with stable server 1.2.)

I would hope that this attitude of nose-thumbing toward those running
1.2 would have changed by now.  Unfortunately, we see otherwise, even in
the very subject line of this thread.  Transport authors (who certainly
have not effectively completed the task of getting their transports to
work well with 1.2) are being advised to focus their attention upon the
incompatible 1.3 server!  Where is the sense in that?

The overall message seems clear, the users (and server operators) don't
matter, only the devel team.

Does anyone care to conjecture whether 1.4 will end up effectively
orphaned in favor of 1.5, as quickly as 1.2 was considered obsoleted?

"1.2 -- the release orphaned before it learned to crawl"  (Great slogan!)

It certainly leaves a bitter taste in my mouth.

-- 
Please (OpenPGP) encrypt all mail whenever possible. Request the following
Public Keys for Lazarus Long <lazarus at overdue.ompages.com>

  Type    Bits/KeyID    Fingerprint                   DSA KeyID: vvvv vvvv
ElGamal: 2048g/41783186 47A0 0929 CD9F B53E 49C0  F06C 560E F574 ED0D F80C
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 244 bytes
Desc: not available
URL: <https://www.jabber.org/jdev/attachments/20001123/69de8b72/attachment-0002.pgp>