| Re: [technology-pmc] Subversive release review request |
|
Hi Wayne, Thank you for this. I
see that EGit project stays in the Technology after the graduation, so we plan
to keep Subversive in Technology as well. What are our next steps
for 1.0 release? I've submitted CQ for SVN 1.7 (http://dev.eclipse.org/ipzilla/show_bug.cgi?id=6441).
As far as I understand we need to wait for its approval and then can submit IP
Log for the review (using the http://www.eclipse.org/projects/ip_log.php?projectid=technology.subversive
service), right? The final step should be IP Log + Docuware submission and
release review, right? Best regards, Igor Vinnykov From: technology-pmc-bounces@xxxxxxxxxxx
[mailto:technology-pmc-bounces@xxxxxxxxxxx] On
Behalf Of Wayne Beaton I spoke with both
Hi Wayne, Gunnar, Thanks for your votes. Let me explain the licensing
issue for you, so maybe there is a chance of publishing 1.0 release (project
graduation) before or together with Juno. When we passed the initial legal
review the following point was indentified as a blocker for graduation. The Subversive project consists of: - Subversive module (distributed from Eclipse) - SVN library connectors JavaHL and SVNKit
(distributed from external location) SVNKit is EPL-incompatible. JavaHL includes Neon
library that is EPL-incompatible, so JavaHL was declared EPL-incompatible too.
Of course, without SVN libraries Subversive can't work with SVN repositories,
so both SVNKit and JavaHL were declared as "works with" dependencies
that should be distributed from an external location. Few years ago when we
discussed Subversive plans with Please consider this again. Can we request the project
graduation and 1.0 release now instead of releasing 0.8 version? What do you
think? Best regards, Igor Vinnykov From: technology-pmc-bounces@xxxxxxxxxxx
[mailto:technology-pmc-bounces@xxxxxxxxxxx]
On Behalf Of Wayne Beaton
Hi
Igor Hello P The Subversive project team would like to request a
project release review according with Eclipse guidelines. We are looking for
your suggestions regarding the release and your approval to submit
documentation to E Let me share with you reasons why we decided to make
the release now: 1. We need to change Subversive integration API,
because the project need to provide support of SVN 1.7. We need to create the
new version with the new API. 2. We simply out of version numbers. The latest
release was 0.7.9 and from our previous experience the update component doesn't
work correctly when the release number, i.e. 0.7.10 in our case, is
"lower" from strings comparation point of view. 3. This release was planned a long time ago. SVN team
planned to replace EPL-incompatible libraries in the SVN 1.7 release, that
should make all Subversive components EPL-compatible, so we expected to make a
project graduation and release version 1.0 once SVN 1.7 become available. But
SVN team decided to postpone libraries replacement to version 1.8 and we have
to wait again. Also the project is on Eclipse for a long time and it
can be really considered as "mature". The only p If someone requires details about EPL-compatibility
issue I will be glad to explain it as well as other topics regarding
Subversive. Best
regards, Igor
Vinnykov Subversive Team
_______________________________________________ technology-pmc mailing list technology-pmc@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/technology-pmc
--
_______________________________________________technology-pmc mailing listtechnology-pmc@xxxxxxxxxxxhttps://dev.eclipse.org/mailman/listinfo/technology-pmc
-- |