Release strategy? about andlytics HOT 35 CLOSED

I also thought about doing that. In the end we need a device account (I also have one, like you) but I guess we should have a dedicated one for the app.
My idea would be to create a new account and then add other devs to the account so they can release new versions.

I can create one and let you know. Any comments on this?

Besides that we should create an organization on github. Comments on this?

from andlytics.

I meant dev account...

from andlytics.

Don't know, I'm not so experience with these things. But I know the way of 8p8web with a donation button for an open source app is the wrong one

from andlytics.

It would be usefull if other people could merge into the master of all the forks

from andlytics.

Donation is another thing. Regarding the account I am willing to spend the 25 dollars for the account and add you guys so we all can publish. I just need to check which information would than be visible to you since I do not want you guys to have access to my credit card information :-)

Sent via Hubroid

from andlytics.

Regarding merging I think there is the option for an 'organization' so members can merge into the organization's master repo

Sent via Hubroid

from andlytics.

Publish = Google Play

Sent via Hubroid

from andlytics.

I think there is a "formal problem", because there is no such thing as a "community account" on Google Play.

Looking at other open source projects that were closed source initially, for example "c:geo", they registered an account with the name "c:geo team" and a .org domain.

The Andy's proposal is the nearest to this model for now, but let's discuss it a little longer.

Btw, I contacted 8p8web to suggest to merge his project with us. I'm waiting for a reply. Fragmentation is bad.

from andlytics.

@ALL I just created a organisation and added most of you guys to this organization so we have an "account" to pull/push/merge etc. and build releases based on this "organization".

Bruno and I have admin rights to the organization. Let's see if this works for us.

@brunomendola I also added @8p8web - can you transfer your repo to the organization? You also have all permissions possible on the organization.

from andlytics.

@brunomendola Nice just realized you already moved the repo :) I already registered an Play Developer Account :) Registrations isn't completed yet, so we can't publish yet.

@brunomendola @fda77 @8p8web @devwom @andlytics can you guys sent me your email-addresses associated with your google account, so I can add you to the publisher account of Andlytics :)

As I said: after registration is completed by Google and I added you to the account we all can publish

Thanks to @brunomendola 's transfer of the repo you all can now push to the master and merge (haven't tried it yet). So this is the new official master :) All future releases should be done via this repo and also each release should be tagged for bugfix research and documentation.

Can't wait for the first release via the new dedicated Play account :)

Thank you all for your efforts in keeping this app alive and I hope I do not give you all the impression of being too pushy.

In case someone else should be added to the Organisation to have push permission just drop @brunomendola or @AndyScherzinegr a line :)

from andlytics.

Thank you Andy, great job!

This is the best for the project, as I realized that I can't be online 24/7 to validate and merge all the many pull requests, so now we could do this work together.

I hope that the developers who already released their version of Andlytics on Google Play will merge their projects with us.

from andlytics.

I hope so too! It is my impression that we have quite some talent here and in my opinion a joint effort will lead to the best brew possible for this app since we will all work together bringing different skills to the dev's table :)

Can you in send me a private message with your googlemail-address (don't know if this is possible on github though :) and I will add you to the Google play account like I said :)

from andlytics.

To clear up any upcoming confusion regarding Google Play. It is a three step process:

1. I invite you based on the googlemail address
2. you respond to the invitation
3. I "OK" your response (don't really know why Google implemented this re-verification....)

--> your in :)

from andlytics.

Wow this goes too fast :-)
I think multi publishing is good idea, but I think we should remark a procedure prior to publishing.
May be as simple as open issue with Title "publishing", and closing it when finished. In order to avoid publishing collisions.
About email do you know how can we send private messages?. I'm looking for it but without success.

Great job guys!!

from andlytics.

Agreed!

Here is an idea :
The organization's repo is the master for the releases. Everyone develops his features and fixes on a fork and pushes them to the master for the release.
At the beginning of a release we define the features in a milestone (can be done on github). Nothing besides that and Bugfixes are allowed to be pushed to the master.
We assign one dev per release to be in charge for this release (build+publish on Google Play).

Any comments?

