Re: [gst-cvs] gst-plugins-base: theoradec: rearrange code in preparation for 422 and 444 support.

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: [gst-cvs] gst-plugins-base: theoradec: rearrange code in preparation for 422 and 444 support.

Jan Schmidt-6
Dude,

Core/Base, and Python are still frozen. Just like every release cycle
for the last 15 months, they stay frozen for a day after the release in
case there's a need to make a brown-paper-bag release.

Do I need to make the modules read-only when they're frozen, or do we
need to change the release process in some way perhaps? I've thought of
doing releases from a branch and cherry-picking blocker commits as they
come in, so that people can keep committing to trunk. The disadvantage
of that is that I'm pretty sure that I'll be 1 of maybe 2 people who are
testing the actual codebase that's going into the tarballs.

Something needs fixing, because even after 15 months of this release
process, it seems someone does this every cycle.

- Jan

On Sun, 2009-05-10 at 18:09 -0700, Michael Smith wrote:

> Module: gst-plugins-base
> Branch: master
> Commit: a91b7f0857ff4933eecd147f441cc097344d00e9
> URL:    http://cgit.freedesktop.org/gstreamer/gst-plugins-base/commit/?id=a91b7f0857ff4933eecd147f441cc097344d00e9
>
> Author: Michael Smith <msmith@syncword.(none)>
> Date:   Mon Apr 27 21:01:51 2009 -0700
>
> theoradec: rearrange code in preparation for 422 and 444 support.
>
> ---
>
>  ext/theora/gsttheoradec.h |    1 +
>  ext/theora/theoradec.c    |  199 +++++++++++++++++++++++++-------------------
>  2 files changed, 114 insertions(+), 86 deletions(-)
>
> Diff:   http://cgit.freedesktop.org/gstreamer/gst-plugins-base/diff/?id=a91b7f0857ff4933eecd147f441cc097344d00e9
>
> ------------------------------------------------------------------------------
> The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
> production scanning environment may not be a perfect world - but thanks to
> Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
> Series Scanner you'll get full speed at 300 dpi even with all image
> processing features enabled. http://p.sf.net/sfu/kodak-com
> _______________________________________________
> gstreamer-cvs mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/gstreamer-cvs
>
--
Jan Schmidt <[hidden email]>


------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gstreamer-devel
Reply | Threaded
Open this post in threaded view
|

Post-release freezes (was: Re: [gst-cvs] gst-plugins-base: theoradec: rearrange code in preparation for 422 and 444 support.)

Tim-Philipp Müller-2
On Mon, 2009-05-11 at 08:51 +0100, Jan Schmidt wrote:

> Do I need to make the modules read-only when they're frozen, or do we
> need to change the release process in some way perhaps? I've thought of
> doing releases from a branch and cherry-picking blocker commits as they
> come in, so that people can keep committing to trunk. The disadvantage
> of that is that I'm pretty sure that I'll be 1 of maybe 2 people who are
> testing the actual codebase that's going into the tarballs.

I like the way we do things currently. I think master should stay frozen
during releases for exactly the reason that otherwise absolutely no one
will test the code that's going into a release.


> Something needs fixing, because even after 15 months of this release
> process, it seems someone does this every cycle.

Maybe it just needs to be communicated a bit more clearly? Maybe

 - the IRC channel topic should say that the modules are
   still frozen and when they unfreeze

 - the release mails should be followed by a mail to gstreamer-devel
   saying in the subject line that the models are still frozen

or something like that? (Sure, people should know, but still ...)

 Cheers
  -Tim



------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gstreamer-devel
Reply | Threaded
Open this post in threaded view
|

Re: [gst-cvs] gst-plugins-base: theoradec: rearrange code in preparation for 422 and 444 support.

Stefan Sauer
In reply to this post by Jan Schmidt-6
Jan Schmidt schrieb:

> Dude,
>
> Core/Base, and Python are still frozen. Just like every release cycle
> for the last 15 months, they stay frozen for a day after the release in
> case there's a need to make a brown-paper-bag release.
>
> Do I need to make the modules read-only when they're frozen, or do we
> need to change the release process in some way perhaps? I've thought of
> doing releases from a branch and cherry-picking blocker commits as they
> come in, so that people can keep committing to trunk. The disadvantage
> of that is that I'm pretty sure that I'll be 1 of maybe 2 people who are
> testing the actual codebase that's going into the tarballs.
>
> Something needs fixing, because even after 15 months of this release
> process, it seems someone does this every cycle.
>
> - Jan
>  
I have no idea what we can make different, besides bringing our rules to
attention again. We're all human and even though we try to do everything
well, for time to time there is an oversight and these things will happen.

