Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [orbit-dev] Bugfixing 3rd party code due to lack of a release

Thanks Adrian, Oisin, and Dave!

Regarding IP: Oh yes, of course I don't work around IP
due diligence but follow it properly, though with the
least possible effort :-)

Adrian - do I need any explicit statements from the patch 
contributor, or is he implicitly licensing his stuff under 
APL 2.0 by attching his patch on Apache Bugzilla / Jira?

I'd love to file a CQ for this, but the link under 
committertools directs me to the Portal, and in the
Portal I cannot find a link for a CQ... any ideas?

Regarding the patch: It would be applied to my personal
copy of the released Commons Net 1.4.1 package (which
currently is in Orbit), the single .java file compiled,
and checked in back into Orbit.

Regarding version numbering: I thought I'd just use the 
CVS-tag-based qualifier, which will increase automagically
when I tag the new version. I thought I'd might add some
readme stating that the bugs were fixed, or update the
about.html explaining that the version is now 1.4.1+ .

Thanks,
--
Martin Oberhuber
Wind River Systems, Inc.
Target Management Project Lead, DSDP PMC Member
http://www.eclipse.org/dsdp/tm 


Back to the top