Bryce Harrington wrote:
> Hi all,
> It's been a while since our 0.45.1 release, and a ton of good new
> features have been added in. However, in recent months many of us have
> busy with new jobs, school, conferences, etc. However with summer here
> I'd like to hear if there is interest in seeing 0.46 released?
Definitely been a bit since the last release... and as much as I would
love to see a new release, it would take a lot of manpower to get 0.46
in shape in a month. So much that I see it as unfeasible (a few of our
core people are very busy and others are MIA).
We would have to determine what of the in-progress features could be
included, update documentation (which the tutorials are undergoing a
pretty major overhaul), testing, bug fixing, more testing, pre-releases,
getting an about screen, etc... all of which are best not rushed.
> Ubuntu's next feature freeze is August 16th, one month from now. I
> would love to see Inkscape 0.46 ready for inclusion there, and would be
> able to pitch in help if others are also interested in getting an
> Inkscape release out in that timeframe. What do you think?
My vote is no for this dev cycle of Ubuntu. It won't be in the main
repos, but wouldn't a backport be doable? I know that's not the most
user friendly, but it's not a bad compromise for one release. Another
option is since we have a couple Ubuntu folk on board, perhaps we could
have unofficial debs on SF for people.
It seems appropriate to me to bring something up that we haven't
discussed in a while. Is anyone else interested in getting on the Gnome
release schedule? It makes the most sense to me as it seems the "major"
distros try to synch with it as well.
Being on the Gnome release schedule would give us a regimented 6 month
release cycle. It has the potential for us to really streamline our
release process by having a posted schedule for feature freeze, bug
fixing, testing, string freeze, etc. Obviously if we feel it's better to
cut a release sooner, that's no problem. But, this way gives us an "at
most" (which we could still stray from if need really exists) timeframe.
Currently the only thing I can think of that will consistently conflict
with the Gnome schedule is GSoC. And if we do entertain the idea of the
Gnome/6 month schedule, it would make sense for us to have all SoC
projects in a branch.
I know that branches can be a pain, but Johan has done a good job with
his this year. Given how well it's worked for Johan, I think that more
than one student merging changes from trunk to a GSoC branch would make
it even smoother. I'd even go as far as to suggest us more seriously
looking into git to avoid the pain we typically see with branches, but,
we do have a few win32 devs and last I heard, git on win32 wouldn't be
an option (unfortunately).
Anyone have any thoughts on this?