Project

General

Profile

Feature #428

Release 0.6

Added by Rogers, Chris over 11 years ago. Updated over 11 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Code Management
Target version:
Start date:
28 April 2011
Due date:
% Done:

100%

Estimated time:
Workflow:

Description

Try to work up a release script for this release...

#1

Updated by Tunnell, Christopher over 11 years ago

something like:

if pass tests:
bzr export blah.tar.gz

I don't think you can upload directly to redmine from a shell (I tried and couldn't figure it out).

#2

Updated by Tunnell, Christopher over 11 years ago

We should probably have our release script create a branch for each release that we can publish nightlies of. This allows us to port back patches.

For instance, I really want 1.X to have spacepoints. But third_party issues should port back to the 0.X series.

#3

Updated by Tunnell, Christopher over 11 years ago

How we tie it in with redmine is unclear. Maybe we should just put everything here:

http://micewww.pp.rl.ac.uk/static_files/

instead?

#4

Updated by Tunnell, Christopher over 11 years ago

  • Status changed from Open to Rejected
  • % Done changed from 0 to 100

reopen if you want. I think a release script is not feasible since we have to look at the jenkins stuff, run tests (can be automated) and upload to redmine (impossible by script).

I'm going to release 0.6 since you were suggesting we do it.

#5

Updated by Rogers, Chris over 11 years ago

  • Status changed from Rejected to Open

Well let me re-spec then. I work more quickly when I have a check list of things to do. If it is to do by hand then fine, but it is less buggy if I can work through a release plan.

So:

Try to work up a release plan for this release...

#6

Updated by Tunnell, Christopher over 11 years ago

Let's say 0.7 (preparing for 1.0 release candidate) if that's okay since you asked about putting out antoher dot release.

I did this:

1. Check jenkins that the trunk latest commit and fresh builds work.
2. bzr tag MAUS-v0.X
3. bzr export maus-v0.X.tar.gz
4. Go to files section and upload

Thinking on the fly: do we want to hold back stuff at this step from releases? Somehow add a file called ".COMPONENT_RELEASE_STATUS" which can mean that code doesn't go into the release or something?

#7

Updated by Rogers, Chris over 11 years ago

Okay for alpha release I guess. I wanted to figure out some documentation stuff as well.

#8

Updated by Rogers, Chris over 11 years ago

Also we should be making release notes.

#9

Updated by Tunnell, Christopher over 11 years ago

  • Target version changed from MAUS-v0.0.1 to Future MAUS release
#10

Updated by Tunnell, Christopher over 11 years ago

Another thing for the list: update release notes and changelog.

#11

Updated by Rogers, Chris over 11 years ago

  • Status changed from Open to Closed

Became MAUS-0.0.1

#12

Updated by Tunnell, Christopher over 11 years ago

  • Target version changed from Future MAUS release to MAUS-v0.0.1

Also available in: Atom PDF