Re: Preparing for an Apache release

[Craig L Russell]

First, import the outside code into the Apache repo. I'd suggest using a jsecurity/import directory and dump whatever history you want into it. The infrastructure folks can help with the import. The import with history will take up to a few weeks, so that's critical.

Next, look at other projects and how they are released. It might give you some ideas on how to repackage the 0.9.0 release if necessary to look like an Apache release. You might decide you like the release format, and just need to add signatures and checksums to make it an Apache release. Then, start migrating code from import to trunk in the format you want to go with. Now would be a good time to validate that you like the structure or make some changes. Do the import and just change copyright notices, headers, and scripts to accommodate the new structure. Once everything is in Apache repo, make a release candidate. Run rat on the release to verify license headers etc. Review the release process (necessarily broad) at http://incubator.apache.org/guides/releasemanagement.html

Craig

On Sep 5, 2008, at 8:51 AM, Les Hazlewood wrote:

And by the way, now would be a good time to update jsecurity/STATUS and add an incubator report to jsecurity/board/200809.txt for September's board meeting. Anyone with commit privileges can update/ add these files.

Hi Joshua,

moment, but as soon as I do, you can be sure I'll ask for help :)

Thanks!

Les

As soon as our mentors tell us what exactly needs to be done, I'd be quite happy to receive your help. I don't know myself what is necessary at the On Fri, Sep 5, 2008 at 11:40 AM, Joshua Partogi <[EMAIL PROTECTED]>wrote:

I agree with you Les, I think the sooner we put a release under apache

would be great. At least this will create less defects in the future

can do?

cheers.

On Fri, Sep 5, 2008 at 9:05 PM, Les Hazlewood <[EMAIL PROTECTED]>
wrote:

for those who are migrating to the Apache release. Is there any help I

After I get 0.9.0 out (the last non-apache release), I'd like to do a

0.9.1

release.

release - all the license headers would be in place, the proper
NOTICE/README files are located appropriately, etc.


0.9.0, it would just be an Apache release.


under our belt without having to worry about functionality - a

The only difference is that the 0.9.1 release would be an official Apache In essence, there would be zero difference in code or functionality with I'm thinking this is a good idea because it would get one Apache release test-but-not-quite-test run, so to speak. It would also look good to

have

an initial *stable* release available to the rest of the Apache

community.

Is this a good idea?  Any opinions?

--
Commitment is what moves you forward
Persistency is what keeps you going
Passion is what takes you even further
http://joshuajava.wordpress.com/

Craig L Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:[EMAIL PROTECTED]
P.S. A good JDO? O, Gasp!

smime.p7s
Description: S/MIME cryptographic signature