I discussed this with Karl. The latest plugin release was 3.3, so in order to 
go straight to bnd 3.5 we would have to do one of the following:

* Release version 3.4 of the plugin pointing at version 3.5 of bnd; or
* Skip version 3.4 of the plugin entirely.

We felt that either option would be confusing for users. So we are releasing 
3.4 with bnd 3.4 and will then very shortly release 3.5.

Regards,
Neil

> On 14 Dec 2017, at 19:49, Raymond Auge <[email protected]> wrote:
> 
> Is there any reason this shouldn't be released with bnd 3.5.0 which is the
> latest release?
> 
> BND 3.5.0 solves several pretty critical issues over 3.4.0.
> 
> I would recommend skipping bnd 3.4.0
> 
> Sincerely,
> - Ray
> 
> On Thu, Dec 14, 2017 at 1:23 PM, Stefan Seifert <[email protected]>
> wrote:
> 
>> +1 (non-binding)
>> 
>> 
> 
> 
> -- 
> *Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile>
> (@rotty3000)
> Senior Software Architect *Liferay, Inc.* <http://www.liferay.com>
> (@Liferay)
> Board Member & EEG Co-Chair, OSGi Alliance <http://osgi.org> (@OSGiAlliance)

Reply via email to