Repository Combining Idea

[Michael Pedersen]

I have been very inactive, and I'm working on being able to change that. It's just been quite slow.

Despite that, I do have an idea I'd like to propose: We have three repositories for all of TG. I'd like to merge them into just one. It would make release management much easier to do.

Does anybody have issues with this? Is it a bad idea, or one whose time has come? What do you all think?

--
Michael J. Pedersen

My Online Resume: http://www.icelus.org/ -- Google+ http://plus.ly/pedersen

Google Talk: m.ped...@icelus.org -- Twitter: pedersentg

[Christoph Zwerschke]

Am 19.04.2013 03:46, schrieb Michael Pedersen:
> Despite that, I do have an idea I'd like to propose: We have three
> repositories for all of TG. I'd like to merge them into just one. It
> would make release management much easier to do.
>
> Does anybody have issues with this? Is it a bad idea, or one whose
> time has come? What do you all think?

The docs repository is an order of magnitude larger, and if docs would
really be maintained as desirable, they would be even larger. So it
makes some sense that they are separate. Makes cloning and searching in
the code repositories much faster. I'm fine with the separate
repositories, and if documented properly, it's not confusing.

-- Christoph

[Alessandro Molina]

I see some advantages in merging TurboGears and tg.devtools repositories, but I agree that the docs should probably be a separate repository.

As I would like to permanently keep the doc on rtfd.org, having the docs separated wouldn't actually cause any bad to the release management process. It should be something rtfd takes care of for us.

[Mengu]

+1 to that.

On Apr 19, 11:11 am, Alessandro Molina <alessandro.mol...@gmail.com>
wrote:

[Michael Pedersen]

Okay, merging the devtools and tg2 repo would be very desirable at least. Leaving the docs separate, and on rtfd.org, means that the release process needs to change, but then again, that already needed to happen with any merge.

One consideration I'd like to toss in before I agree with the "merge tg2 and tg2devtools but not tg2docs": Every repo gets tagged when a release is made. A big reason for the merge is to reduce the number of tags that has to be done, and thereby reduce errors.

Is everybody okay with simply not having tags in the tg2docs repository?

--
You received this message because you are subscribed to the Google Groups "TurboGears Trunk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to turbogears-tru...@googlegroups.com.
To post to this group, send email to turbogea...@googlegroups.com.
Visit this group at http://groups.google.com/group/turbogears-trunk?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Jorge Vargas]

Hello 

So yea me here back from the death here.

The original intent of having a separate repository (package actually) was that you could have a runnable version of the code (tg) while having an extensions and all the things to develop tg (tg.devtools) in a separate package. In a nutshell the idea was to keep a core for TG thin with just what was needed to run it in production.

Not giving an opinion here just a fact that may have been forgotten.

[Christoph Zwerschke]

Am 25.04.2013 04:46, schrieb Michael Pedersen:
> Is everybody okay with simply not having tags in the tg2docs repository?

But doesn't rtfd.org create the various versions of the docs based on
tags in the repository?

-- Chris

[Michael Pedersen]

Note that I did not say to combine the packages. The packages serve their own distinct purpose, and should be kept separate. I'm arguing for putting the two repositories together to reduce release issues.

[Michael Pedersen]

If it does, then why not combine everything down into one repository? As for size, we'd be creating a single repository that's about 24M to download/clone/search. For point of reference, the actual repository for tg2 is 7.1M, tg2devtools is 3.1M, and tg2docs is 13.6M (according to a du I just did on them).

The additional size is not excessive, searching is not going to be appreciably longer, and releases/tags will be simpler to manage. Everything for tg2 will be under one umbrella. I'm really failing to see an issue with this.

--
You received this message because you are subscribed to the Google Groups "TurboGears Trunk" group.

To unsubscribe from this group and stop receiving emails from it, send an email to turbogears-trunk+unsubscribe@googlegroups.com.
To post to this group, send email to turbogears-trunk@googlegroups.com.

Visit this group at http://groups.google.com/group/turbogears-trunk?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Alessandro Molina]

Yep,

we need to keep tags in doc repository because otherwise you would lose the ability to have previous versions documentation. 

[Christoph Zwerschke]

Am 25.04.2013 18:52, schrieb Michael Pedersen:
> If it does, then why not combine everything down into one repository? As
> for size, we'd be creating a single repository that's about 24M to
> download/clone/search. For point of reference, the actual repository for
> tg2 is 7.1M, tg2devtools is 3.1M, and tg2docs is 13.6M (according to a
> du I just did on them).
>
> The additional size is not excessive, searching is not going to be
> appreciably longer, and releases/tags will be simpler to manage.
> Everything for tg2 will be under one umbrella. I'm really failing to see
> an issue with this.

I get different numbers:

On disc: 4MB for tg, 2MB for tgdev, 39MB for tgdocs,
Via network: 2.5MB for tg, 0.8MB for tgdev, 10.5MB for tgdocs

That's a large overhead when the docs are always included. Also, if
somebody wants to add complete zipped tutorials with source code, images
or even screencasts and videos to the docs (we had these in the tg1
docs), then they will grow even larger. Concerning tgdev, if we add
larger front-end frameworks with JavaScript libraries and themes as
optional quickstart templates, and these are regularly updated, it may
become larger as well.

Some workflows for deploying or testing require cloning the tg
repository which will then take time over slow networks. For instance,
our travis build clones the repo after every push to the repo.

-- Christoph