Repository layouts

(very similar to what I proposed on the DBIC list but as a
lazy svn admin
and cat herder I'd like to see both projects using the same
layout 

It's time for a repo re-org again - -current got detached
from trunk
and we're starting to get confused again, plus 5.80 is
getting delayed by
lack of repo setup

Here's the basic proposal -

Catalyst-Runtime/5.70/trunk # current trunk
Catalyst-Runtime/5.70/branches/* # probably empty
Catalyst-Runtime/5.80/trunk # new -current equivalent
Catalyst-Runtime/5.80branches/* # equivalent of
branches/Catalyst-Runtime/ now

Catalyst-Runtime/tags # tags. shockingly.

The idea of doing it this way is that (1) main point for a
given series is
always called 'trunk' so people don't get confused, (2)
we're always svk
cp-ing down so pulling a 5.70 bugfix to 5.80 is a 'pull' but
once we go to
5.90 it's -still- a pull, something the svn book
branches/5.70 etc. layout
doesn't handle (fine for them but we've got a better merging
tool so let's
use the damn thing).

Thoughts, people?

-- 
      Matt S Trout       Need help with your Catalyst or
DBIx::Class project?
   Technical Director    Want a managed development or
deployment platform?
 Shadowcat Systems Ltd.  Contact mst (at)
shadowcatsystems.co.uk for a quote
http://chainsawblues.vo
x.com/             http://www.shadowc
atsystems.co.uk/ 

_______________________________________________
Catalyst-dev mailing list
Catalyst-devlists.rawmode.org
http://lists.rawmode.org/mailman/listinfo/catalyst-dev

07:59 <kd> mst: seems sane to me
08:00 <mst> kd: upvote on list then.
08:00 <mst> I want to have a clear majority of "yes,
cool" if I'm gonna do this

On 29/06/07, Matt S Trout <dbix-classtrout.me.uk> wrote:
> (very similar to what I proposed on the DBIC list but
as a lazy svn admin
> and cat herder I'd like to see both projects using the
same layout 
>
> It's time for a repo re-org again - -current got
detached from trunk
> and we're starting to get confused again, plus 5.80 is
getting delayed by
> lack of repo setup
>
> Here's the basic proposal -
>
> Catalyst-Runtime/5.70/trunk # current trunk
> Catalyst-Runtime/5.70/branches/* # probably empty
> Catalyst-Runtime/5.80/trunk # new -current equivalent
> Catalyst-Runtime/5.80branches/* # equivalent of
branches/Catalyst-Runtime/ now
>
> Catalyst-Runtime/tags # tags. shockingly.
>
> The idea of doing it this way is that (1) main point
for a given series is
> always called 'trunk' so people don't get confused, (2)
we're always svk
> cp-ing down so pulling a 5.70 bugfix to 5.80 is a
'pull' but once we go to
> 5.90 it's -still- a pull, something the svn book
branches/5.70 etc. layout
> doesn't handle (fine for them but we've got a better
merging tool so let's
> use the damn thing).
>
> Thoughts, people?
>
> --
>       Matt S Trout       Need help with your Catalyst
or DBIx::Class project?
>    Technical Director    Want a managed development or
deployment platform?
>  Shadowcat Systems Ltd.  Contact mst (at)
shadowcatsystems.co.uk for a quote
> http://chainsawblues.vo
x.com/             http://www.shadowc
atsystems.co.uk/
>
> _______________________________________________
> Catalyst-dev mailing list
> Catalyst-devlists.rawmode.org
> http://lists.rawmode.org/mailman/listinfo/catalyst-dev

>

_______________________________________________
Catalyst-dev mailing list
Catalyst-devlists.rawmode.org
http://lists.rawmode.org/mailman/listinfo/catalyst-dev

On Jun 29, 2007, at 1:40 AM, Matt S Trout wrote:

> (very similar to what I proposed on the DBIC list but
as a lazy svn  
> admin
> and cat herder I'd like to see both projects using the
same layout 
>
> It's time for a repo re-org again - -current got
detached from trunk
> and we're starting to get confused again, plus 5.80 is
getting  
> delayed by
> lack of repo setup
>
> Here's the basic proposal -
>
> Catalyst-Runtime/5.70/trunk # current trunk
> Catalyst-Runtime/5.70/branches/* # probably empty
> Catalyst-Runtime/5.80/trunk # new -current equivalent
> Catalyst-Runtime/5.80branches/* # equivalent of
branches/Catalyst- 
> Runtime/ now
>
> Catalyst-Runtime/tags # tags. shockingly.

+1.  Hooray for dropping 'current' 

_______________________________________________
Catalyst-dev mailing list
Catalyst-devlists.rawmode.org
http://lists.rawmode.org/mailman/listinfo/catalyst-dev

On 6/29/07, Andy Grundman <andyhybridized.org> wrote:
>
> On Jun 29, 2007, at 1:40 AM, Matt S Trout wrote:
>
> > (very similar to what I proposed on the DBIC list
but as a lazy svn
> > admin
> > and cat herder I'd like to see both projects using
the same layout 
> >
> > It's time for a repo re-org again - -current got
detached from trunk
> > and we're starting to get confused again, plus
5.80 is getting
> > delayed by
> > lack of repo setup
> >
> > Here's the basic proposal -
> >
> > Catalyst-Runtime/5.70/trunk # current trunk
> > Catalyst-Runtime/5.70/branches/* # probably empty
> > Catalyst-Runtime/5.80/trunk # new -current
equivalent
> > Catalyst-Runtime/5.80branches/* # equivalent of
branches/Catalyst-
> > Runtime/ now
> >
> > Catalyst-Runtime/tags # tags. shockingly.
>
> +1.  Hooray for dropping 'current' 
>
> _______________________________________________
> Catalyst-dev mailing list
> Catalyst-devlists.rawmode.org
> http://lists.rawmode.org/mailman/listinfo/catalyst-dev

>

yes, cool.

_______________________________________________
Catalyst-dev mailing list
Catalyst-devlists.rawmode.org
http://lists.rawmode.org/mailman/listinfo/catalyst-dev

On Friday 29 June 2007 03:03:52 am Kieren Diment wrote:
> > Here's the basic proposal -
> >
> > Catalyst-Runtime/5.70/trunk # current trunk
> > Catalyst-Runtime/5.70/branches/* # probably empty
> > Catalyst-Runtime/5.80/trunk # new -current
equivalent
> > Catalyst-Runtime/5.80/branches/* # equivalent of
> > branches/Catalyst-Runtime/ now
> >
> > Catalyst-Runtime/tags # tags. shockingly.

I like this.  It will be much easier to automatically
migrate to a different 
version control system if we feel like it.

Is the plan to do the same for everything else?

Catalyst-Plugin-Something/trunk
Catalyst-Plugin-Something/branches
Catalyst-Plugin-Something/tags

-- 
package JAPH;use Catalyst
qw/-Debug/;($;=JAPH)->config(name => do {
$,.=reverse qw[Jonathan tsu rehton lre rekca
Rockway][$_].[split //,
";$;"]->[$_].q; ;for
1..4;$,=~s;^.;;;$,});$;->setup;

_______________________________________________
Catalyst-dev mailing list
Catalyst-devlists.rawmode.org
http://lists.rawmode.org/mailman/listinfo/catalyst-dev

On Wed, Jul 04, 2007 at 05:38:50PM -0500, Jonathan Rockway
wrote:
> On Friday 29 June 2007 03:03:52 am Kieren Diment
wrote:
> > > Here's the basic proposal -
> > >
> > > Catalyst-Runtime/5.70/trunk # current trunk
> > > Catalyst-Runtime/5.70/branches/* # probably
empty
> > > Catalyst-Runtime/5.80/trunk # new -current
equivalent
> > > Catalyst-Runtime/5.80/branches/* # equivalent
of
> > > branches/Catalyst-Runtime/ now
> > >
> > > Catalyst-Runtime/tags # tags. shockingly.
> 
> I like this.  It will be much easier to automatically
migrate to a different 
> version control system if we feel like it.
> 
> Is the plan to do the same for everything else?
> 
> Catalyst-Plugin-Something/trunk
> Catalyst-Plugin-Something/branches
> Catalyst-Plugin-Something/tags

I was going to cut across Catalyst core and DBIx-Class only
to begin with.

Then if it works we can script the migration for everything
else and if it
doesn't your poor benighted repo admin (i.e. me  only has
the two projects
he's most familiar with to reorg a second time, which makes
it easier for
me to spot something going wrong.

-- 
      Matt S Trout       Need help with your Catalyst or
DBIx::Class project?
   Technical Director    Want a managed development or
deployment platform?
 Shadowcat Systems Ltd.  Contact mst (at)
shadowcatsystems.co.uk for a quote
http://chainsawblues.vo
x.com/             http://www.shadowc
atsystems.co.uk/ 

_______________________________________________
Catalyst-dev mailing list
Catalyst-devlists.rawmode.org
http://lists.rawmode.org/mailman/listinfo/catalyst-dev