any23-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Lewis John Mcgibbney <lewis.mcgibb...@gmail.com>
Subject Re: dev Digest 3 Mar 2013 11:13:43 -0000 Issue 224
Date Mon, 04 Mar 2013 00:17:08 GMT
Hi Peter,
On Sun, Mar 3, 2013 at 3:13 AM, <dev-digest-help@any23.apache.org> wrote:

> It looks good to me.
>
> From what I have read the GitHub any23 mirror
> https://github.com/apache/any23 should still work transparently
> through the read-only git://git.apache.org/any23.git repository, which
> will be the same repository as
> https://git-wip-us.apache.org/repos/asf/any23.git . However, to write
> to the repository we will need to use
> https://git-wip-us.apache.org/repos/asf/any23.git (after it is enabled
> for writing).
>
> In terms of branching strategies in Git, I would like if branches are
> created per issue (or per group of similar issues) and named starting
> with the main issue number for the branch. For example, ANY23-101. We
> may end up also having ANY23-101-part2 or ANY23-101-strategy2, if
> there ends up being more than one branch for an issue. I don't mind
> having branches located physically in different repositories,
> including GitHub repositories, and linked to from Jira issues, but we
> have run into issues discussing this strategy (which works fine for
> the rest of the open source world) in the past so it could also work
> if we have a policy that the branch be pushed directly to
> https://git-wip-us.apache.org/repos/asf/any23.git when it is ready for
> draft or final peer review, and links from Jira go to that branch.
> Personally, I think it would work well if people who do not have write
> access to https://git-wip-us.apache.org/repos/asf/any23.git fork the
> repository on GitHub and link to their branches from Jira issues, but
> the perceived legal difficulties with that strategy are above my head.
>
> Pete r


It would greatly appreciated if you can lead the conversation over on the
INFRA Jira issue and we can begin working on familiarizing ourselves with
the Git writable repos.
Thank you
Lewis

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message