Every minute this evening, everyone could track what I was doing and
how efficient I was at it :-) Some patches were clearly no-brainers.
The point is that what is now on master is ready for your testing
before I stamp it as 2.6.0. There might be patches on the ML I didn't
process yet, the habitués know that I take priority on bug reports...
I merged the type info redux patches on master and the circular buffer
connection policy as well.
It's not like I'm going to release tomorrow, but now might be a good
time to see if your patch made it... and reply to this thread if it
didn't but should.
Did not make it:
- fixing the updateHook + events behavior.
- flexiport implementation
I won't let the release slip any further because of these. The
upcoming type system fixup is really worth it for everyone working on
2.5 right now.
Peter
Amazing !
On 09/28/2012 12:17 AM, Peter Soetens wrote:
> Every minute this evening, everyone could track what I was doing and
> how efficient I was at it :-) Some patches were clearly no-brainers.
>
> The point is that what is now on master is ready for your testing
> before I stamp it as 2.6.0. There might be patches on the ML I didn't
> process yet, the habitués know that I take priority on bug reports...
>
> I merged the type info redux patches on master and the circular buffer
> connection policy as well.
>
> It's not like I'm going to release tomorrow, but now might be a good
> time to see if your patch made it... and reply to this thread if it
> didn't but should.
>
> Did not make it:
> - fixing the updateHook + events behavior.
> - flexiport implementation
>
> I won't let the release slip any further because of these. The
> upcoming type system fixup is really worth it for everyone working on
> 2.5 right now.
Just so that I am sure that you see it:
https://gitorious.org/orocos-toolchain/rtt/merge_requests/15
Sylvain
Amazing !
2012/9/28 <paul [dot] chavent [..] ...>
> There are some patches that would need more testing.
>
> How do you think about making a kind of 2.5.9 that would be declared as a
> 2.6.0 for testing purpose (that would include features that won't be in the
> release).
>
> This could allow to make live tests easier.
>
> When the testing is done, we remove unwanted parts, and we tag the final
> release.
>
It is the purpose of the master branch, isn't it?
>
>
> --
> Orocos-Dev mailing list
> Orocos-Dev [..] ...
> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-dev
>
Amazing !
On Fri, Sep 28, 2012 at 6:50 PM, Charles Lesire-Cabaniols
<charles [dot] lesire [..] ...> wrote:
>
>
> 2012/9/28 <paul [dot] chavent [..] ...>
>
>> There are some patches that would need more testing.
>>
>> How do you think about making a kind of 2.5.9 that would be declared as a
>> 2.6.0 for testing purpose (that would include features that won't be in
>> the
>> release).
>>
>> This could allow to make live tests easier.
>>
>> When the testing is done, we remove unwanted parts, and we tag the final
>> release.
>
>
> It is the purpose of the master branch, isn't it?
Yes it is. We're testing master in the run-up for the release and then
release it as 2.6.0.
So for autoproj, it's just selecting the master branch for all packages.
Peter
Amazing !
Do you merge test code in master ?
There are some patches that you hesitate to merge on master that could be integrated on an "experimental branch".
It could allow us to test a branch without having to manage all new patches from the bugtracker...
Le 09/28/2012 09:32 PM, Peter Soetens a écrit :
> On Fri, Sep 28, 2012 at 6:50 PM, Charles Lesire-Cabaniols
> <charles [dot] lesire [..] ...> wrote:
>>
>>
>> 2012/9/28 <paul [dot] chavent [..] ...>
>>
>>> There are some patches that would need more testing.
>>>
>>> How do you think about making a kind of 2.5.9 that would be declared as a
>>> 2.6.0 for testing purpose (that would include features that won't be in
>>> the
>>> release).
>>>
>>> This could allow to make live tests easier.
>>>
>>> When the testing is done, we remove unwanted parts, and we tag the final
>>> release.
>>
>>
>> It is the purpose of the master branch, isn't it?
>
> Yes it is. We're testing master in the run-up for the release and then
> release it as 2.6.0.
>
> So for autoproj, it's just selecting the master branch for all packages.
>
> Peter
>
Amazing !
There are some patches that would need more testing.
How do you think about making a kind of 2.5.9 that would be declared as a 2.6.0 for testing purpose (that would include features that won't be in the release).
This could allow to make live tests easier.
When the testing is done, we remove unwanted parts, and we tag the final release.
Amazing !
On 09/28/2012 12:17 AM, Peter Soetens wrote:
> Every minute this evening, everyone could track what I was doing and
> how efficient I was at it :-) Some patches were clearly no-brainers.
>
> The point is that what is now on master is ready for your testing
> before I stamp it as 2.6.0. There might be patches on the ML I didn't
> process yet, the habitués know that I take priority on bug reports...
>
> I merged the type info redux patches on master and the circular buffer
> connection policy as well.
>
> It's not like I'm going to release tomorrow, but now might be a good
> time to see if your patch made it... and reply to this thread if it
> didn't but should.
I want to get the orocos toolchain synced with rock on the orogen stuff.
Amazing !
On Fri, Sep 28, 2012 at 12:17:12AM +0200, Peter Soetens wrote:
> Every minute this evening, everyone could track what I was doing and
> how efficient I was at it :-) Some patches were clearly no-brainers.
Yeah, what a frenzy!
> The point is that what is now on master is ready for your testing
> before I stamp it as 2.6.0. There might be patches on the ML I didn't
> process yet, the habitués know that I take priority on bug reports...
>
> I merged the type info redux patches on master and the circular buffer
> connection policy as well.
> It's not like I'm going to release tomorrow, but now might be a good
> time to see if your patch made it... and reply to this thread if it
> didn't but should.
I sent you a merge request yesterday afternoon via gitorious for
miscellaneous small Lua improvements. Please apply!
Thanks!
Markus