Mainly to release 1.6 and 1.5 (pre-asf) releases, unless it is appropriate to do so from ASF repos...
On Monday, May 6, 2013, David Nalley wrote: > On Mon, May 6, 2013 at 12:46 PM, Adrian Cole > <[email protected]<javascript:;>> > wrote: > > Hi, team. > > > > Folks have expressed interest in continuing use of github for the purpose > > of review. I've discussed a plan for how we can transition and figured > it > > best to repost it here. The idea is to have a place for legacy code > > updates to occur from until the end of the year, and make space for the > > next line of collaboration. > > > > Current status: > > > > jclouds on github is an account controlled only by me. This includes the > > repositories being imported into the ASF prefixed with incubator- > > > > Ideal status (subject to debate): > > > > jclouds on github is an org with representative members correlating to > the > > PPMC. It contains forked repositories from the authoritative sources in > > apache. > > jclouds-legacy on github is an org with representative members > correlating > > to the PPMC. Its repositories are the old ones, which were transferred > to > > it. These repositories and the account are marked as deprecated. > > > > I've already provisioned the org jclouds-legacy, and migrating repos to > it > > is pretty trivial. Converting the existing jclouds account to an org is > > very easy. In other words, this process from a technical POV is stupidly > > simple. > > > > This all in mind, let's chat about any blocking concerns. If there > aren't > > any, we should start the process so that we can start using github as a > > collaboration point for code updates into the ASF. > > > > you're on! > > So what's the point of jclouds-legacy? > The history is complete in the ASF repos, and would be complete in > github mirrors of the ASF repos, so I am not sure I understanding the > reasoning by creating another gh org. > > --David >
