GNU Classpath version control migration after .99?

View: New views
5 Messages — Rating Filter:   Alert me  

GNU Classpath version control migration after .99?

by Pekka Enberg-4 :: Rate this Message:

| View Threaded | Show Only this Message

Hello,

0.99 is almost out of the door so I'd like to begin the discussion on
version control migration. AFAICT, we've all agreed that we'll dump
CVS but left the decision open to which tool we'll migrate.

What I'd personally like to see is that once 0.99 is out, we shut down
CVS, convert the git mirrors to read-write git repositories:

http://icedtea.classpath.org/mirror/git

and keep the existing Mercurial mirroring scripts in place.

Thoughts?

                                Pekka


Re: GNU Classpath version control migration after .99?

by Andrew Hughes-7 :: Rate this Message:

| View Threaded | Show Only this Message

----- Original Message -----

> Hello,
>
> 0.99 is almost out of the door so I'd like to begin the discussion on
> version control migration. AFAICT, we've all agreed that we'll dump
> CVS but left the decision open to which tool we'll migrate.
>
> What I'd personally like to see is that once 0.99 is out, we shut
> down
> CVS, convert the git mirrors to read-write git repositories:
>
> http://icedtea.classpath.org/mirror/git
>
> and keep the existing Mercurial mirroring scripts in place.
>
> Thoughts?
>

Well, you probably know from

http://developer.classpath.org/pipermail/classpath/2012-March/003180.html

that I'm in favour of a move to git sooner rather than later.

How about we give it a week from now (say Monday 19th, 16h00 UTC), and if there
are no objections, we push the existing IcedTea mirror to the Classpath Savannah
project and start using that?

>                                 Pekka
>
>

--
Andrew :)

Free Java Software Engineer
Red Hat, Inc. (http://www.redhat.com)

PGP Key: 248BDC07 (https://keys.indymedia.org/)
Fingerprint = EC5A 1F5E C0AD 1D15 8F1F  8F91 3B96 A578 248B DC07



Re: GNU Classpath version control migration after .99?

by Pekka Enberg-4 :: Rate this Message:

| View Threaded | Show Only this Message

On Mon, Mar 12, 2012 at 10:00 PM, Andrew Hughes <ahughes@...> wrote:
> Well, you probably know from
>
> http://developer.classpath.org/pipermail/classpath/2012-March/003180.html
>
> that I'm in favour of a move to git sooner rather than later.
>
> How about we give it a week from now (say Monday 19th, 16h00 UTC), and if there
> are no objections, we push the existing IcedTea mirror to the Classpath Savannah
> project and start using that?

I'm obviously happy with that.

                        Pekka


Re: GNU Classpath version control migration after .99?

by Andrew Hughes-7 :: Rate this Message:

| View Threaded | Show Only this Message

----- Original Message -----

> On Mon, Mar 12, 2012 at 10:00 PM, Andrew Hughes <ahughes@...>
> wrote:
> > Well, you probably know from
> >
> > http://developer.classpath.org/pipermail/classpath/2012-March/003180.html
> >
> > that I'm in favour of a move to git sooner rather than later.
> >
> > How about we give it a week from now (say Monday 19th, 16h00 UTC),
> > and if there
> > are no objections, we push the existing IcedTea mirror to the
> > Classpath Savannah
> > project and start using that?
>
> I'm obviously happy with that.
>
>                         Pekka
>

As the deadline has now passed, I've populated the git repository on Savannah:

http://git.savannah.gnu.org/cgit/classpath.git

This is now the active development repository and the old CVS repository is obsolete.
--
Andrew :)

Free Java Software Engineer
Red Hat, Inc. (http://www.redhat.com)

PGP Key: 248BDC07 (https://keys.indymedia.org/)
Fingerprint = EC5A 1F5E C0AD 1D15 8F1F  8F91 3B96 A578 248B DC07



Re: GNU Classpath version control migration after .99?

by Pekka Enberg-4 :: Rate this Message:

| View Threaded | Show Only this Message

On Tue, Mar 20, 2012 at 12:28 AM, Andrew Hughes <ahughes@...> wrote:
> As the deadline has now passed, I've populated the git repository on Savannah:
>
> http://git.savannah.gnu.org/cgit/classpath.git
>
> This is now the active development repository and the old CVS repository is obsolete.

Yay! :-)