ReleaseS

TWiki> LibrePlan Web>ReleaseS (29 Apr 2013, ManuelRego)EditAttach

Releases

• LibrePlan
• CutyCapt
• Release Process (deprecated)
  • Description
    • Release Tasks
      • Mandatory
    • Ideally

LibrePlan

Version

Date

Release notes

Announcement

1.4

1.4.0

2013/04/29

 

1.3

1.3.3

2012/12/21

1.3.2

2012/11/30

1.3.1

2012/10/15

1.3.0

2012/07/26

 

1.2

1.2.4

2012/05/23

1.2.3

2012/04/19

1.2.2

2012/03/15

1.2.1

2012/01/19

1.2.0

2011/12/01

 

1.1

1.1.3

2011/08/12

1.1.2

2011/07/18

1.1.1

2011/06/07

1.1.0

2011/05/19

 

1.0

1.0.6

2011/04/27

1.0.5

2011/04/08

1.0.4

2011/03/17

1.0.3

2011/02/16

1.0.2

2011/01/21

1.0.1

2011/01/14

1.0.0

2011/01/07

CutyCapt

Version

Date

Distribution

Architecture

Download

20110107

2011/01/07

Ubuntu Maverick 10.10

i386

cutycapt_20110107-1.maverick_i386.deb

Ubuntu Maverick 10.10

amd64

cutycapt_20110107-1.maverick_amd64.deb

Ubuntu Lucid 10.04

i386

cutycapt_20110107-1.lucid_i386.deb

Ubuntu Lucid 10.04

amd64

cutycapt_20110107-1.lucid_amd64.deb

Debian 6 Squeeze

i386

cutycapt_20110107-1.squeeze_i386.deb

Debian 6 Squeeze

amd64

cutycapt_20110107-1.squeeze_amd64.deb

Release Process (deprecated)

Description

LibrePlan release process consists in periods of 3 months divided in 2 phases:

• Development: 10 weeks
• Testing: 2 weeks

Bugfixing is always being done so it is part of both phases Development and Testing. When Development phase finishes no more features (freeze) would be added for the upcoming version.

That means that each 3 months users will have available a fresh stable version of LibrePlan. Anyway, we will do minor releases which fix bugs over the stable version when some critical issue appears or a good amount of bugs are fixed.

The week after each major release LibrePlan community will join in the IRC room (#navalplan) to discuss about features for the next version and update the RoadMap. This is a good moment to request new features for the project.

Release Tasks

Mandatory

• Prepare and test Debian package.
• Update translations.
• Update NEWS and TODO files.
• Upload new packages to SourceForge.net.
• Upload new packages to Launchpad.
• Announce release:
  • Piece of news at website, SourceForge.net, freecode.net and Facebook.
  • Tweet about new version.
  • Mail to project mailing lists.
• Upgrade demo.
• Coordination meeting to debate the RoadMap for next versions.

Ideally

• Update documentation.
• Update help.
• Update screenshots.

Copyright (c) by the contributing authors. All material on this collaboration platform is the property of the contributing authors.