Planning for post release bug fixing

GoogleCodeExporter commented 9 years ago

The following is a proposal for how we maintain releases.

When 1.0 is released we do the following:
     create a tag 1.0
     create a branch 1.0
     bump the trunk up to version 1.1

Development on 1.1 happens in trunk. Code in tag 1.0 is never changed.
Bugs in 1.0 that are reported by users or developers are fixed in branch 1.0 
and in trunk, if relevant. It could be that trunk had moved on so that the bug 
is no longer in the trunk code (functionality may have been dropped or 
refactored for example).

In the event that bug fixes are substantial between 1.0 and the release of 1.1, 
we could do a release out of branch 1.0. This would be tagged as 1.0.1. Since 
it is a tag, code in there never gets changed, but bug fixes in the 1.0.x 
series continue to be made in branch 1.0.

Bug fixes for 1.0 are handled until 2.0 is released (one year). 
We may want to have one developer oversee the bug fix process for a particular 
release. 

So to summarize our major versions two-dot:  1.0, 1.1, 2.0, 2.1, etc. These are 
released every six months at the end of a release cycle. Bug fix releases for a 
major release are three-dot: 2.0.1, 2.0.2, etc,  and are released during a 
release cycle.

Original issue reported on code.google.com by sjsrey on 1 Jul 2010 at 2:35

GoogleCodeExporter commented 9 years ago

for update plan see 
http://groups.google.com/group/pysal-dev/browse_thread/thread/ceb2128c75cac507

Original comment by sjsrey on 29 Jul 2010 at 12:19

GoogleCodeExporter commented 9 years ago

on further thought, i think we should just increment in trunk like numpy 
http://projects.scipy.org/numpy/wiki/MakingReleases

whatever we do we should decide this shortly

Original comment by sjsrey on 31 Jul 2010 at 2:17

Added labels: Priority-High, Milestone-1.1, Maintainability

GoogleCodeExporter commented 9 years ago

Original comment by sjsrey on 7 Jan 2011 at 9:17

Added labels: Milestone-2.0
Removed labels: Milestone-1.1

GoogleCodeExporter commented 9 years ago

Original comment by sjsrey on 26 Jan 2011 at 8:30

Added labels: Milestone-1.2
Removed labels: Milestone-2.0

GoogleCodeExporter commented 9 years ago

No post release bug fixes until 2.0 series.

For now we post bugs on the "Known issues" page for previous versions affected 
by the bug and we fix it in the trunk.

Original comment by sjsrey on 13 Apr 2011 at 11:08

Changed state: Fixed

google-code-export / pysal

Planning for post release bug fixing #106