-1 for the very same reasons Jake mentioned. We're not ready to call anything a release candidate yet.
- Dave On Mon, Nov 18, 2013 at 9:10 AM, Jake Farrell <jfarr...@apache.org> wrote: > Hey Tim > +1 to getting the code imported so people can start submitting patches and > helping work on it. > > "In light of recent conversations" - There have been no conversations on > the any of the mailing lists up to this initial import email, please make > sure conversations regarding releases are carried out on the mailing lists. > > -1 to trying to tag an Apache release candidate out of this initial import > in its currently state due to the following issues > > * No Apache license header on any files > * Missing NOTICES file > * The namespace are still org.usergrid > * No artifact provided and no signatures > > Please see http://incubator.apache.org/guides/releasemanagement.html and > https://www.apache.org/dev/release-publishing.html for additional details > that should be in place before proposing a release candidate. > > -Jake > > > > On Mon, Nov 18, 2013 at 2:13 AM, Tim Anglade <timangl...@apache.org>wrote: > >> (cc’ing all committers on their personal address; if you have not done so, >> please subscribe to the Apache Usergrid dev list: >> https://mail-archives.apache.org/mod_mbox/incubator-usergrid-dev/) >> >> >> Hi all, I’d like to propose the following tag as the basis for our initial >> “code drop” to the Apache Software Foundation. >> >> https://github.com/usergrid/usergrid/tree/v1.0-rc1 >> >> In light of recent conversations I further propose that we tag a release >> matching our eventual code drop, and that that eventual release be >> numbered >> 1.0 (hence the “v1.0-rc1” label for this release candidate). >> >> I propose an initial 72-hour window for discussion on this release >> candidate. If all matters are resolved by then Dave J. has offered go >> ahead >> and submit this release as our official code drop for entry into the >> Apache >> Incubator. At that time, Apigee will proceed and close down its old >> repositories. >> >> >> Additional notes >> 1. This new repository is a git subtree merge of 12 distinct repositories >> developed previously under the “apigee” or “scottganyo” accounts on >> github. >> For full details of what has been merged see the release notes: >> https://github.com/usergrid/usergrid/releases/tag/v1.0-rc1 >> 2. The merge preserves full history for all files despite their relocation >> (e.g. https://github.com/usergrid/usergrid/commits/master/stack/README.md >> ). >> 3. I added instructions in the root README on how to upgrade your personal >> code setup and pull in work you may have had on a personal fork that was >> not merged in the new repo yet: >> >> https://github.com/usergrid/usergrid#how-to-update-your-code-setup--pull-changes-from-your-old-forks >> 4. If need be, you can also pull changes from this new repo into your old >> forks: >> >> https://github.com/usergrid/usergrid#how-to-pull-commits-made-on-this-repo-into-your-old-forks >> 5. For a limited time, I volunteer to maintain asynchronous branches >> matching each previous repository (e.g. >> https://github.com/usergrid/usergrid/tree/portal, >> https://github.com/usergrid/usergrid/tree/sdks/ios, etc.). These have the >> advantage of being immediately compatible with the old independent repo >> (i.e. you can push/pull your old fork of apigee/usergrid-portal directly >> on >> the “portal” branch of usergrid/usergrid). >> 6. I recommend we support items #4 and #5 for a limited time only and >> strongly encourage all interested contributors to upgrade their setup per >> the instructions in item #3. >> > >
