684762 - publish regular stable Socorro releases

Status: RESOLVED FIXED

(Socorro :: Infra, task, P2)

Description

[Robert Helmer [:rhelmer]]

People who wish to install Socorro (or upgrade an existing install) have to track our development releases, which are targetted towards Mozilla's needs it isn't always clear which release they should use.

We also have problems with new, from-scratch installs (bug 653362). Furthermore, 2.2 introduced a split between "old" and "new" tcbs that is quite confusing for new installs.

We should make it easy for others to install and keep Socorro up to date. This gives them an incentive to report and fix bugs that are more likely to be recent and useful to us.

I propose to start simply:

1) get the basic "from scratch" install instructions finished (this is the intent of the INSTALL file)

2) come up with a simple way to test such an install (we could use the socorro-vagrant project for this)

3) cherry-pick the builds from our CI that we use for production, and publish these as releases occasionally (for example https://jenkins.mozilla.org/job/socorro-master/lastSuccessfulBuild/artifact/socorro.tar.gz - we can add RPM and deb and perhaps other packages in the future).

Targetting this towards 2.3, but it shouldn't block.

Comment 1

[Robert Helmer [:rhelmer]]

(In reply to Robert Helmer [:rhelmer] from comment #0)
> I propose to start simply:
> 
> 1) get the basic "from scratch" install instructions finished (this is the
> intent of the INSTALL file)


This is done, although getting the initial dataset loaded is still a challenge.
For internal Mozilla use we have scrubbed production data such as bug 691891 but for publishing purposes we should probably make up a fake dataset.


> 2) come up with a simple way to test such an install (we could use the
> socorro-vagrant project for this)
> 
> 3) cherry-pick the builds from our CI that we use for production, and
> publish these as releases occasionally (for example
> https://jenkins.mozilla.org/job/socorro-master/lastSuccessfulBuild/artifact/
> socorro.tar.gz - we can add RPM and deb and perhaps other packages in the
> future).
> 
> Targetting this towards 2.3, but it shouldn't block.


We could start doing this as of 2.4
Solving the data issues would be nice but I think we can get community testing help on that.

Comment 2

[Robert Helmer [:rhelmer]]

Our current release process (https://wiki.mozilla.org/Socorro/Release_Process) makes this a lot better. We tag builds that we expect to work for other people, and you can even get them as zip files: https://github.com/mozilla/socorro/tags/

I think the real problem now is that it's hard to bring up Socorro from scratch, but we're working on that by continuing to refactor the DB into something that makes sense, and thinking about the first-user install experience.