In my experience this would be a lean release management approach... :-)

@devwom just go to my profile, click on my website an dsent me your email address via the contact form. Worked fine for Bruno :-)

from andlytics.

Fine, but I have 2 comments

1. We should add additional step prior to publish, in order to allow localize possible new strings.

2. All Andlytics users know about Google Play login change issues, and they should be fixed asap. To do that we should define "priority fix" branch/fork or better way.

from andlytics.

1. absolutely, yes

2. Don't quite understand the issue here?! In case we need a hotfix release which could always fork a release tag, fix the problem, release, push back to master. Right?

from andlytics.

The "GitHUB organization" seems to work properly, thx AndyScherzinger

from andlytics.

I want mean that Andlytics will need a lot of hotfix'es, due Google play login changes. May be fork/fix/push master is the best way. I'm not cvs's advanced user so I only want remark this issue.

from andlytics.

@fda77 happy to see it's working for everybody so far, Google Play might still take another while to "process the registration"...

@devwom I totally agree with you on this issue. Only way I see right know is fork/fix/release on a fork and push back to master... point here is that the fix needs to be done be one of the developers with publishing rights on the Google Play account, which would be you, me fda77 and Bruno atm. Although I would also like to have Maurizio aka @8p8web on board für this organization and as a publisher on the shared Google Play Publisher account.

from andlytics.

Hello Andy, thanks for your great effort, if you want to add my Google account to publish here is the email address: [email protected]

Thanks,
Maurizio

from andlytics.

Hi Maurizio! Done! :)

@ all: Still waiting for Google to do their job..."Your Registration to Google Play is still being processed."

from andlytics.

Accepted immediatly ;) thank you very much!

On 06/23/2012 11:41 AM, Andy Scherzinger wrote:

Hi Maurizio! Done! :)

@ all: Still waiting for Google to do their job..."Your Registration to Google Play is still being processed."

---

Reply to this email directly or view it on GitHub:
https://github.com/Andlytics-Project/andlytics/issues/12#issuecomment-6523837

from andlytics.

Your welcome but we are still waiting for Google to be done with this registration. We can't publish anything before that...

from andlytics.

can't wait for the approval but should be a matter of a day or two
(maybe /working/ days...)

On 06/23/2012 11:46 AM, Andy Scherzinger wrote:

Your welcome but we are still waiting for Google to be done with this registration. We can't publish anything before that...

---

Reply to this email directly or view it on GitHub:
#12 (comment)

from andlytics.

Just a little update on this matter. It might take a while....

Google suspended the account since I opened and account with the Andlytics Google Account but managed to pay with my personal one. Their system obviously didn't like this... I'll try to deal with this matter tonight... grrrr

from andlytics.

The account is enabled. What's about the .keystore? Should we add it to the GIT and set the password to "andlytics"?

from andlytics.

I've seen that :)

Good question. I already created one on my home PC. I am not sure if we should add it to the repo since it is public. Which means anyone could create a signed apk of the app and publish it (somewhere) and it would be signed with our release key.
So it might be better to just share it with the people who actually do the publishing on Google Play.

Any comments?

from andlytics.

I'm agree with Andy. Make public will allow create a lot of valid signed andlytics versions.
I have thought that the best way could be sign it using a remote server (I do not know if it is possible). It will allow us store it in only one place, and it could be easily add and remove more people sing andlytics.
We do not know how many people could appear and disappear from project, and publishing keystore it is not good idea.

from andlytics.

Signed apk's would not help anyone without acces to the developer account. Also the package name will be occupied in the market. If the .keystore is only in 1 place it could be lost..

from andlytics.

true for the market, but you could still build a signed apk and put it on a server. It would still be installed and override our official apk.

How about putting it into the cloud? shared dropbox folder?

from andlytics.

If not in the git, it doesn't matter where :)

from andlytics.

True, but if I put it in a dropbox and noone else has dropbox....

from andlytics.

anyone who needs the keystore (devs on the github organization) drop me an email with your dropbox-email, so I can invite you to the folder with the store and the password...

from andlytics.

Same as Developer Account

from andlytics.