Hi,
looks fine to me!
Let's try to get the number of open bugs down during 2.17.0 and 2.17.1.
Cheers,
Uli

-----Ursprungliche Nachricht-----
Von: Anton Pak [mailto:[email protected]]
Gesendet: Mittwoch, 2. Februar 2011 15:10
An: OpenHPI-devel
Betreff: [Openhpi-devel] OpenHPI 2.16.0/2.17.0 timelines


Hello!

Let us discuss timeline for 2.16.0.

2.15.1 was about two months ago.
We have 56 downloads and don't have any complain (as usual :) ).
Currently there are two changes in 2.15.x tree since 2.15.1 release:
- documentation files update
- re-issue HPI call in case of connection failure (for working with
redundant HPI service)
And we have no other items to include.

I suggest middle or end of February for stable 2.16.0 release.

Trunk has much more changes done. And there are about 10-20
pending/planned changes.
May be it makes sense to release unstable 2.17.0 soon and have one more
development 2.17.1 release
and then stable 3.0.0.

What say?

        Anton Pak

----------------------------------------------------------------------------
--
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better price-free!
Download using promo code Free_Logger_4_Dev2Dev. Offer expires
February 28th, so secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsight-sfd2d
_______________________________________________
Openhpi-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openhpi-devel


------------------------------------------------------------------------------
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better price-free!
Download using promo code Free_Logger_4_Dev2Dev. Offer expires 
February 28th, so secure your free ArcSight Logger TODAY! 
http://p.sf.net/sfu/arcsight-sfd2d
_______________________________________________
Openhpi-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openhpi-devel

Reply via email to