You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@airavata.apache.org by Chathura Herath <ch...@cs.indiana.edu> on 2011/12/21 15:36:20 UTC
Branching to "stable"
Hi Devs,
I have branched the trunk to branch/stable. Please continue to work on
any fixes you may run into i will merge them before we tag it to the
0.2.
--
Chathura Herath
http://people.apache.org/~chathura/
http://chathurah.blogspot.com/
Re: Branching to "stable"
Posted by Heshan Suriyaarachchi <he...@gmail.com>.
On Wed, Dec 21, 2011 at 9:36 AM, Chathura Herath <ch...@cs.indiana.edu>wrote:
> Hi Devs,
>
> I have branched the trunk to branch/stable. Please continue to work on
> any fixes you may run into i will merge them before we tag it to the
> 0.2.
>
Ok.
>
>
> --
> Chathura Herath
> http://people.apache.org/~chathura/
> http://chathurah.blogspot.com/
>
--
Regards,
Heshan Suriyaarachchi
http://heshans.blogspot.com/
Re: Branching to "stable"
Posted by Suresh Marru <sm...@cs.indiana.edu>.
OOPS sorry I was confused then. I was under the impression that was RC branch, this makes sense to me know.
+ 1 for the branch and this process.
Suresh
On Dec 21, 2011, at 1:03 PM, Chathura Herath wrote:
> To be in accordance with release guidelines the release candidate
> should be called version-incubating-SNAPSHOT. "Stable" is the branch
> we use to test so people can test while bugs are getting fixed, i
> didnt invent this. Probably at the end of the day testing will move to
> the branch which will be the release candidate. So i see no violation
> of the process as is, unless you could point me to a document that
> says otherwise.
>
> This is in accordance with release management for svn written by our
> old friend Leo (http://lsimons.wordpress.com/2010/02/19/using-long-lived-stable-branches/)
> which is the advised svn management strategy endorsed by the
> (http://incubator.apache.org/guides/releasemanagement.html#guidelines.
> )
>
> I am not at the point where i can call a release candidate, still in
> the testing phase. We can name it accordingly when we call for release
> candidate and the vote.
>
> Thanks
> Chathura
>
> On Wed, Dec 21, 2011 at 12:24 PM, Suresh Marru <sm...@cs.indiana.edu> wrote:
>> Hi Chathura,
>>
>> Please revert this branch, lets follow the following version semantics.
>>
>> Here is the normal process how the release plugging works:
>> *We include apache pom as the parent - http://svn.apache.org/repos/asf/maven/pom/trunk/maven/pom.xml
>> *Always trunk should be having next version and -incubating-snapshot suffix, so the current trunk should be 0.2-incubating-SNAPSHOT
>> *The release preparation among other things will automatically do the following to tags and versions:
>> **Tag the trunk to airavata-0.2-incubating
>> ** stage the jars and source to nexus repository staging area
>> **after the release steps are complete, it will automatically bump the trunk to 0.3-incubating-SNAPSHOT
>>
>> So the following corrections are required:
>> 1) Delete the currently created "stable" branch
>> 2) branch the trunk to "0.2-incubating-SNAPSHOT" so the release goals will work.
>> 3) do not worry about trunk pom's and continue working on the code
>> 4) if release steps are followed the branch will be tagged and branch version will be bumped to 0.3-incubating-SNAPSHOT
>> 5) After release is successful, merge any code and pom's (to make the trunk back to 0.3-incubating-SNAPSHOT).
>>
>> Suresh
>>
>>
>> On Dec 21, 2011, at 9:36 AM, Chathura Herath wrote:
>>
>>> Hi Devs,
>>>
>>> I have branched the trunk to branch/stable. Please continue to work on
>>> any fixes you may run into i will merge them before we tag it to the
>>> 0.2.
>>>
>>>
>>> --
>>> Chathura Herath
>>> http://people.apache.org/~chathura/
>>> http://chathurah.blogspot.com/
>>
>>
>> -----BEGIN PGP SIGNATURE-----
>>
>> iQIcBAEBAgAGBQJO8hY1AAoJEHmz9P1hfdutQCEP/RsZY6e28IGJgF2vcMqA67PL
>> WCyc9mNupqT9zYhOVX7NkNU6bPA8LKW5NEJZ+cEoulVX5FZZy5awfBWPjfrJo/IP
>> pgX5aCSd1shE61Ts+YMCS8uI6DF78klbPRuyPklTc0z9PrnN7S7GWuBx+o7cOFHs
>> zNp7JydTkc0vfYxnNG1v2yAZ2LYZ31eDZlYPM+xT9OystSbb4QwDAK/YDymZI7CP
>> KcRRrGwlnWre3aYs3HbiNhcPmVFFSBeSQq3sa/YLBD/yK0jNkp5zUCK/LKhoXLI9
>> /jPdMWOSmu/wLMxhAyi2vliNnqkvxlWrwi5xzuSj8obmsBMgYeLtHSIeQfxYC3rr
>> KwtW2RNkhCKQAU376WGp6uvhHdypkzu4my+4YRHlGG9hJLpcn+ZEaE1CMCYWTnp9
>> vhmFMr1JQxDAJDpz4t0aL5HeXeyqr+nUSoPRX6lYt5AAKXWLryB+bhhwYHgV2UN4
>> dCB1N0+Gui0oRQvIHGms7swnDfLTJ1k5krPQ61PLOPDn3H8y00HEVtD4uec49lvF
>> 38U2N9AMADiw82EnRxB9p/JNjVUNOQ/ywLVe3BFjtphY2f5+2NOMqYSRCK9SxQ+q
>> eSGfdUlC91aDZHD4junyW9gLcNgIWaRIsXPLLV/isHWSZ9OTKZw1cxuX8b3L/MHA
>> ktHfr5SJyLqh9I4k1uOO
>> =UlYY
>> -----END PGP SIGNATURE-----
>>
>
>
>
> --
> Chathura Herath
> http://people.apache.org/~chathura/
> http://chathurah.blogspot.com/
Re: Branching to "stable"
Posted by Chathura Herath <ch...@cs.indiana.edu>.
To be in accordance with release guidelines the release candidate
should be called version-incubating-SNAPSHOT. "Stable" is the branch
we use to test so people can test while bugs are getting fixed, i
didnt invent this. Probably at the end of the day testing will move to
the branch which will be the release candidate. So i see no violation
of the process as is, unless you could point me to a document that
says otherwise.
This is in accordance with release management for svn written by our
old friend Leo (http://lsimons.wordpress.com/2010/02/19/using-long-lived-stable-branches/)
which is the advised svn management strategy endorsed by the
(http://incubator.apache.org/guides/releasemanagement.html#guidelines.
)
I am not at the point where i can call a release candidate, still in
the testing phase. We can name it accordingly when we call for release
candidate and the vote.
Thanks
Chathura
On Wed, Dec 21, 2011 at 12:24 PM, Suresh Marru <sm...@cs.indiana.edu> wrote:
> Hi Chathura,
>
> Please revert this branch, lets follow the following version semantics.
>
> Here is the normal process how the release plugging works:
> *We include apache pom as the parent - http://svn.apache.org/repos/asf/maven/pom/trunk/maven/pom.xml
> *Always trunk should be having next version and -incubating-snapshot suffix, so the current trunk should be 0.2-incubating-SNAPSHOT
> *The release preparation among other things will automatically do the following to tags and versions:
> **Tag the trunk to airavata-0.2-incubating
> ** stage the jars and source to nexus repository staging area
> **after the release steps are complete, it will automatically bump the trunk to 0.3-incubating-SNAPSHOT
>
> So the following corrections are required:
> 1) Delete the currently created "stable" branch
> 2) branch the trunk to "0.2-incubating-SNAPSHOT" so the release goals will work.
> 3) do not worry about trunk pom's and continue working on the code
> 4) if release steps are followed the branch will be tagged and branch version will be bumped to 0.3-incubating-SNAPSHOT
> 5) After release is successful, merge any code and pom's (to make the trunk back to 0.3-incubating-SNAPSHOT).
>
> Suresh
>
>
> On Dec 21, 2011, at 9:36 AM, Chathura Herath wrote:
>
>> Hi Devs,
>>
>> I have branched the trunk to branch/stable. Please continue to work on
>> any fixes you may run into i will merge them before we tag it to the
>> 0.2.
>>
>>
>> --
>> Chathura Herath
>> http://people.apache.org/~chathura/
>> http://chathurah.blogspot.com/
>
>
> -----BEGIN PGP SIGNATURE-----
>
> iQIcBAEBAgAGBQJO8hY1AAoJEHmz9P1hfdutQCEP/RsZY6e28IGJgF2vcMqA67PL
> WCyc9mNupqT9zYhOVX7NkNU6bPA8LKW5NEJZ+cEoulVX5FZZy5awfBWPjfrJo/IP
> pgX5aCSd1shE61Ts+YMCS8uI6DF78klbPRuyPklTc0z9PrnN7S7GWuBx+o7cOFHs
> zNp7JydTkc0vfYxnNG1v2yAZ2LYZ31eDZlYPM+xT9OystSbb4QwDAK/YDymZI7CP
> KcRRrGwlnWre3aYs3HbiNhcPmVFFSBeSQq3sa/YLBD/yK0jNkp5zUCK/LKhoXLI9
> /jPdMWOSmu/wLMxhAyi2vliNnqkvxlWrwi5xzuSj8obmsBMgYeLtHSIeQfxYC3rr
> KwtW2RNkhCKQAU376WGp6uvhHdypkzu4my+4YRHlGG9hJLpcn+ZEaE1CMCYWTnp9
> vhmFMr1JQxDAJDpz4t0aL5HeXeyqr+nUSoPRX6lYt5AAKXWLryB+bhhwYHgV2UN4
> dCB1N0+Gui0oRQvIHGms7swnDfLTJ1k5krPQ61PLOPDn3H8y00HEVtD4uec49lvF
> 38U2N9AMADiw82EnRxB9p/JNjVUNOQ/ywLVe3BFjtphY2f5+2NOMqYSRCK9SxQ+q
> eSGfdUlC91aDZHD4junyW9gLcNgIWaRIsXPLLV/isHWSZ9OTKZw1cxuX8b3L/MHA
> ktHfr5SJyLqh9I4k1uOO
> =UlYY
> -----END PGP SIGNATURE-----
>
--
Chathura Herath
http://people.apache.org/~chathura/
http://chathurah.blogspot.com/
Re: Branching to "stable"
Posted by Suresh Marru <sm...@cs.indiana.edu>.
Hi Chathura,
Please revert this branch, lets follow the following version semantics.
Here is the normal process how the release plugging works:
*We include apache pom as the parent - http://svn.apache.org/repos/asf/maven/pom/trunk/maven/pom.xml
*Always trunk should be having next version and -incubating-snapshot suffix, so the current trunk should be 0.2-incubating-SNAPSHOT
*The release preparation among other things will automatically do the following to tags and versions:
**Tag the trunk to airavata-0.2-incubating
** stage the jars and source to nexus repository staging area
**after the release steps are complete, it will automatically bump the trunk to 0.3-incubating-SNAPSHOT
So the following corrections are required:
1) Delete the currently created "stable" branch
2) branch the trunk to "0.2-incubating-SNAPSHOT" so the release goals will work.
3) do not worry about trunk pom's and continue working on the code
4) if release steps are followed the branch will be tagged and branch version will be bumped to 0.3-incubating-SNAPSHOT
5) After release is successful, merge any code and pom's (to make the trunk back to 0.3-incubating-SNAPSHOT).
Suresh
On Dec 21, 2011, at 9:36 AM, Chathura Herath wrote:
> Hi Devs,
>
> I have branched the trunk to branch/stable. Please continue to work on
> any fixes you may run into i will merge them before we tag it to the
> 0.2.
>
>
> --
> Chathura Herath
> http://people.apache.org/~chathura/
> http://chathurah.blogspot.com/