DragonFly 3.4 release planning

[Justin Sherrill <justin@xxxxxxxxxxxxxxxxxx>]

--047d7bd91f1044325e04d9167296
Content-Type: text/plain; charset=ISO-8859-1

Here's my extended thinking for the 3.4 release.  Things to have:

* The ability to use either dports or pkgsrc on a new install

This is possible now with /usr/Makefile.  It would be slightly easier with
pkg already installed on the release, but not absolutely necessary.

* A set of dports binaries for download

Francois Tigeot has already built a x86-64 set; I don't know if we have a
i386 set yet.

* A set of dports binaries mirrored

I'd like to see them on avalon and therefore easily mirrored. ftigeot,
marino - we could rsync them from wherever you want to build them, if that
would work out.

* Written instructions somewhere on dragonflybsd.org for using dports

This just requires someone to do it.  I can do that, since I've already
written similar instructions on the Digest.

* A binary build of pkgsrc-2013Q1

This is the biggest time consumer; pkgsrc-2013Q1 is due in a few days, and
it usually takes me a few weeks to get a complete build.  Since pkgsrc
works generally better from source anyway, it may be worth not holding up
the release for this.

* Anything remaining that people want to commit to DragonFly

I don't think there's anything... we've had a lot of updates for stability
because of poudriere and so on, so we've reached the point where people are
recommending 3.3 over 3.2 - that's a signal for release.

The schedule:

FreeBSD ports is entering freeze on March 30, which gives some time to get
a complete build from dports.  I'll guess a minimum week for that, for
building and uploading, assuming it's going to avalon for mirroring.

I'd like to avoid having a release during Google Summer of Code (assuming
we get in again); students aren't announced until the end of May, so that
gives a max time frame of nearly 2 months.

I'll handle release stuff as with previous releases, assuming nobody else
is interested in trying it.  My schedule's a mess, but it's getting better
with the end of the snow season.

Based on this, I'm thinking a 3.4 release target of April 13-14.

If you have a feature you want to get in that won't work with this
schedule, please say so.  If you have some delicious cookies and are going
to send them to me, please say so.  If one of my plan ideas here isn't
workable, please say so.  If I just volunteered you for more work (possibly
marino, ftigeot) and it won't work out, please say so.

--047d7bd91f1044325e04d9167296
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Here&#39;s my extended thinking for the 3.4 release. =A0Th=
ings to have:<div style><br></div><div style>* The ability to use either dp=
orts or pkgsrc on a new install<br></div><div style><br></div><div style>Th=
is is possible now with /usr/Makefile. =A0It would be slightly easier with =
pkg already installed on the release, but not absolutely necessary.</div>
<div style><br></div><div style>* A set of dports binaries for download</di=
v><div style><br></div><div style>Francois Tigeot has already built a x86-6=
4 set; I don&#39;t know if we have a i386 set yet. =A0</div><div style><br>
</div><div style>* A set of dports binaries mirrored</div><div style><br></=
div><div style>I&#39;d like to see them on avalon and therefore easily mirr=
ored. ftigeot, marino - we could rsync them from wherever you want to build=
 them, if that would work out.</div>
<div style><br></div><div style>* Written instructions somewhere on <a href=
=3D"http://dragonflybsd.org";>dragonflybsd.org</a> for using dports<br></div=
><div style><br></div><div style>This just requires someone to do it. =A0I =
can do that, since I&#39;ve already written similar instructions on the Dig=
est.</div>
<div style><br></div><div style>* A binary build of pkgsrc-2013Q1</div><div=
 style><br></div><div style>This is the biggest time consumer; pkgsrc-2013Q=
1 is due in a few days, and it usually takes me a few weeks to get a comple=
te build. =A0Since pkgsrc works generally better from source anyway, it may=
 be worth not holding up the release for this.</div>
<div style><br></div><div style>* Anything remaining that people want to co=
mmit to DragonFly</div><div style><br></div><div style>I don&#39;t think th=
ere&#39;s anything... we&#39;ve had a lot of updates for stability because =
of poudriere and so on, so we&#39;ve reached the point where people are rec=
ommending 3.3 over 3.2 - that&#39;s a signal for release.</div>
<div style><br></div><div style>The schedule:</div><div style><br></div><di=
v style>FreeBSD ports is entering freeze on March 30, which gives some time=
 to get a complete build from dports. =A0I&#39;ll guess a minimum week for =
that, for building and uploading, assuming it&#39;s going to avalon for mir=
roring.</div>
<div style><br></div><div style>I&#39;d like to avoid having a release duri=
ng Google Summer of Code (assuming we get in again); students aren&#39;t an=
nounced until the end of May, so that gives a max time frame of nearly 2 mo=
nths.</div>
<div style><br></div><div style>I&#39;ll handle release stuff as with previ=
ous releases, assuming nobody else is interested in trying it. =A0My schedu=
le&#39;s a mess, but it&#39;s getting better with the end of the snow seaso=
n.</div>
<div style><br></div><div style>Based on this, I&#39;m thinking a 3.4 relea=
se target of April 13-14.</div><div style><br></div><div style>If you have =
a feature you want to get in that won&#39;t work with this schedule, please=
 say so. =A0If you have some delicious cookies and are going to send them t=
o me, please say so. =A0If one of my plan ideas here isn&#39;t workable, pl=
ease say so. =A0If I just volunteered you for more work (possibly marino, f=
tigeot) and it won&#39;t work out, please say so. =A0</div>
<div style><br></div><div style><br></div><div style><br></div></div>

--047d7bd91f1044325e04d9167296--