Hi,
Here are some of the problems I've found ...
http://people.apache.org/%7Epamarcelot/ldapstudio_0.6.0/LDAP_Studio_0.6.0.zip
----
(1) License file should be include the licenses of all the components
use like the one for ANTLR etc. Also might want to use LICENSE.txt
instead to just be consistent but this is not as much of a big deal.
See http://www.apache.org/dev/release.html here:
"If A Distribution Contains Code Under Several Licenses, Should It
Contain Several License Files?
No - all license information should be contained in the LICENSE file.
When a distribution contains code under several licenses, the LICENSE
file should contain details of all these licenses. For each component
which is not Apache licensed, details of the component and the license
under which the component is distributed should be appended to the
LICENSE file."
(2) There is no NOTICE.txt file in this with the proper attributions.
(3) Also you might want to let people know that this is for windows
because of the exe in it. Perhaps you have all these materials
(LICENSE.txt and NOTICE.txt) in the resultant installation footprint.
You might just want to offer up the exe for a windows release artifact
and make sure these files are present in the installation footprint.
http://people.apache.org/%7Epamarcelot/ldapstudio_0.6.0/LDAP_Studio_0.6.0_linux_i386.tar.gz
----
(1) see #1 above. Also need to append license for eclipse and
attribution for Eclipse licensed stuff.
(2) see #2 above.
(3) I see a jar here from IBM com.ibm.icu_3.4.5.jar that needs an
attribution. Also is the license ok for this. I have no clue what it is.
(4) We need to put the LICENSE.txt and the NOTICE.txt files into the
META-INF of all the directory artifacts in the plugins directory.
See http://www.apache.org/dev/release.html here:
"Raw artifacts may be distributed if they contain LICENSE and NOTICE
files. For example, the java artifact format is based on a compressed
directory structure and those projects wishing to distribute raw jars
place LICENSE and NOTICE files in the META-INF directory within the jar."
Check out a project like ant built with ant to see how they include all
this stuff automatically in the build.
---
I'll presume the ppc version of this tarball is pretty similar. I have
not had a chance to test the dmg either.
Please don't be dismayed by all these requirements. They are things
mandated by all Apache releases and we must make sure we abide by them.
However once you get your build to incorporate these things then
releasing is much easier after the first time.
Regards,
Alex
begin:vcard
fn:Alex Karasulu
n:Karasulu;Alex
org:Apache Software Foundation;Apache Directory
adr:;;1005 N. Marsh Wind Way;Ponte Vedra ;FL;32082;USA
email;internet:[EMAIL PROTECTED]
title:Member, V.P.
tel;work:(904) 791-2766
tel;fax:(904) 808-4789
tel;home:(904) 808-4789
tel;cell:(904) 315-4901
note;quoted-printable:AIM: alexokarasulu=0D=0A=
MSN: [EMAIL PROTECTED]
Yahoo!: alexkarasulu=0D=0A=
IRC: aok=0D=0A=
PGP ID: 1024D/4E1370F8 BBCC E8D8 8756 2D51 C3D4 014A 3662 F96F 4E13 70F8=0D=0A=
x-mozilla-html:FALSE
url:http://people.apache.org/~akarasulu
version:2.1
end:vcard
