« Return to Thread: Should we officially kill the 0.22 ?
Re: Should we officially kill the 0.22 ?
by Michael Bell
::
Rate this Message:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Daniel Gollub wrote:
> On Wednesday 25 March 2009 02:30:20 pm Michael Bell wrote:
>>
>> Daniel Gollub wrote:
>>> I don't agree here - there are many lucky people which managed to get
>>> 0.22 working. Updating to some 0.3x might break things again.
>>>
>>> They should downgrade to 0.22 for the time being. Upgrading to 0.40 will
>>> be also kind of supported by configuration update helpers (e.g.
>>> OSyncUpdater). I don't plan to support 0.36 update to 0.4x or so.
>> Actually I think that 0.22 is in EOS state (End-Of-Support). This is
>> what Juha and Bricks mean. I agree on this. EOS does not mean EOL. If
>> there is a distro which want to fix it then they can do it in our or in
>> their VCS. The simple question today is, if you want to focus on 0.40
>> development who supports 0.22? We need real commitments here.
>
> Right - who supports OpenSync 0.22? Who develops OpenSync trunk?
I develop only on trunk (libwbxml and libsyncml). The SyncML plugin is
maintained too by me. I "just" need a stable API to develop and test.
> Ok - then i revoke this "decision" thing - at least in my personal opinion
> things worked out quite well the last year - expect that 0.40 is not released
> yet.
The problem is that the last point is the only thing which is visible
from the outside. If somebody is working on the trunk then this trunk is
too often broken. So how should somebody start working on OpenSync if it
breaks so often. Learning is a process which has to do with continuity.
People can only learn to code OpenSync if there is some kind of
continuity and this is the problem today. I don't think that there will
be new upstream developers until 0.40 is released and there is a
reliable code base or API.
I also stopped working on the SyncML plugin for a while because the API
changed too fast. I wait for a signal that it makes sense to adapt to
the actual API.
> Right - all wait for a stable release/API - but how many really actively
> contribute to OpenSync API development?
Please see above. I really think that there will be no new contributors
until 0.40.
> Quite frankly, in my opinion only those how really heavily contribute to
> OpenSync with time to this project should "judge"/decided what we want to see
> as "supported" and what not.
>
> What benefit do you see if we announce in the wild that we don't support 0.22
> and we don't support 0.3x? I guess this will just motivate people fork
> OpenSync or start a new project ...
The most people need a statement that 0.22 works as it is or not. So
sometimes there are workarounds but there will be no code fixes. This
will reduce noise.
> And letting distros package up 0.3x isn't a good idea either.
0.3x should never be packaged. I think we all agree here.
> I agree that their is not much support at all in 0.22 - and my priority is on
> 0.40. But i prefer to keep current setups with "old" mobiles working instead
> of breaking those setups in favor of "hardware enablement".
Nobody wants that those people upgrade. EOS or EOSL has nothing to do
with EOL. There is a clear difference. If it works then there is no
reason why they should upgrade.
Best regards
Michael
- --
___________________________________________________________________
Michael Bell Humboldt-Universitaet zu Berlin
Tel.: +49 (0)30-2093 2482 ZE Computer- und Medienservice
Fax: +49 (0)30-2093 2704 Unter den Linden 6
michael.bell@... D-10099 Berlin
___________________________________________________________________
PGP Fingerprint: 09E4 3D29 4156 2774 0F2C C643 D8BD 1918 2030 5AAB
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFJykU42L0ZGCAwWqsRAvH6AJ9joJnGlYaJ2ap2soRlWN5TwPsCxgCgx7EV
+JX3tV7ngVQmlcLPQFPexPs=
=djw4
-----END PGP SIGNATURE-----
------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
_______________________________________________
Opensync-devel mailing list
Opensync-devel@...
https://lists.sourceforge.net/lists/listinfo/opensync-devel
Hash: SHA1
Daniel Gollub wrote:
> On Wednesday 25 March 2009 02:30:20 pm Michael Bell wrote:
>>
>> Daniel Gollub wrote:
>>> I don't agree here - there are many lucky people which managed to get
>>> 0.22 working. Updating to some 0.3x might break things again.
>>>
>>> They should downgrade to 0.22 for the time being. Upgrading to 0.40 will
>>> be also kind of supported by configuration update helpers (e.g.
>>> OSyncUpdater). I don't plan to support 0.36 update to 0.4x or so.
>> Actually I think that 0.22 is in EOS state (End-Of-Support). This is
>> what Juha and Bricks mean. I agree on this. EOS does not mean EOL. If
>> there is a distro which want to fix it then they can do it in our or in
>> their VCS. The simple question today is, if you want to focus on 0.40
>> development who supports 0.22? We need real commitments here.
>
> Right - who supports OpenSync 0.22? Who develops OpenSync trunk?
I develop only on trunk (libwbxml and libsyncml). The SyncML plugin is
maintained too by me. I "just" need a stable API to develop and test.
> Ok - then i revoke this "decision" thing - at least in my personal opinion
> things worked out quite well the last year - expect that 0.40 is not released
> yet.
The problem is that the last point is the only thing which is visible
from the outside. If somebody is working on the trunk then this trunk is
too often broken. So how should somebody start working on OpenSync if it
breaks so often. Learning is a process which has to do with continuity.
People can only learn to code OpenSync if there is some kind of
continuity and this is the problem today. I don't think that there will
be new upstream developers until 0.40 is released and there is a
reliable code base or API.
I also stopped working on the SyncML plugin for a while because the API
changed too fast. I wait for a signal that it makes sense to adapt to
the actual API.
> Right - all wait for a stable release/API - but how many really actively
> contribute to OpenSync API development?
Please see above. I really think that there will be no new contributors
until 0.40.
> Quite frankly, in my opinion only those how really heavily contribute to
> OpenSync with time to this project should "judge"/decided what we want to see
> as "supported" and what not.
>
> What benefit do you see if we announce in the wild that we don't support 0.22
> and we don't support 0.3x? I guess this will just motivate people fork
> OpenSync or start a new project ...
The most people need a statement that 0.22 works as it is or not. So
sometimes there are workarounds but there will be no code fixes. This
will reduce noise.
> And letting distros package up 0.3x isn't a good idea either.
0.3x should never be packaged. I think we all agree here.
> I agree that their is not much support at all in 0.22 - and my priority is on
> 0.40. But i prefer to keep current setups with "old" mobiles working instead
> of breaking those setups in favor of "hardware enablement".
Nobody wants that those people upgrade. EOS or EOSL has nothing to do
with EOL. There is a clear difference. If it works then there is no
reason why they should upgrade.
Best regards
Michael
- --
___________________________________________________________________
Michael Bell Humboldt-Universitaet zu Berlin
Tel.: +49 (0)30-2093 2482 ZE Computer- und Medienservice
Fax: +49 (0)30-2093 2704 Unter den Linden 6
michael.bell@... D-10099 Berlin
___________________________________________________________________
PGP Fingerprint: 09E4 3D29 4156 2774 0F2C C643 D8BD 1918 2030 5AAB
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFJykU42L0ZGCAwWqsRAvH6AJ9joJnGlYaJ2ap2soRlWN5TwPsCxgCgx7EV
+JX3tV7ngVQmlcLPQFPexPs=
=djw4
-----END PGP SIGNATURE-----
------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
_______________________________________________
Opensync-devel mailing list
Opensync-devel@...
https://lists.sourceforge.net/lists/listinfo/opensync-devel
« Return to Thread: Should we officially kill the 0.22 ?
| Free embeddable forum powered by Nabble | Forum Help |
