Hello, thanks for your input, Martijn. As you pointed out there's some work left regarding licensing, readme and build stuff.
I have some questions: - Are Eclipse project files forbidden? We put them in for convenience reasons. - Is the maven distributable a must for the initial incubating release or could this be a new feature for the next rel.? The reason we want this release out as soon as possible is that the namespace from the last (non Apache) release to the new one has changed. So everyone who would download the last non-Apache-incubator-release would be forced to change his source code after upgrading to the first Apache Incubator release which we find quite painful for the user/developer. Any inputs from anyone would be appreciated, Ciao Jörg :-) -----Ursprüngliche Nachricht----- Von: Martijn Dashorst [mailto:[EMAIL PROTECTED] Gesendet: Sonntag, 17. August 2008 17:27 An: [email protected] Betreff: Re: More votes required for Empire-db release The licenses, notice and such should go into the META-INF directory in the jar file, not in the root. The manifest.mf should contain information such as documented here: http://commons.apache.org/releases/prepare.html#checkjarmanifest Martijn On Sun, Aug 17, 2008 at 5:18 PM, Martijn Dashorst <[EMAIL PROTECTED]> wrote: > - the struts package contains license files for the dependencies, the > core distribution doesn't (which contains e.g. hsqldb) > - the hsqldb jar file (in the empire-db) does not show a version > number in its name > - the struts package doesn't list the freemarker license > - also need Apache license headers in TLD, Java, jsp, properties > files and css files (also check the examples!) > - struts package also doesn't contain build file, readme, release notes > > Martijn > > On Sun, Aug 17, 2008 at 5:00 PM, Martijn Dashorst > <[EMAIL PROTECTED]> wrote: >> I've run RAT on the distribution >> (apache-empire-db-2.0.3-incubating.zip) and noticed the following >> things: >> >> - package.html files don't have Apache license header >> - eclipse project files are in the distribution >> - no build files -> how do I build from source? >> - no maven distributable? -> hurts adoption >> - no readme/release notes >> >> Martijn >> >> On Sun, Aug 17, 2008 at 3:30 PM, Martijn Dashorst >> <[EMAIL PROTECTED]> wrote: >>> Hmm >>> >>> There are a couple of things that worry me: >>> - no discussion whatsoever on dev@ about the forthcoming release >>> - no RAT report >>> - are all licensing issues resolved? >>> - no discussions, period? >>> >>> It feels like there is a lot of off-line communication happening, >>> which is not good. >>> >>> - growing the community sounds like me to be the number one thing to >>> concentrate on, not getting a release out of the door asap >>> >>> Martijn >>> >> >> >> >> -- >> Become a Wicket expert, learn from the best: http://wicketinaction.com >> Apache Wicket 1.3.4 is released >> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3. >> > > > > -- > Become a Wicket expert, learn from the best: http://wicketinaction.com > Apache Wicket 1.3.4 is released > Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3. > -- Become a Wicket expert, learn from the best: http://wicketinaction.com Apache Wicket 1.3.4 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.
