Automate release process

[cadorn]

The proposed release process will work as follows:

Manual

1. Make entry for release in CHANGELOG.md including:
   • Release date
   • $fixed tag value tied to the release
   • Release notes
   • Links to release resources
2. Tag repository using $fixed tag value
3. Push tag to github

Automatic

1. firebug.io continuous delivery system will pick up new tag
2. generate xpi & make available for download
3. Search for open issues that are labelled fixed and insert $fixed <release> comment
4. Feed summary page for release
5. Tweet release page

[cadorn]

@janodvarko What do you think?

[janodvarko]

Sounds good to me

generate xpi & make available for download

Note that this might involve upload on AMO (beta and final releases)

Search for open issues that are labelled fixed and insert $fixed comment

Search for closed issues that are not labeled as resolved insert $fixed comment

So, these steps should happen:
0. Run tests, first?

1. Change version number in package.json
2. Generate update.rdf file (for getfirebug.com)
3. generate xpi using: jpm xpi
4. Upload to getfirebug.com and AMO (xpi + update.rdf)
5. Commit package.json and create git-tag, push.
6. Search for closed issues that are not labeled as resolved insert $fixed comment
7. Put $fixed comment into those issues
8. Mark these issues as resolved (using a label)
9. Make new entry in release-notes.md file and commit

Honza

[cadorn]

Ok. I have scripts for most of this. Going to focus on the test runner first. Once all tests pass on a commit to master the commit is available for release which will trigger the release process.

I want to get this working for firebug.next and a sample firebug.next extension. Do we have a reference sample extension for firebug.next yet? Where is the code?

[janodvarko]

Once all tests pass on a commit to master the commit is available for release
which will trigger the release process.

How we can specify which commit (where all tests pass) should trigger the release process? Of course we don't want to trigger the process every time the tests are green...

Do we have a reference sample extension for firebug.next yet?

Not yet

Honza

[cadorn]

How we can specify which commit (where all tests pass) should trigger the release process? Of course we don't want to trigger the process every time the tests are green...

Oh, the commit will be available for release. A release using that commit can then be triggered manually using the admin.

[cadorn]

I'll be working on all the pieces needed for this over the holidays. I expect to have this start working early next year.

[cadorn]

Things got pushed. Trying to slot in asap.

[cadorn]

Going to pick this up after the new clean dependency management system is done: https://github.com/sourcemint/sm.genesis