[haiku-development] Re: Ready to go for R1/Alpha4 yet?

  • From: John Scipione <jscipione@xxxxxxxxx>
  • To: haiku-development@xxxxxxxxxxxxx
  • Date: Mon, 30 Jul 2012 16:28:13 -0400

On Mon, Jul 30, 2012 at 2:36 PM, scottmc <scottmc2@xxxxxxxxx> wrote:
> Are we ready yet to make a push for an Alpha4 release?  Here's a
> proposed schedule.  Do we have volunteers to help make it happen?
> http://dev.haiku-os.org/wiki/R1/Alpha4/StatusAndCoordination

I suppose the time for R1/Alpha4 has finally come. First thing we need
to do is to assign a release coordinator to facilitate the process. I
nominate Ryan Leavengood since he seems to be getting back into Haiku
development again recently.

> August 18th as the cut off date for any new features, including any
> changes to text that would need to be translated by our many
> translators out there.
>
> August 19th - August 25 as a bug crushing week, and to put in the final
> pieces, including the latest translations from Pootle.  This might
> also be a good week to focus on coverity bugs as well:
> http://dev.haiku-os.org/wiki/Coverity
>
> August 26 - 31 to test and work out any remaining major showstoppers,
> with a possible release date 2-3 days after we declare it stable.
>
> September 1st as a possible release date.
>
> All dates would be subject to change depending on how things progress of 
> course.
>
> This would be our first release since the move to git, and also the
> first since moving from HTA to pootle, so there might be a few more
> bumps than in the previous releases.

I thought that the release schedule was delayed to accommodate GSOC
although I suppose that is not strictly necessary. Do we want to wait
for R1/A4 until after GSOC commences to incorporate the student's
changes and when there is more spare time from mentors? If that is not
a consideration then the above release schedule seems fine to me.

> Please review the list of open R1/Alpha4 tickets and if you are
> involved with one or more of them determine whether or not it should
> be worth holding up a release to get it fixed, or if a fix could be in
> place in time, and adjust the ticket's comments and milestone
> accordingly.
> http://dev.haiku-os.org/query?status=assigned&status=in-progress&status=reopened&status=new&group=status&milestone=R1%2Falpha4
>
> Here's the wiki page for coordinating the release.  We still need
> volunteers to step up to help make this happen.
> http://dev.haiku-os.org/wiki/R1/Alpha4/StatusAndCoordination
>
> Comments?

Once a release coordinator is secured we'll need to finalize the
schedule, create a r1alpha4 branch, and fix blocker bugs. But the main
work is going to be rebuilding each of the optional packages.

One change I'd like to make for R1A4 is to add virtual methods in
ControlLook and also add dummy FBC padding virtual methods for future
expansion. This will break all packages that depends on ControlLook,
which is most packages, so I figure that R1A4 is the time to do it.
Then we can rebuild each package with this change made.

John Scipione

Other related posts: