Dear Richard, all
I apologize for the few activity around the UPnP sub-project, we talked
about the UPnP release in Munich but I missed the target.
Nevertheless we (me and Stefano) are testing the code and we would like
to submit some changes before doing an official release.
In order to be safe the end of December is the date we can reasonably
indicate.
I know the code has been sufficiently tested in the past and, excepted
for the documentation still missing, we could release the current version.
But let me say which are our plan (unordered incomplete list).
1. release two versions targeting JRE 1.3 and >1.4
2. remove the dependence with the upnp.extra bundle from the basedriver
3. enable the configuration of different parameters which are now
constant (e.g. MX, used port, bootstrap search type, exporter and
importer module)
4. improve the threading and buffer capacity of cyberlink (high)
5. back porting cyberlink to JRE 1.3
6. provide a set of helper classes with the extra bundle
7. rewrite the example code using extra bundle
8. write the documentation
-------
9. include part of Didier's sandbox code in the UPnP subproject
10. add security capabilities to the base driver.
Many of the points 1-8 are already implemented, as we are testing the
base driver on a Stargate gateway (ARM based), but we have to reorganize
the code and repository used. Point 9-10 are not required for the
release and they will have lower priority.
ciao
francesco
Richard S. Hall wrote:
The message from Lucas Galfaso was actually well timed.
At ApacheCon I was talking with Felix Meschberger about our need to
actually start making official releases of our sub-projects. Actually,
my thinking was motivated by the recent users@ message from Matthias
Luebken, where he was asking about how to get access to our service
implementations. Both of these recent messages illustrate that we need
to improve on the current situation.
In general, we have sub-projects that are in good shape and some that
are experimental. My view is that we should attempt to make official
release of all sub-projects as long as they do something useful (i.e.,
as long as it is not too unstable). My thinking is that they only way we
will start getting feedback for JIRA issues and possible contributors
for our sub-projects is by making them reasonably easy to access.
So, I think we need to make a list of which sub-projects we should
target for release (sub-project contributors should speak up about their
sub-projects) and start releasing them, giving them an appropriate
version number to indicate their level of completeness/stability.
It would also be good for us to figure out how we can create an OBR
repository for our released bundles.
This will likely involve a bit of effort, but if we actually want people
to use our stuff, we have to make it easy for them to do so. Let's try
to jump start this activity.
Thoughts?
-> richard
