[kepler-dev] Where the changes goes for kepler 2.1, Kepler trunk or Kepler 2.0 Branch?

[David Welker]

Hi Jianwu,

Changes for 2.1 should go into the trunk only. The only thing that should go into the 2.0 branch are patches to 2.0. (e.g. 2.0.1, 2.0.2, 2.0.3, .... etc.).

Eventually, we will create a new 2.1 branch from the trunk, but it is a little early at this point. It is better to delay the point where developers have to check in all their changes into two branches, as this increases the probability of error and doubles the amount of testing one must do before committing changes.

Sent from my iPhone

On Aug 2, 2010, at 6:51 PM, Jianwu Wang <jianwu at sdsc.edu> wrote:

> Hi All,
> 
>    I don't think we discussed this issue during our meeting for Kepler 2.1 bugs.  Definitely every changes for Kepler 2.1 should first be checked into Kepler trunk. But since all changes, no matter they are about Kepler 2.1 bug fixing all not, will be checked in Kepler trunk. If we release Kepler 2.1 by freezing Kepler trunk sometime in the future. New bugs may pop up because of other changes.
> 
>    So should we check in changes for Kepler 2.1 bug fixing to Kepler 2.0 branch, so that testing for Kepler 2.1 will be much easier?
> 
> -- 
> 
> Best wishes
> 
> Sincerely yours
> 
> Jianwu Wang
> jianwu at sdsc.edu
> http://users.sdsc.edu/~jianwu/
> 
> Assistant Project Scientist
> Scientific Workflow Automation Technologies (SWAT) Laboratory
> San Diego Supercomputer Center
> University of California, San Diego
> San Diego, CA, U.S.A.
> 
> _______________________________________________
> Kepler-dev mailing list
> Kepler-dev at kepler-project.org
> http://mercury.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-dev