Hi,
> Did you already open up a ticket with infra to get that looked at?
No but I have now:
https://issues.apache.org/jira/browse/INFRA-5708
Thanks,
Justin
Justin,
Did you already open up a ticket with infra to get that looked at?
-Nick
On Thu, Dec 27, 2012 at 8:09 PM, Justin Mclean wrote:
> Hi,
>
> Still to do:
> 1. Place release in correct location ie /dist not /dist/incubation (OK
> for now I think)
> 2. Official announcement to various lists
Yea you're right. :) I'm not sure what I was thinking. So yea we do have to
wait to merge to be able to get passed the merge issue to then tag trunk.
-omar
On Thursday, December 27, 2012, Justin Mclean wrote:
> Hi,
>
> > You can see the diagram for the nvie model here:
> > http://nvie.com/posts/
Hi,
> You can see the diagram for the nvie model here:
> http://nvie.com/posts/a-successful-git-branching-model/
Yep and you can see master being tagged which is same as our trunk.
Justin
Hi,
> Make a tag from the release branch, not the develop branch.
Only issue here is that branch may be be around as long as the trunk or
develop. Trunk is what's supports to contains the last stable release so make
more sense for it to be tagged. (IMO)
But yep get the point re not tagging dev
Make a tag from the release branch, not the develop branch. Develop branch
could have changes that were made while the release was being prepared.
After merging the release to develop it could be different than what is
being released from the release branch. You can see the diagram for the
nvie mod