I've worked with SUV for the past half dozen years or so on figuring out release blocker stuff. I'm willing to take it on even if there is no interest on SUV's end to help determine such things. I will draft a release plan tomorrow morning (as I had previously offered to) and send it to you Bryce for your review and edits and I will begin reviewing for blocker bugs in the tracker after that.
Cheers,
Josh
On Wed, May 04, 2016 at 03:57:51PM +0200, Tavmjong Bah wrote:
> On Wed, 2016-05-04 at 09:04 -0400, Martin Owens wrote:
> > On Wed, 2016-05-04 at 14:27 +0200, Tavmjong Bah wrote:
> > >
> > > We should discuss this on Friday's IRC meeting.
> > Friday's meeting is a board meeting isn't it? I thought developer
> > decisions like releases were more developer consensus on mailing list
> > type things and less board responsibility.
> >
> > (or is this just convenient discussion space?)
>
> Yes, it is not the board's duty to make developer decisions. But I
> think the board does have the responsibility to aid (and prod) the
> developers to make decisions when needed as well as to support the
> execution of those decisions (e.g. fund a dedicated hackfest).
>
> (it is also a convenient discussion space)
You're both right, and I do agree that having a meeting to get things
going with the release is a great idea.
Traditionally we've often encouraged non-board-specific technical
discussions to happen immediately following the board meeting. What if
we had a short board meeting for say 20-30 min, and then a second
followup meeting specifically to focus on release coordination
discussions?
Sounds like we've crested the hill on the cmake work (we still need to
do a comparison between the automake-generated dist and the cmake dist,
to see if we're missing anything important). Once we're comfortable
with what's in the dist, I can cut an alpha release - possibly as early
as this weekend. I'm prepared to do a series of (bi-weekly?)
pre-releases as we work towards the final release. Next step would be
to start gathering a list of release blockers and recruit owners for
getting those items examined; I would love it if someone could volunteer
to coordinate/manage the release blocker bugfixing work.
Bryce
------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@...1794...s.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/inkscape-devel