Hi Mentors, I am starting to gather information on what needs to be done to create an incubator release. So far I have been referring to the http://incubator.apache.org/guides/releasemanagement.html there seem to be a lot of 'TODO's in that document.
Our download structure seems to have most of the artifacts listed in the documentation in terms of source code folder, license, notices etc We have the following 1. a source zip a. License b. Notice c. Folders for each of the components in Imperius following the maven structure cimspl-samples imperius-cimsplclientsideprovider cimspl-common imperius-cimsplextension imperius-cimsplprovider imperius-javaspl imperius-javasplextension imperius-splcore imperius-spleditorcore javaspl-samples 2. binary zip a. docs b. lib c. samples d. license e. notice f. readme In terms of bugs we plan to review the open ones and figure out which ones are critical and need to be closed prior to the release Do you see any missing pieces in the distribution structure that we have currently? Do you have any other pointers on what would be the best way to go about building this release? Thanks Neeraj ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ "The light at the end of the tunnel...may be you" Neeraj Joshi WebSphere XD - Compute Grid AIM, IBM Apache Imperius - http://incubator.apache.org/imperius ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ From: Kevan Miller <kevan.mil...@gmail.com> To: imperius-dev@incubator.apache.org Date: 07/07/2009 01:51 PM Subject: Re: July podling incubator board reports On Jul 6, 2009, at 7:08 PM, David L Kaminsky wrote: > did imperius ever do an official release? if not, why not? i seem to > remember the topic coming up a bunch, but no release... > No. The inability of the community to generate a release does not bode well, IMO. We added several new committers to the project back in April. I was hoping that we might see some movement in the community. However, I think progress has been minimal at best. Personally, I think it's time to start thinking about when this podling should be shutdown, unless real progress is made. --kevan