|
»
« Return to Thread: New release plan
Re: New release plan
by TomHuybrechts
::
Rate this Message:
On Tue, Mar 10, 2009 at 8:45 PM, Kohsuke Kawaguchi
<Kohsuke.Kawaguchi@...> wrote:
> Dean Yu wrote:
>>
>> Hi Kohsuke,
>> Is there a reason you don't want to create a branch on Tuesday evening
>> instead of cutting off commits? It seems ironic that we don't try to
>> practice CI for building Hudson itself.
>
> Yeah, we should do that. I guess I could automate the branch handling on my
> side, and the merging shouldn't be too painful. changelog.html needs to be
> changed a bit so that we can list changes in N+2.
>
> And I think we do practice CI for building Hudson --- there's Hudson on
> Hudson as you can see on http://hudson.glassfish.org/job/hudson/
>
> But my feeling is that our current test coverage is just not high enough to
> catch all the problems this way.
>
I prefer the original idea (a 'voluntary' restraint on committing
during the quiet period) over branching each time.
I'd also like to suggest we take this time to review commits others
have done. Not every problem (e.g. backward compatibility) will be
caught by the tests we have now, but some extra eyeballs will surely
help. Perhaps it would help to send a mail (automatically) every time
the quiet period starts stating changes that have been made since the
last release ? Or a link to a Fisheye page where can you can see them
all at a glance.
Tom
>
>> In the end you're our dictator and I'll go along with whatever you
>> decide. :)
>
> --
> Kohsuke Kawaguchi
> Sun Microsystems http://weblogs.java.net/blog/kohsuke/
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...
<Kohsuke.Kawaguchi@...> wrote:
> Dean Yu wrote:
>>
>> Hi Kohsuke,
>> Is there a reason you don't want to create a branch on Tuesday evening
>> instead of cutting off commits? It seems ironic that we don't try to
>> practice CI for building Hudson itself.
>
> Yeah, we should do that. I guess I could automate the branch handling on my
> side, and the merging shouldn't be too painful. changelog.html needs to be
> changed a bit so that we can list changes in N+2.
>
> And I think we do practice CI for building Hudson --- there's Hudson on
> Hudson as you can see on http://hudson.glassfish.org/job/hudson/
>
> But my feeling is that our current test coverage is just not high enough to
> catch all the problems this way.
>
I prefer the original idea (a 'voluntary' restraint on committing
during the quiet period) over branching each time.
I'd also like to suggest we take this time to review commits others
have done. Not every problem (e.g. backward compatibility) will be
caught by the tests we have now, but some extra eyeballs will surely
help. Perhaps it would help to send a mail (automatically) every time
the quiet period starts stating changes that have been made since the
last release ? Or a link to a Fisheye page where can you can see them
all at a glance.
Tom
>
>> In the end you're our dictator and I'll go along with whatever you
>> decide. :)
>
> --
> Kohsuke Kawaguchi
> Sun Microsystems http://weblogs.java.net/blog/kohsuke/
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...
« Return to Thread: New release plan
| Free embeddable forum powered by Nabble | Forum Help |
