[aerogear-dev] AeroGear Android 1.0.1 - Under staging repository

[Bruno Oliveira]

-1 at first glance, it looks very confuse to me

On Jun 6, 2013, at 7:41 PM, Tadeas Kriz <tkriz at redhat.com> wrote:

> How about making a different ("staging") branch for the aerogear-android-todo repository, which will be using the 1.0.1 version. And after the 1.0.1 is promoted into public repository, merge the "staging" branch back into master. That wouldn't confuse newcomers, because when they'd clone master, it would fetch aerogear from Maven Central. And for the "staging" branch, there should probably be information about the staging nexus repository in the Readme file.
> 
> ----- Original Message -----
> From: "Bruno Oliveira" <bruno at abstractj.org>
> To: "AeroGear Developer Mailing List" <aerogear-dev at lists.jboss.org>
> Sent: Thursday, June 6, 2013 5:04:20 PM
> Subject: Re: [aerogear-dev] AeroGear Android 1.0.1 - Under staging repository
> 
> We wrote that a long long time ago. Would be really nice to hear your 
> thoughts.
> 
> We do not promote first, we stage it first. In this way people can test 
> with the staging repository, if some bug are found we still have time to 
> revert it.
> 
> As far is I know if you promote it, it would be released on Maven Central.
> 
> Karel Piwko wrote:
>> Thanks Daniel and Bruno.
>> 
>> I'd say that the release process is fine expect committing changes before
>> the staging repo is promoted to release repo, which leaves master temporary
>> broken. Is there any reason why promoting can't happen first? Like that
>> commit triggers Travis CI?
>> 
>> Karel
>> 
>> On Wed, 05 Jun 2013 14:00:24 -0300
>> Bruno Oliveira<bruno at abstractj.org>  wrote:
>> 
>>> Hi Karel, we follow this process
>>> https://github.com/aerogear/collateral/blob/master/RELEASE_HOWTO.md
>>> 
>>> And we're open for suggestions, feel free to change it.
>>> 
>>> Daniel Passos wrote:
>>>> On Wed, Jun 5, 2013 at 10:51 AM, Karel Piwko<kpiwko at redhat.com
>>>> <mailto:kpiwko at redhat.com>>  wrote:
>>>> 
>>>>     I think it would be great if repositories that require it, like [1] [2]
>>>>     are bumped in master after it goes off staging. That would solve
>>>>     some confusion
>>>>     about readme instructions not being accurate.
>>>> 
>>>> 
>>>> My bad, won't happen again
>>>> 
>>>>     Karel
>>>> 
>>>>     [1] https://github.com/aerogear/aerogear-android-todo
>>>>     [2] https://github.com/aerogear/aerogear-android-integration-tests
>>>> 
>>>>     On Tue, 04 Jun 2013 11:31:26 -0300
>>>>     Bruno Oliveira<bruno at abstractj.org<mailto:bruno at abstractj.org>>  wrote:
>>>> 
>>>>> Good morning guys.
>>>>> 
>>>>> Passos will release AeroGear Android 1.0.1, but before press THE
>>>>     button
>>>>> to release. Would be nice if some bug hunters could test it and file
>>>>> bugs to Passos.
>>>>> 
>>>>> Staging repository:
>>>>     https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-097/
>>>> 
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> 
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> 
> -- 
> -
> abstractj
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev