On Wednesday 28 October 2009, Nicolas Pitre wrote:
> On Wed, 28 Oct 2009, David Brownell wrote:
> > On Wednesday 28 October 2009, Zach Welch wrote:
> > >
> > > Are we trying for 0.3.0, or not?!?
> >
> > I was kind of expecting you to cut an RC some time ago;
> > so I've been wondering the same thing ...
>
> OK then. What about cutting it _now_ ?
I'll count that as a vote for what I'll call a
"modified Øyvind plan" ...
- Øyvind suggested Friday,
- I elaborated as 12:01am UTC Friday, which is
about 19.5 hours away, as I write.
That's quite close to "now", but still allows
a little time for last minute panics and even
some last-minute second thoughts and bugfixes.
> Please make it 0.3.0-rc1 right away. If something is really screwed and
> require a big patch then just merge the fix and call it -rc2.
> Otherwise let's ship 0.3.0 final in a week and accept small and only
> obvious bug fixes until then.
Yep, "modified Øyvind plan". I'm all for it.
Let's call this the plan of record. So if
anyone objects, "speak now or forever hold
your peas".
Doc updates are generally OK in this kind of
window too; I have a few of those.
So specifically ... we need names assigned to
action items. The tasks seem to be three:
1 - Create and push a "v0.3.0-rc1" tag,
with associated configure.in update
2 - Create a tarball; test it; distribute
via the SF and Berlios download pages
3 - Send announcement
#1 and #3 are trivial. And in fact, they
suffice -- #2 can come later. In the
interests of moving things forward, I
will sign up to perform those two trivial
tasks at about 12:01 Friday, UTC. (But
if anyone else craves that duty, let me
know!)
Courtesy of commits last night from Zach,
I think #2 *should* be trivial; but I've
not yet tried his scripts. Also, only a
limited number of folk can put tarballs
onto the Berlios download page... the SF
one is a bit more writable. So I'm a bit
inclined to leave #2 up to someone who
can write to both sites.
- Dave
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
