The best projects install and run as a complete package. I have been tripped up in the past trying to collect "external dependencies". Many users don't know that "hibernate" refers to something other than a long winter snooze...
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Allen Gilliland Sent: Monday, May 01, 2006 11:17 AM To: [email protected] Subject: Re: Scrapping 2.2 -- was Re: VOTE: Release Roller 2.2-incubating Bleh. I am still very weary of the whole "download these dependencies on your own" situation. Especially if we can't even keep the proper version in the repository to develop against and just not ship it in the release. People are going to start doing the wrong thing, like getting the wrong Hibernate version maybe? I am fine with all the other stuff (#1, #3, #4), but #3 still has me worried. I don't see the benefit in replacing Hibernate long term with something else just because of an opensource licensing issue and I hate to think about putting up with this external downloads thing forever. Maybe I am just a bitter ball though? -- Allen David M Johnson wrote: > > Cliff Schmidt, our legal affairs guy, is insisting that we add Apache > copyright headers to all files in the Roller 2.2 release before we can > make the release. That's fine, but 2.2 is old news now and I'd like to > move forward. > > So... since some of us have already put the Roller 2.3 code base > through testing and into production, I would like to focus instead on > getting a Roller 2.3 release out the door with full Apache copyright, > licensing and packaging compliance. > > Here's what I'd like to do in the Roller trunk: > 1 - Add copyright headers to all files > 2 - Implement Proposal_RemoveUnshippables (http://tinyurl.com/rl8qo) > 3 - Refactor for org.apache.roller packaging > 4 - Put together a Roller 2.3 release candidate (with all 2.2 and 2.3 > features) > > I'd like to get this over as quickly as possible (i.e. today/tomorrow) > so we can proceed with Roller 3.0 developments like better URLs and > the front-page improvements. And BTW, Anil has already started #1 and > I've already implemented much of #2. > > Does anybody object to my moving ahead with this work in the trunk? > I'd welcome comments, critiques and suggestions about any part of the plan. > > - Dave > > > > > On Apr 30, 2006, at 8:22 PM, Cliff Schmidt wrote: >> On 4/30/06, David Crossley <[EMAIL PROTECTED]> wrote: >>> Craig McClanahan wrote: >>> > David M Johnson <[EMAIL PROTECTED]> wrote: >>> > > >>> > >OK, so Cliff says we need to have copyright notices on all files >>> > >before we can release 2.2 and that we should make the release on >>> > >Apache infrastructure this time. >>> > > >>> > >He also mentioned that somebody has a script that will >>> > >automatically apply said copyright notice to all source files. >>> > >Anybody know where this script can be found? >>> > >>> > There are a variety of relicensing scripts in various languages, >>> > in >>> the >>> > "relicense" subdirectory of the "committers" SVN module. You >>> should have >>> > access to that by checking out [1]. >>> > >>> > - Dave >>> > >>> > Craig >>> > >>> > [1] https://svn.apache.org/repos/private/committers >>> >>> I have some local modifications to the Perl version of that tool, >>> but i am waiting to hear the outcome of last week's board meeting >>> before committing the changes. >> >> I explained the issues to the board last week and told them that we >> now have a header approved by our lawyers -- just waiting on one last >> piece of feedback before sending out the proposed text and process to >> the legal-discuss list. I told the board I'd have the official >> resolution ready for them to vote on at the May 17th meeting. >> >> Cliff >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >
