On Thursday October 16, 2008 05:31:59 Lukasz Szybalski wrote:
Certainly because none of the people who mentionned interest in this
thread wanted to implement a bazaar bazed solution... And because this
discussion originated from the statement that we could host alberto's
things
On Thu, Oct 16, 2008 at 1:19 AM, Gustavo Narea [EMAIL PROTECTED] wrote:
On Thursday October 16, 2008 05:31:59 Lukasz Szybalski wrote:
Certainly because none of the people who mentionned interest in this
thread wanted to implement a bazaar bazed solution... And because this
discussion
On Thu, Oct 16, 2008 at 12:04 PM, Jorge Vargas [EMAIL PROTECTED] wrote:
On Thu, Oct 16, 2008 at 1:19 AM, Gustavo Narea [EMAIL PROTECTED] wrote:
On Thursday October 16, 2008 05:31:59 Lukasz Szybalski wrote:
Certainly because none of the people who mentionned interest in this
thread wanted
On Thu, Oct 16, 2008 at 1:10 PM, Lukasz Szybalski [EMAIL PROTECTED] wrote:
On Thu, Oct 16, 2008 at 12:04 PM, Jorge Vargas [EMAIL PROTECTED] wrote:
On Thu, Oct 16, 2008 at 1:19 AM, Gustavo Narea [EMAIL PROTECTED] wrote:
On Thursday October 16, 2008 05:31:59 Lukasz Szybalski wrote:
On Tue, Oct 14, 2008 at 1:05 AM, Florent Aide [EMAIL PROTECTED] wrote:
On Tue, Oct 14, 2008 at 5:43 AM, Lukasz Szybalski [EMAIL PROTECTED] wrote:
Just out of curiosity, is there a reason why bazaar is not mentioned
in this thread?
http://bazaar-vcs.org/BzrPlugins
Certainly because none
On Tue, Oct 14, 2008 at 5:43 AM, Lukasz Szybalski [EMAIL PROTECTED] wrote:
Just out of curiosity, is there a reason why bazaar is not mentioned
in this thread?
http://bazaar-vcs.org/BzrPlugins
Certainly because none of the people who mentionned interest in this
thread wanted to implement a
Just out of curiosity, is there a reason why bazaar is not mentioned
in this thread?
http://bazaar-vcs.org/BzrPlugins
Thanks,
Lucas
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
TurboGears Trunk group.
To post
On Wed, Sep 3, 2008 at 10:54 AM, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
Does anyone have a migration plan? I mean, a series of commands and
configurations that would be run to migrate our repository?
Not yet. I brought up the question before comming up with a detailed
plan because I
I'm not 100% sure I follow you here. What is your suggestion? I
think it makes sense to maintain a svn repository that has reasonably
current code for several months at least. The question is how often
to merge changes over to that repository, and how fine-grained the
history of that
Em Tuesday 02 September 2008 10:33:13 Florent Aide escreveu:
On 9/2/08, Alberto Valverde [EMAIL PROTECTED] wrote:
Hi,
Sorry for being late to the party, I was on vacations.
I'd also like seeing TG2 switching to mercurial. Most of the pro
arguments have been already mentioned in
Does anyone have a migration plan? I mean, a series of commands and
configurations that would be run to migrate our repository?
Not yet. I brought up the question before comming up with a detailed
plan because I didn't want to waste time on a detailed plan if we
weren't really going to make
Hi,
Sorry for being late to the party, I was on vacations.
I'd also like seeing TG2 switching to mercurial. Most of the pro arguments
have been already mentioned in this thread but I'll briefly repeat those
that I find most valuable:
- Being able to work offline. I know most of us have a good
On 9/2/08, Alberto Valverde [EMAIL PROTECTED] wrote:
Hi,
Sorry for being late to the party, I was on vacations.
I'd also like seeing TG2 switching to mercurial. Most of the pro arguments
have been already mentioned in this thread but I'll briefly repeat those
that I find most
Jorge Vargas, el 28 de agosto a las 17:33 me escribiste:
On Thu, Aug 28, 2008 at 4:48 PM, Jorge Godoy [EMAIL PROTECTED] wrote:
There are great projects out there that still uses CVS and they are doing
very
well.
yes indeed, great code is not determine by the tools around it.
But it
OK, this has been a really good discussion, and I'm excited by all the
interest in making our development process as accessible and easy to
get involved as possible, and I think that lots of good points and
counterpoints have been raised. But, I also think it's time to get
on with the work of
With all that said, I think I'm pretty well convinced that a switch to
mercurial is in our future. My suggestion is that we move trunk,
and projects/tg.devtools' into mercurial first, and that we work on
getting Alberto's setup working on our servers, and see how things go.
If there are
Mark Ramm schrieb:
Disadvantages of switching:
1) TG contributers need to learn a new tool.
2) TG contribution documentation needs to be changed
3) The process could become more confusing and chaotic, if people go
around publishing branches of their own.
Plus:
we either need to
Mark Ramm, el 29 de agosto a las 12:26 me escribiste:
A couple of alternatives to mercurial were suggested. SVK would work
on top of the existing infrastructure and provide some of the same
benifits. But I see a couple of disadvantages here. SVK is harder
to install and maintain, and is
git svn is a great tool for migration/git-svn coexistence. With git svn
you even can keep the svn as the real trunk and do all the branching in
a git repository, completely maintaining backward compatibility for
people using svn. This is great for any migration (specially, users minds
we either need to switch TG2 and TG1.x together* or we need
- two tracs
- two buildbots
- possibly two user management systems
If we want to switch TG 1.x to mercurial we need to change a lot of
things in the build process.
Good point.
My thought was that we would need to be running two
I don't mind the switch - all I'd like to see is that it is done *after* a
first TG2 release has been done. I (and I don't doubt many others) have
SVN-based installations. I can constantly update, and provide patches if
needed.
Yea, it makes sense to me to do this post 1.9.7 final, or at
Mark Ramm schrieb:
On the other hand, if we have a totally different project infrastructure
for TG2 and TG 1.x, it might become more difficult to share efforts.
Possibly, though I think that we should be keeping tg1 and tg2 tickets
seprate anyway, and code rarely flows back and forth
On Fri, Aug 29, 2008 at 4:13 PM, Christopher Arndt [EMAIL PROTECTED] wrote:
Mark Ramm schrieb:
On the other hand, if we have a totally different project infrastructure
for TG2 and TG 1.x, it might become more difficult to share efforts.
Possibly, though I think that we should be keeping tg1
Hi,
This discussion sounds a little like RHEL (TG1) and Fedora (TG2).
Suggest you keep the existing TG1.x infrastructure on SVN. Split TG2
trac and repo out.
Perhaps setup trac1.turbo... and trac2.turbo... for the different
versions? trac.turbo... just points to trac1.turbo...
Allows the
Em Thursday 28 August 2008 02:50:06 Jorge Vargas escreveu:
All 4 of Mark's original ideas are valid, plus offline commits as
several others have suggested, plus the ideas I posted that you didn't
reject, plus the ones where I think your objections are not valid :)
I am not rejecting anything.
On Thu, Aug 28, 2008 at 4:48 PM, Jorge Godoy [EMAIL PROTECTED] wrote:
Em Thursday 28 August 2008 02:50:06 Jorge Vargas escreveu:
All 4 of Mark's original ideas are valid, plus offline commits as
several others have suggested, plus the ideas I posted that you didn't
reject, plus the ones
Em Friday 22 August 2008 04:16:53 Jorge Vargas escreveu:
- branches, especially private ones, are awesome. For example I run my
own webhelpers private branch for one of my GAE projects, I got full
rev history, I can commit whatever I want, everything works. If some
of that code needs to move
On Wed, Aug 27, 2008 at 9:32 PM, Jorge Godoy [EMAIL PROTECTED] wrote:
I have the same question that I posted on the other list: What will changing
the main repository from on VCS to another gives us? I haven't seen anything
that can't be obtained today.
It allows people without commit access
On Wed, Aug 27, 2008 at 10:32 PM, Jorge Godoy [EMAIL PROTECTED] wrote:
Em Friday 22 August 2008 04:16:53 Jorge Vargas escreveu:
- branches, especially private ones, are awesome. For example I run my
own webhelpers private branch for one of my GAE projects, I got full
rev history, I can
On Tue, Aug 19, 2008 at 8:05 PM, Jorge Godoy [EMAIL PROTECTED] wrote:
Em Tuesday 19 August 2008 12:50:57 percious escreveu:
I think SVN does not work well in the mode of development that
benefits TG2 the most: the sprint. Many of our sprints are held in
pods across the world. With a
On Tue, Aug 19, 2008 at 7:12 AM, Mark Ramm [EMAIL PROTECTED] wrote:
We have a new server for TurboGears.org, and Alberto asked if we could
host ToscaWidgets.org there as well.
This seemed like a good idea to everybody responsible to the server,
but I raised the idea of switching TG2 to
I am +1 for hg. I've been using it for my private projects for a
while now and I've ditched SVN for it for as many projects as I could.
It's faster than SVN for almost everything and doesn't require
internet access for those times when you want to code while traveling.
On a subjective note, it
Hello,
On Tuesday 19 August 2008 15:12:54 Mark Ramm wrote:
1) Alberto's got a neat setup on the toscawidgets site, where
mercurial, trac, and everything are all part of a single system with a
single username/password.
You can do that with SVN and Trac too, by sharing the same Htpasswd
Am Dienstag, den 19.08.2008, 09:12 -0400 schrieb Mark Ramm:
We have a new server for TurboGears.org, and Alberto asked if we could
host ToscaWidgets.org there as well.
This seemed like a good idea to everybody responsible to the server,
but I raised the idea of switching TG2 to mercurial in
This seemed like a good idea to everybody responsible to the server,
but I raised the idea of switching TG2 to mercurial in a private
e-mail to the parties involved.
Obviously this is something that we should all talk about on the
mailing list before we even think seriously about making a
Others use SVN. As do many projects that use TG and for example use
svn:externals.
Hmm, are there a lot of TG users who are using svn:externals to pull
TG in their own SVN setup?
I have not seen people doing this, but that doesn't mean it's not happening.
--Mark Ramm
On Tuesday 19 August 2008 17:17:57 Mark Ramm wrote:
Others use SVN. As do many projects that use TG and for example use
svn:externals.
Hmm, are there a lot of TG users who are using svn:externals to pull
TG in their own SVN setup?
I have not seen people doing this, but that doesn't mean
On Tue, Aug 19, 2008 at 11:32 AM, Diez B. Roggisch [EMAIL PROTECTED] wrote:
On Tuesday 19 August 2008 17:17:57 Mark Ramm wrote:
Others use SVN. As do many projects that use TG and for example use
svn:externals.
Hmm, are there a lot of TG users who are using svn:externals to pull
TG
With the advent of indicies (basketweaver, eggbasket, etc) I dont
really see a need for people to do a svn:externals for their own
projects. Simply check the trunk out and make your own egg and egg
basket. This is a formidable way of doing distribution of the trunk
code, because it freezes
.as HG has been getting some bad press in the recent future.
Sounds like you've got a time machine.
Should I sell or buy? :)
Just kidding,
Daniel
--
Psss, psss, put it down! - http://www.cafepress.com/putitdown
--~--~-~--~~~---~--~~
You received this
On Tue, Aug 19, 2008 at 8:12 AM, Mark Ramm [EMAIL PROTECTED]wrote:
We have a new server for TurboGears.org, and Alberto asked if we could
host ToscaWidgets.org there as well.
This seemed like a good idea to everybody responsible to the server,
but I raised the idea of switching TG2 to
Em Tuesday 19 August 2008 12:50:57 percious escreveu:
I think SVN does not work well in the mode of development that
benefits TG2 the most: the sprint. Many of our sprints are held in
pods across the world. With a mecurial, git, or bzr repo, we can
have these pods committing locally to a
Em Tuesday 19 August 2008 22:34:34 [EMAIL PROTECTED] escreveu:
Besides, with HG web interface, people could get current
snapshot.tgz/.zip without check out the source repository.
It allows new developers to try the source without commitment, or
figure out how to check out the source code.
43 matches
Mail list logo
