flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Om <bigosma...@gmail.com>
Subject Re: Finishing the Git migration - READ FIRST
Date Tue, 12 Mar 2013 17:55:58 GMT
On Tue, Mar 12, 2013 at 10:53 AM, Gordon Smith <gosmith@adobe.com> wrote:

> > let us first come to a decision whether we are happy with the new Git
> repos or not.
>
> I looked back through the emails and can't find the URL for the new Git
> repo. Can we inspect it using a browser or do we have to install a Git
> client?
>
>
The links are in the JIRA ticket.  But here they are again - all browsable.


https://git-wip-us.apache.org/repos/asf/flex-falcon.git
https://git-wip-us.apache.org/repos/asf/flex-sdk.git
https://git-wip-us.apache.org/repos/asf/flex-tlf.git
https://git-wip-us.apache.org/repos/asf/flex-utilities.git

Thanks,
Om


> - Gordon
>
> -----Original Message-----
> From: omuppi1@gmail.com [mailto:omuppi1@gmail.com] On Behalf Of Om
> Sent: Tuesday, March 12, 2013 10:49 AM
> To: dev@flex.apache.org
> Subject: Finishing the Git migration - READ FIRST
>
> All,
>
> Before we get into lengthy debates about Git and Git vs. SVN, etc.  we
> need to first finish the migration process so that the new Git repos will
> become Read-Write.  This means that the Flex PMC should first accept the
> new branches and give INFRA a go-ahead.  Here is INFRA's comment on the
> JIRA ticket [1]
>
> "The git repos are also read only. Please have the FLEX PMC look at the
> repos, see if they are acceptable, all branches are present, etc, and if
> found accordingly, please update this ticket and I'll make them writable."
>
> Instead of posting comments and discussing on the JIRA ticket, let us
> first come to a decision whether we are happy with the new Git repos or not.
>
> *Please respond to this thread with details on what repos are missing
> (projects, whiteboards, etc.)  *Once we have a consensus, I will post that
> list on the JIRA ticket.  Once all those Reps are migrated to Git, we can
> give INFRA the go ahead to make them all read-write.
>
> Once that is done, we can apply a fix to the SDK - TLF problem and push it
> to the repo.
>
> To re-iterate, it is a waste of everyone's  energy to keep discussing
> potential fixes to any problem without getting the Git repos to become
> read-write.
>
> Thanks,
> Om
>
> [1] https://issues.apache.org/jira/browse/INFRA-5549
>

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