Doing #2 wouldn't be identical to doing #1? If you don't have the bandwidth for that, would you please share the cheatsheet for it and I'll take care of it.
>From this list is missing what I've mentioned in a previous email: * Have a banner in GH Oozie GIT that we've moved * Have a banner in GH Oozie PAGES that we've moved * Shutdown the Y! Oozie JIRA (redirection to Apache JIRA would be nice) * Switch off GH Issues (and admin can do that) * Close [email protected] to membership and emails, see how to put a we've moved banner/message there Thxs. Alejandro On Thu, Aug 25, 2011 at 2:42 PM, Mohammad Islam <[email protected]> wrote: > > > Hi All , > > This is the current status: > > 1. Moving master code to trunk: In Progress. Scheduled to be done on next > week. Owner: Mohammad > > 2. Moving branches code (specially 2.3) to SVN branch. Not planned. Owner: ? > > 3. Migrating Old JIRA to new apache JIRA. Jira created: > https://issues.apache.org/jira/browse/INFRA-3883. Owner: ? > > 4. Migration of Git issues to new JIRA. Not started. Owner:? > > 5. Creating a basic top level Oozie site based on APT formatting: Started > should be there in couple of days. Owner: Mohammad > > 6. Mailing-list announcement. Status: Not started. Expected to be done by > this Friday. Owner:Mohammad > > 7. Establish/document the standard process of new code review. Owner: > Alejandro and Mohammad. > > 8. Update the status page for the Apache board. Owner : Mohammad will help > Alan. > > 9. > > Please feel free to add your name into any items. > > > Regards, > Mohammad
