GStreamer-devel

Core/Base/Bad/Python released. Next step - moving to GIT.

Classic

List

Threaded

4 messages Options

Jan Schmidt-6

Core/Base/Bad/Python released. Next step - moving to GIT.

Now that the set of Core/Base/Python/Bad release are out of the way, the
plan is to move to GIT over the next week.

Edward will be managing the timing and activity of the actual migration
to fit in with his week at LCA, but the general plan is:

* Core/Base/Bad/Python stay frozen until further notice
* Edward decides when he wants to cue up the migration and lets us know
* At a designated time *all other* modules will freeze in CVS and CVS
will be marked Read-only, so that there can be no commits while the
migration takes place.
* Everything moves to git in the standard locations on the
freedesktop.org servers (which should be something like
http://cgit.freedesktop.org/gstreamer/gstreamer,
http://cgit.freedesktop.org/gstreamer/gst-plugins-base etc)
* Everyone can start using git, and CVS is only useful as a read-only
history.

In case of unexpected disaster:
All repositories are tagged with GIT_MIGRATION for the commit at which
the conversions were done. If the worst comes to worst, we can then
easily get all commits since that conversion as a series of unified-diff
patches, make cvs read-write again, and commit them.

Edward - over to you!

Cheers,
Jan.
--
Jan Schmidt <[hidden email]>

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gstreamer-devel

Edward Hervey

Re: Core/Base/Bad/Python released. Next step - moving to GIT.

Administrator

Thanks Jan for the releases !

So for the missing info:
* I'll be grabbing an fdo admin to de-activate cvs (leaving only
anoncvs). No shortage of them here at LCA.
* Since this switch information has already been circulating for a few
weeks now, I propose to do that at 23:59 CET tonight (20th Jan). For
people in Europe it won't matter that way, but I'm currently in
Australia so leaves me a full day to make sure the migration goes
flawlessly before Europe wakes up again.

The rest is pretty straighforward, and the conversion/upload/activate
should take (with checks) around 4 hours.

I don't think there's much more to say,

See you the other side :)

Edward

On Tue, 2009-01-20 at 00:20 +0000, Jan Schmidt wrote:

> Now that the set of Core/Base/Python/Bad release are out of the way, the
> plan is to move to GIT over the next week.
>
> Edward will be managing the timing and activity of the actual migration
> to fit in with his week at LCA, but the general plan is:
>
> * Core/Base/Bad/Python stay frozen until further notice
> * Edward decides when he wants to cue up the migration and lets us know
> * At a designated time *all other* modules will freeze in CVS and CVS
> will be marked Read-only, so that there can be no commits while the
> migration takes place.
> * Everything moves to git in the standard locations on the
> freedesktop.org servers (which should be something like
> http://cgit.freedesktop.org/gstreamer/gstreamer,
> http://cgit.freedesktop.org/gstreamer/gst-plugins-base etc)
> * Everyone can start using git, and CVS is only useful as a read-only
> history.
>
> In case of unexpected disaster:
> All repositories are tagged with GIT_MIGRATION for the commit at which
> the conversions were done. If the worst comes to worst, we can then
> easily get all commits since that conversion as a series of unified-diff
> patches, make cvs read-write again, and commit them.
>
> Edward - over to you!
>
> Cheers,
> Jan.

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gstreamer-devel

Jan Schmidt-6

Re: Core/Base/Bad/Python released. Next step - moving to GIT.

On Tue, 2009-01-20 at 04:23 +0100, Edward Hervey wrote:

> Thanks Jan for the releases !
>
> So for the missing info:
> * I'll be grabbing an fdo admin to de-activate cvs (leaving only
> anoncvs). No shortage of them here at LCA.
> * Since this switch information has already been circulating for a few
> weeks now, I propose to do that at 23:59 CET tonight (20th Jan). For
> people in Europe it won't matter that way, but I'm currently in
> Australia so leaves me a full day to make sure the migration goes
> flawlessly before Europe wakes up again.

+1 on the timing.

J.