Stefan

> On Sun, 2009-05-10 at 18:09 -0700, Michael Smith wrote:
>  
>> Module: gst-plugins-base
>> Branch: master
>> Commit: a91b7f0857ff4933eecd147f441cc097344d00e9
>> URL:    http://cgit.freedesktop.org/gstreamer/gst-plugins-base/commit/?id=a91b7f0857ff4933eecd147f441cc097344d00e9
>>
>> Author: Michael Smith <msmith@syncword.(none)>
>> Date:   Mon Apr 27 21:01:51 2009 -0700
>>
>> theoradec: rearrange code in preparation for 422 and 444 support.
>>
>> ---
>>
>>  ext/theora/gsttheoradec.h |    1 +
>>  ext/theora/theoradec.c    |  199 +++++++++++++++++++++++++-------------------
>>  2 files changed, 114 insertions(+), 86 deletions(-)
>>
>> Diff:   http://cgit.freedesktop.org/gstreamer/gst-plugins-base/diff/?id=a91b7f0857ff4933eecd147f441cc097344d00e9
>>
>> ------------------------------------------------------------------------------
>> The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
>> production scanning environment may not be a perfect world - but thanks to
>> Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
>> Series Scanner you'll get full speed at 300 dpi even with all image
>> processing features enabled. http://p.sf.net/sfu/kodak-com
>> _______________________________________________
>> gstreamer-cvs mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/gstreamer-cvs
>>
>>    


------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gstreamer-devel
Reply | Threaded
Open this post in threaded view
|

Re: [gst-cvs] gst-plugins-base: theoradec: rearrange code in preparation for 422 and 444 support.

michael smith-6-3
In reply to this post by Jan Schmidt-6
On Mon, May 11, 2009 at 12:51 AM, Jan Schmidt <[hidden email]> wrote:
> Dude,
>
> Core/Base, and Python are still frozen. Just like every release cycle
> for the last 15 months, they stay frozen for a day after the release in
> case there's a need to make a brown-paper-bag release.

Sorry. Normal practice is that the irc channel topic says which
modules are frozen, I thought. It doesn't mention anything at the
moment.

I'll spend some time trying to figure out how to get git to revert
these later today, if you want.

Mike

------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gstreamer-devel
Reply | Threaded
Open this post in threaded view
|

Re: [gst-cvs] gst-plugins-base: theoradec: rearrange code in preparation for 422 and 444 support.

Jan Schmidt-6
On Mon, 2009-05-11 at 09:09 -0700, Michael Smith wrote:

> On Mon, May 11, 2009 at 12:51 AM, Jan Schmidt <[hidden email]> wrote:
> > Dude,
> >
> > Core/Base, and Python are still frozen. Just like every release cycle
> > for the last 15 months, they stay frozen for a day after the release in
> > case there's a need to make a brown-paper-bag release.
>
> Sorry. Normal practice is that the irc channel topic says which
> modules are frozen, I thought. It doesn't mention anything at the
> moment.
>
> I'll spend some time trying to figure out how to get git to revert
> these later today, if you want.
>

I'm unfreezing in a few hours anyway, so might as well leave them in.
I'll try and make sure to leave the freeze notice in the channel topic
next time.

For the record, the actual rule is that things unfreeze when I push the
commit that bumps the version number in configure.ac back to
development.

The consensus seems to be that there's nothing wrong with our current
practice apart from me forgetting to leave the IRC topic marked frozen,
so that's cool.

J.
--
Jan Schmidt <[hidden email]>


------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gstreamer-devel
Reply | Threaded
Open this post in threaded view
|

Re: [gst-cvs] gst-plugins-base: theoradec: rearrange code in preparation for 422 and 444 support.

michael smith-6-3
On Mon, May 11, 2009 at 9:54 AM, Jan Schmidt <[hidden email]> wrote:

> I'm unfreezing in a few hours anyway, so might as well leave them in.
> I'll try and make sure to leave the freeze notice in the channel topic
> next time.

Ok. Sorry for the screwup.

>
> For the record, the actual rule is that things unfreeze when I push the
> commit that bumps the version number in configure.ac back to
> development.
>
> The consensus seems to be that there's nothing wrong with our current
> practice apart from me forgetting to leave the IRC topic marked frozen,
> so that's cool.

The current practice is ok with me.

I think it'd be slightly better to branch _at release time_ (but
retain the freeze on trunk before the release). Brown-paper-bag
releases, as well as future security releases if required, would
happen from the branch. No post-release freeze would be required. So
if we were to change anything, that's what I'd suggest.

Mike

------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gstreamer-devel