Google Code shutting down

gaekwad · 2015-03-12 16:27:17

google-opensource.blogspot.com/2015/03/farewell-to-google-code.html

Includes timeline, links to download stuff and other background info.

philwareham · 2015-03-12 18:26:31

You could see that coming a mile off.

It might be pertinent to move the old Textpattern 4.5 branch off Google Code though, since there _may_be some more development in that branch at some point.

gaekwad · 2015-03-12 19:18:58

philwareham wrote #288983:

You could see that coming a mile off.

I’m just glad the Textpattern to GitHub transition took place last year, frankly.

wet · 2015-03-13 05:25:31

philwareham wrote #288983:

It might be pertinent to move the old Textpattern 4.5 branch off Google Code though, since there _may_be some more development in that branch at some point.

We should definitely keep a working repo around.

This would need to take its dependency on SVN revision numbers for diagnostics and checksums into account. Any suggestions? Option #1: I can provide SVN hosting and authorized commit access.

gaekwad · 2015-03-13 06:44:20

wet wrote #288988:

Option #1: I can provide SVN hosting and authorized commit access.

I’ll pledge €30 toward this.

wet · 2015-03-13 06:47:22

gaekwad wrote #288991:

I’ll pledge €30 toward this.

No thanks. It’d be on me.

philwareham · 2015-03-13 09:09:24

wet wrote #288988:

Option #1: I can provide SVN hosting and authorized commit access.

I guess the other option would be to pull it into GitHub – but that might be confusing with the 4.6 master already on there. Google have provided a Google Code to GitHub migration tool (which would have been handy 6 months ago, but hey).

Bloke · 2015-03-13 09:30:34

The Google Code to GitHub migration tool FAQ states:

Projects will be migrated to GitHub creating a repo with the same name as the Google Code project. It is not possible to specify a different name for the GitHub repo.

So even if the checksum dependency was resolved somehow, I guess that’s not a viable option.

This is just one more reason for us to knuckle down and get a 4.6.0 release ready. Now where did I put my time creator plugin…

gaekwad · 2015-03-13 09:43:07

Bloke wrote #288998:

Now where did I put my time creator plugin…

I’ll pledge £30 toward this.

philwareham · 2015-03-13 09:44:33

Bloke wrote #288998:

This is just one more reason for us to knuckle down and get a 4.6.0 release ready. Now where did I put my time creator plugin…

When you create that plugin, send me a copy :) – I’ve got so much to do to get Textpattern 4.6 ready. I will eventually, though.

Textpattern CMS

Textpattern CMS support forum

#1 2015-03-12 16:27:17