> The rest is pretty straighforward, and the conversion/upload/activate
> should take (with checks) around 4 hours.
>
> I don't think there's much more to say,
>
> See you the other side :)
>
> Edward
>
> On Tue, 2009-01-20 at 00:20 +0000, Jan Schmidt wrote:
> > Now that the set of Core/Base/Python/Bad release are out of the way, the
> > plan is to move to GIT over the next week.
> >
> > Edward will be managing the timing and activity of the actual migration
> > to fit in with his week at LCA, but the general plan is:
> >
> > * Core/Base/Bad/Python stay frozen until further notice
> > * Edward decides when he wants to cue up the migration and lets us know
> > * At a designated time *all other* modules will freeze in CVS and CVS
> > will be marked Read-only, so that there can be no commits while the
> > migration takes place.
> > * Everything moves to git in the standard locations on the
> > freedesktop.org servers (which should be something like
> > http://cgit.freedesktop.org/gstreamer/gstreamer,
> > http://cgit.freedesktop.org/gstreamer/gst-plugins-base etc)
> > * Everyone can start using git, and CVS is only useful as a read-only
> > history.
> >
> > In case of unexpected disaster:
> > All repositories are tagged with GIT_MIGRATION for the commit at which
> > the conversions were done. If the worst comes to worst, we can then
> > easily get all commits since that conversion as a series of unified-diff
> > patches, make cvs read-write again, and commit them.
> >
> > Edward - over to you!
> >
> > Cheers,
> > Jan.
>

--
Jan Schmidt <[hidden email]>

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gstreamer-devel

Edward Hervey

Re: Core/Base/Bad/Python released. Next step - moving to GIT.

Administrator

Update:

* CVS is now read-only (anoncvs)
* conversion is currently underway

I expect to be able to push the converted repos in 2 hours

Edward

On Tue, 2009-01-20 at 12:24 +0000, Jan Schmidt wrote:

> On Tue, 2009-01-20 at 04:23 +0100, Edward Hervey wrote:
> > Thanks Jan for the releases !
> >
> > So for the missing info:
> > * I'll be grabbing an fdo admin to de-activate cvs (leaving only
> > anoncvs). No shortage of them here at LCA.
> > * Since this switch information has already been circulating for a few
> > weeks now, I propose to do that at 23:59 CET tonight (20th Jan). For
> > people in Europe it won't matter that way, but I'm currently in
> > Australia so leaves me a full day to make sure the migration goes
> > flawlessly before Europe wakes up again.
>
> +1 on the timing.
>
> J.
>
> > The rest is pretty straighforward, and the conversion/upload/activate
> > should take (with checks) around 4 hours.
> >
> > I don't think there's much more to say,
> >
> > See you the other side :)
> >
> > Edward
> >
> > On Tue, 2009-01-20 at 00:20 +0000, Jan Schmidt wrote:
> > > Now that the set of Core/Base/Python/Bad release are out of the way, the
> > > plan is to move to GIT over the next week.
> > >
> > > Edward will be managing the timing and activity of the actual migration
> > > to fit in with his week at LCA, but the general plan is:
> > >
> > > * Core/Base/Bad/Python stay frozen until further notice
> > > * Edward decides when he wants to cue up the migration and lets us know
> > > * At a designated time *all other* modules will freeze in CVS and CVS
> > > will be marked Read-only, so that there can be no commits while the
> > > migration takes place.
> > > * Everything moves to git in the standard locations on the
> > > freedesktop.org servers (which should be something like
> > > http://cgit.freedesktop.org/gstreamer/gstreamer,
> > > http://cgit.freedesktop.org/gstreamer/gst-plugins-base etc)
> > > * Everyone can start using git, and CVS is only useful as a read-only
> > > history.
> > >
> > > In case of unexpected disaster:
> > > All repositories are tagged with GIT_MIGRATION for the commit at which
> > > the conversions were done. If the worst comes to worst, we can then
> > > easily get all commits since that conversion as a series of unified-diff
> > > patches, make cvs read-write again, and commit them.
> > >
> > > Edward - over to you!
> > >
> > > Cheers,
> > > Jan.
> >