[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [paho-dev] Eclipse Paho 1.3 Release Plan

Hi Ian,

There aren't any service releases listed on [1] so I assumed none had
been made, that's all.

[1] https://projects.eclipse.org/projects/iot.paho

Cheers,

Roger



On Wed, Mar 1, 2017 at 5:30 PM, Ian Craggs
<icraggs@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
> Pierre, Roger,
>
> I've always made service releases for individual components whenever they
> were needed, not having a global Paho release for that.  Do you think we
> particularly need a Paho release as well?
>
> Ian
>
>
>
> On 02/27/2017 11:07 PM, Roger Light wrote:
>>
>> Hi Pierre,
>>
>> I don't think it is unreasonable to depend on Python 2.7.9 and 3.2.
>>
>> With regards a service release I think this is a good idea if there
>> are "enough" bugs that have fixes already made. I think having more
>> frequent service releases is something we should generally aspire to.
>>
>> Ian/James - is there any problem with making a Paho 1.2.1 service
>> release that at least includes the Python client, but that is open to
>> any of the other clients to join? I agree with Pierre that June is
>> quite a way off.
>>
>> Cheers,
>>
>> Roger
>>
>>
>>
>> On Mon, Feb 27, 2017 at 10:26 AM, Pierre Fersing
>> <pierre.fersing@xxxxxxxxxxx> wrote:
>>>
>>> Hello all,
>>>
>>> On the Python side, the develop branch that hold new features does
>>> include
>>> one breaking change: it requires newer version of Python.
>>>
>>> I think the feature added (SNI support) needs to be released and worth a
>>> break change as it is waited by users.
>>>
>>> For the details, it will require Python 2.7.9+ or 3.2+ for the TLS/SSL
>>> support (instead of 2.7+/3.0+). Code without TLS are not affected.
>>>
>>>
>>> Also on the subject of release, the last Python client release is 8
>>> months
>>> old and there are few bug fixes that I would like to release before June.
>>> For this, we would need to do a service release 1.2.1 that would happen
>>> before June.
>>>
>>> Does those ideas look good to you ?
>>>
>>> Regards,
>>>
>>> PierreF
>>>
>>>
>>>
>>> Le 19/01/2017 Ã 16:56, Ian Craggs a Ãcrit :
>>>
>>> Hello all,
>>>
>>> you might have seen that we have outlined the next release of Eclipse
>>> Paho,
>>> 1.3, and aligned it with the next simultaneous release of Eclipse,
>>> Oxygen:
>>>
>>>      https://projects.eclipse.org/projects/technology.paho
>>>
>>> We have had a sequence of Paho releases that have been associated with
>>> Eclipse simultaneous releases, so it seems like a good opportunity to do
>>> this again.   We could have had 1.1.0 associated with Mars but I didn't
>>> realize that they didn't have to be exactly simultaneous at the time.  So
>>> we
>>> can release 1.3 before the Oxygen date in June if we choose to.  As
>>> always,
>>> there is a month lead up time where the project plan and legal reviews
>>> take
>>> place, so the work should be substantially completed in May.
>>>
>>> Breaking Changes - Version 2?
>>>
>>> Roger asked some time ago whether we could consider a version 2.0
>>> release,
>>> as he had some breaking changes he was considering for the Python client.
>>> James is reviewing a pull request this week for the Java client which
>>> could
>>> also result in breaking changes, and it would be good to allow this to
>>> happen for individual Paho applications.  As no-one really takes any
>>> notice
>>> of the Paho release number, then it seems to me that the Paho
>>> applications
>>> should be able to decide for themselves what their version numbers ought
>>> to
>>> be.  So the Python and Java clients could move to 2.0 within the Paho 1.3
>>> release for instance, or release both 2.0 and 1.3 branches.
>>>
>>> I'll check with Benjamin to see what he thinks our options are.
>>>
>>> Proposed Release Contents
>>>
>>> - first formal release of mqtt-spy in Paho (Kamil, I need to speak to
>>> you!)
>>> - first formal release of Tomoaki's MQTT-SN gateway
>>> - it would be great to get a release of the C++ client (Frank?)
>>> - updates/fixes to other clients/applications:
>>>      - C client (I have a raft of outstanding work to look at)
>>>      - embedded clients for both MQTT and MQTT-SN
>>>      - Java/Android
>>>      - Python? Go? M2MQTT?
>>>
>>> For all committers, please let us know what you would like to include, or
>>> any other suggestions you might have.  James or I will contact you
>>> individually to make sure we know your plans, if you don't get in contact
>>> with us first :-)
>>>
>>> Thanks!
>>>
>>>
>>> --
>>>
>>> Ian Craggs
>>>
>>> icraggs@xxxxxxxxxx                 IBM United Kingdom
>>>
>>> Eclipse Paho Project Lead; Committer on Eclipse Mosquitto;
>>>
>>> Tech Lead in IBM Watson IoT Platform
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>>
>>> paho-dev mailing list
>>>
>>> paho-dev@xxxxxxxxxxx
>>>
>>> To change your delivery options, retrieve your password, or unsubscribe
>>> from
>>> this list, visit
>>>
>>> https://dev.eclipse.org/mailman/listinfo/paho-dev
>>>
>>>
>>>
>>> _______________________________________________
>>> paho-dev mailing list
>>> paho-dev@xxxxxxxxxxx
>>> To change your delivery options, retrieve your password, or unsubscribe
>>> from
>>> this list, visit
>>> https://dev.eclipse.org/mailman/listinfo/paho-dev
>>
>> _______________________________________________
>> paho-dev mailing list
>> paho-dev@xxxxxxxxxxx
>> To change your delivery options, retrieve your password, or unsubscribe
>> from this list, visit
>> https://dev.eclipse.org/mailman/listinfo/paho-dev
>
>
> --
> Ian Craggs
> icraggs@xxxxxxxxxx                 IBM United Kingdom
> Eclipse Paho Project Lead; Committer on Eclipse Mosquitto;
> Tech Lead in IBM Watson IoT Platform
>
> _______________________________________________
> paho-dev mailing list
> paho-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from
> this list, visit
> https://dev.eclipse.org/mailman/listinfo/paho-dev