You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@usergrid.apache.org by Tim Anglade <ti...@apache.org> on 2013/11/18 08:13:12 UTC
Release Candidate #1 for Usergrid 1.0 / Apache Incubator Code Drop
(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.
Re: Release Candidate #1 for Usergrid 1.0 / Apache Incubator Code Drop
Posted by Nate McCall <na...@thelastpickle.com>.
-1 on an RC per Jake's list.
Let's import the code so we can devide and conquer on the above. I created
four initial JIRA issues for precisely this, so "game on."
Also, everyone not on dev@usergrid.incubator.apache.org please sign up for
it now.
On Mon, Nov 18, 2013 at 8:17 AM, Dave <sn...@gmail.com> wrote:
> -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 <jf...@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 <timanglade@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.
> >>
> >
> >
>
--
-----------------
Nate McCall
Austin, TX
@zznate
Co-Founder & Sr. Technical Consultant
Apache Cassandra Consulting
http://www.thelastpickle.com
Re: Release Candidate #1 for Usergrid 1.0 / Apache Incubator Code Drop
Posted by Dave <sn...@gmail.com>.
-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 <jf...@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 <ti...@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.
>>
>
>
Re: Release Candidate #1 for Usergrid 1.0 / Apache Incubator Code Drop
Posted by Lewis John Mcgibbney <le...@gmail.com>.
Hi,
Can you please try dev-subscribe@ and I'll try and mod you through?
Ta
Lewis
On Tue, Nov 19, 2013 at 4:00 PM, Shaozhuang Liu <st...@hibernate.org> wrote:
> any idea why this ?
> seems my address has been put into spam list or something?
>
> ##################################################################################################################
> Hi. This is the qmail-send program at apache.org.
> I'm afraid I wasn't able to deliver your message to the following
> addresses.
> This is a permanent error; I've given up. Sorry it didn't work out.
>
> <de...@usergrid.incubator.apache.org>:
> 192.87.106.230 failed after I sent the message.
> Remote host said: 552 spam score (5.8) exceeded threshold
> (FSL_HELO_NON_FQDN_1,HELO_LOCALHOST,HTML_MESSAGE,NORMAL_HTTP_TO_IP,WEIRD_PORT
>
> --- Below this line is a copy of the message.
>
> Return-Path: <st...@apache.org>
> Received: (qmail 82682 invoked by uid 99); 19 Nov 2013 15:57:17 -0000
> Received: from minotaur.apache.org (HELO minotaur.apache.org)
> (140.211.11.9)
> by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Nov 2013 15:57:17
> +0000
> Received: from localhost (HELO [192.168.1.155]) (127.0.0.1)
> (smtp-auth username stliu, mechanism plain)
> by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Nov 2013
> 15:57:17 +0000
> From: Shaozhuang Liu <st...@apache.org>
> Content-Type: multipart/alternative;
> boundary="Apple-Mail=_0FC75B40-1F39-473F-A4D6-F04F4A4A6417"
> Subject: error when building website locally
> Message-Id: <22...@apache.org>
> Date: Tue, 19 Nov 2013 23:57:13 +0800
> To: "dev@usergrid.incubator.apache.org" <dev@usergrid.incubator.apache.org
> >
> Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\))
> X-Mailer: Apple Mail (2.1812)
>
>
> ##################################################################################################################
>
> -------------------------
> Best Regards,
>
> Strong Liu <stliu at hibernate.org>
> http://about.me/stliu/bio
>
> On 2013Nov 19, at 1:26 AM, Tim Anglade <ti...@apache.org> wrote:
>
> > Good to know. I wasn't aware that “Release Candidate” carried a
> particular meaning at the ASF, although in retrospect that should have been
> obvious. What should this tag be called, if anything?
> >
> > On Monday, November 18, 2013, Jake Farrell 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 <ti...@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.
> > >
>
>
--
*Lewis*
Re: Release Candidate #1 for Usergrid 1.0 / Apache Incubator Code Drop
Posted by Shaozhuang Liu <st...@hibernate.org>.
any idea why this ?
seems my address has been put into spam list or something?
##################################################################################################################
Hi. This is the qmail-send program at apache.org.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.
<de...@usergrid.incubator.apache.org>:
192.87.106.230 failed after I sent the message.
Remote host said: 552 spam score (5.8) exceeded threshold (FSL_HELO_NON_FQDN_1,HELO_LOCALHOST,HTML_MESSAGE,NORMAL_HTTP_TO_IP,WEIRD_PORT
--- Below this line is a copy of the message.
Return-Path: <st...@apache.org>
Received: (qmail 82682 invoked by uid 99); 19 Nov 2013 15:57:17 -0000
Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9)
by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Nov 2013 15:57:17 +0000
Received: from localhost (HELO [192.168.1.155]) (127.0.0.1)
(smtp-auth username stliu, mechanism plain)
by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Nov 2013 15:57:17 +0000
From: Shaozhuang Liu <st...@apache.org>
Content-Type: multipart/alternative; boundary="Apple-Mail=_0FC75B40-1F39-473F-A4D6-F04F4A4A6417"
Subject: error when building website locally
Message-Id: <22...@apache.org>
Date: Tue, 19 Nov 2013 23:57:13 +0800
To: "dev@usergrid.incubator.apache.org" <de...@usergrid.incubator.apache.org>
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\))
X-Mailer: Apple Mail (2.1812)
##################################################################################################################
-------------------------
Best Regards,
Strong Liu <stliu at hibernate.org>
http://about.me/stliu/bio
On 2013Nov 19, at 1:26 AM, Tim Anglade <ti...@apache.org> wrote:
> Good to know. I wasn't aware that “Release Candidate” carried a particular meaning at the ASF, although in retrospect that should have been obvious. What should this tag be called, if anything?
>
> On Monday, November 18, 2013, Jake Farrell 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 <ti...@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.
> >
Re: Release Candidate #1 for Usergrid 1.0 / Apache Incubator Code Drop
Posted by Tim Anglade <ti...@apache.org>.
Good to know. I wasn't aware that “Release Candidate” carried a particular
meaning at the ASF, although in retrospect that should have been obvious.
What should this tag be called, if anything?
On Monday, November 18, 2013, Jake Farrell 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 <timanglade@apache.org<javascript:;>>
> 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.
> >
>
Re: Release Candidate #1 for Usergrid 1.0 / Apache Incubator Code Drop
Posted by Jake Farrell <jf...@apache.org>.
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 <ti...@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.
>