Hi JB,
Just to be clear, not cause any misleading to SMX3.x users.
I might be wrong, but I don't think we(anyone have committership) will
maintain or release SMX 3.x after 3.x EOL from Apache side for a
certain company, that's why we discuss here and will announce the 3.x
EOL.
If some company need it after 3.x EOL, they need fork the branch,
maintain and release themselves, but it's not from Apache Servicemix.
Freeman
On 2012-6-7, at 上午12:14, Jean-Baptiste Onofré wrote:
Organization no, but people (with the SMX committership) yes.
I will continue to maintain (as minimal) SMX3 and JBI Component, as
it's still in production (in friend companies, etc).
Regards
JB
On 06/06/2012 09:53 AM, diwakar wrote:
Hi,
Thanks for the replies.
>> But they should plan to migrate to 4.x.
Migrating to 4.x JBI is not trivial and JBI may not be
supported in 5.x. So we are planning to get rid of JBI (which takes
time).
We have to survive till then.
>> However, it doesn't mean that we are going to
remove the
svn repo, it means that we won't work on this branch anymore
>> Or have in-house team/knowledge to support/
maintain it
So, some one from our organization can become active in
Servicemix 3.x community and still do releases of 3.x.x (only for our
organization?) by committing changes to the apache svn even after
end of
2012. Please let me know if this understanding is correct.
With Best Regards,
Diwakar
--
View this message in context:
http://servicemix.396122.n5.nabble.com/DISCUSS-ServiceMix-3-x-EOL-tp5713318p5713559.html
Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
---------------------------------------------
Freeman Fang
FuseSource
Email:[email protected]
Web: fusesource.com
Twitter: freemanfang
Blog: http://freemanfang.blogspot.com
http://blog.sina.com.cn/u/1473905042
weibo: http://weibo.com/u/1473905042
