Inkscape 0.49 status update & discussion of a proposed release plan
Hey All!
Are there any larger features people are planning on still for this cycle that aren't well known? If you want to get something in that is unknown, please speak up soon because we want to help you test it. :) I know of the following items which we're looking to get in: *All of the current GSoC projects. :) *fingers crossed* *What will also probably be more work towards GTK3 compatibility.
On the refactoring front I can report good news that Abhishek Sharma has gotten all proper libcroco stuff submitted upstream. If lucky, we may be just a few distribution releases away from being able to take libcroco out of trunk!
Additionally, Alex Valavanis has brought our in-trunk copy of libgdl up-to-par with the 2.X (whatever is "current") branch of libgdl. I'm unsure if patch submissions have been made in that direction for the couple of custom features that we have in our copy. Either way, hopefully we'll be able to get our copy out of trunk around the same time.
Campbell Barton has been plugging away on cmake related stuff. I'm not sure of the status of it, especially cross-platform-wise.
Obviously, Krzysztof Konsinski's GSoC work from last year has been merged and all I can say is... please stress test this the best you can. Pretend you don't know how to use Inkscape and break it like a newb. ;)
Are there any big refactoring goals we're still missing out on that people think we should shoot for? (please be reasonable)
I'm planning on looking to look into a couple Windows things, but will save that for a different email.
All of that aside, here is a VERY loose and preliminary proposed release plan:
Mid-August for Chill Beginning of September for Frost (Bug Hunt begins) End of September for Feature Freeze End of October for Hard Freeze Sometime in November for Branch & Release
I'd like feedback on the bug hunt goal. I think we've actually gotten a lot accomplished for a release just with the cairo renderer alone. Newly created bugs aside (as in, if you introduce bugs during this cycle, they don't count toward the total), 250 points seems like a reasonable goal. Do note, we will be releasing an uber-stable 0.48.3 more likely than not, so if we release "0.49" to a wider audience to get more testing, it's not so bad.
For those new to the process, our bug hunt will begin at Feature Freeze. Traditionally, we specify a point target for us to reach, and award us points based on the severity of the bug: 3, 6, 9, or 12 points for low, medium, high, and critical.
Lastly... version numbering... we have way too many opinions about this. I do want to reiterate, Inkscape deserves a more "grown-up" version numbering scheme for users. I very much think Mental's comment about we should have a public version number and then stick with our current numbering scheme for development purposes. It's akin to code-names internally and solid numbers publicly. So, are date formats appealing? YY.MM or YYYY, some arbitrary number we just agree on starting with, bump the decimal place from with the current numbering, or what? If we get too many opinions again, I'll propose handing it over to the board...
Thoughts or comments?
Cheers, Josh
On Thu, 2011-07-28 at 19:12 -0700, Josh Andler wrote:
Are there any larger features people are planning on still for this cycle that aren't well known? If you want to get something in that is unknown, please speak up soon because we want to help you test it. :) I know of the following items which we're looking to get in: *All of the current GSoC projects. :) *fingers crossed* *What will also probably be more work towards GTK3 compatibility.
Hey Josh,
Could you make a comprehensive list of all features under development, or link to the place where they might be tracked? I know Inkscape doesn't make heavy use of launchpad blueprints for tracking everything, but I'd like to know what things are moving and what perhaps is open to experimentation and further development.
For perhaps several releases hence.
Martin,
On Thu, Jul 28, 2011 at 8:47 PM, Martin Owens <doctormo@...400...> wrote:
Could you make a comprehensive list of all features under development, or link to the place where they might be tracked?
Honestly, other than the things brought up in this thread. The only items I'm aware of being actively worked on are GSoC projects. Those are the rendering caching work, css related work, javascript related work, and the kml<->svg conversion work. Unfortunately the latter 2 are not as communicative as I would like, so I'm unsure of their status.
Cheers, Josh
On Sat, Aug 13, 2011 at 6:58 PM, Josh Andler wrote:
work, and the kml<->svg conversion work. Unfortunately the latter 2 are not as communicative as I would like, so I'm unsure of their status.
You mean they have passed the midterm evaluation, but now are at the risk of not passing final evaluation?
Alexandre Prokoudine http://libregraphicsworld.org
I mean that with me, communication from one is poor and communication the other is non-existent. I was CC'd on every email between Abhishek and Tavmjong this year, so I am VERY in the know. It was really great in fact. I can ping Krzysztof whenever I want and he is very responsive and gives me great status updates.
The one whose communication is poor had actually given an update a couple weeks ago, but it's been silent since then. I will be pinging the mentors here shortly asking for them to get an update from the student.
One thing for sure, I am going to make it clear next year, should we be accepted again, that we will have a new rule that they MUST give an update at least every other week. If they can't do that, *I* will fail them. If they can't commit to communication as part of their project, they don't understand a large part of what makes open source work.
Cheers, Josh
On Sat, Aug 13, 2011 at 9:18 AM, Alexandre Prokoudine <alexandre.prokoudine@...400...> wrote:
On Sat, Aug 13, 2011 at 6:58 PM, Josh Andler wrote:
work, and the kml<->svg conversion work. Unfortunately the latter 2 are not as communicative as I would like, so I'm unsure of their status.
You mean they have passed the midterm evaluation, but now are at the risk of not passing final evaluation?
Alexandre Prokoudine http://libregraphicsworld.org
FREE DOWNLOAD - uberSVN with Social Coding for Subversion. Subversion made easy with a complete admin console. Easy to use, easy to manage, easy to install, easy to extend. Get a Free download of the new open ALM Subversion platform now. http://p.sf.net/sfu/wandisco-dev2dev _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
On Sat, Aug 13, 2011 at 9:16 PM, Josh Andler wrote:
One thing for sure, I am going to make it clear next year, should we be accepted again, that we will have a new rule that they MUST give an update at least every other week. If they can't do that, *I* will fail them. If they can't commit to communication as part of their project, they don't understand a large part of what makes open source work.
Nothing prevents you from doing it this time excpet it's a little too late :)
As fasr as I can tell, one of the two student who are not reposnive has just committed stuff into his branch, and the other one last committed on August 2. That's something, but not enough indeed.
Alexandre Prokoudine http://libregraphicsworld.org
On Sat, Aug 13, 2011 at 6:58 PM, Josh Andler wrote:
On Thu, Jul 28, 2011 at 8:47 PM, Martin Owens <doctormo@...400...> wrote:
Could you make a comprehensive list of all features under development, or link to the place where they might be tracked?
Honestly, other than the things brought up in this thread. The only items I'm aware of being actively worked on are GSoC projects. Those are the rendering caching work, css related work, javascript related work, and the kml<->svg conversion work. Unfortunately the latter 2 are not as communicative as I would like, so I'm unsure of their status.
Nicolas Dufour did some more work on image embedding/linking management dialogs few weeks ago. Not sure what the current status is, but I'd probably take a risk of trying to fit it in.
So, what's the plan for 0.49 as of now? One GSoC project is in, two more are reportedly ready for merging. What abut the rest?
Alexandre Prokoudine http://libregraphicsworld.org
Nicolas did also a lot of work with me on Customizable filters (internal extensions) : 46 items at the moment (and we are working on a couple more), some if them regrouping several old ones. I did some new regular ones. Filters menu is simplified.
ivan
________________________________ De : Alexandre Prokoudine <alexandre.prokoudine@...400...> À : Inkscape Devel List inkscape-devel@lists.sourceforge.net Envoyé le : Lundi 19 Septembre 2011 14h54 Objet : Re: [Inkscape-devel] Inkscape 0.49 status update & discussion of a proposed release plan
On Sat, Aug 13, 2011 at 6:58 PM, Josh Andler wrote:
On Thu, Jul 28, 2011 at 8:47 PM, Martin Owens <doctormo@...400...> wrote:
Could you make a comprehensive list of all features under development, or link to the place where they might be tracked?
Honestly, other than the things brought up in this thread. The only items I'm aware of being actively worked on are GSoC projects. Those are the rendering caching work, css related work, javascript related work, and the kml<->svg conversion work. Unfortunately the latter 2 are not as communicative as I would like, so I'm unsure of their status.
Nicolas Dufour did some more work on image embedding/linking management dialogs few weeks ago. Not sure what the current status is, but I'd probably take a risk of trying to fit it in.
So, what's the plan for 0.49 as of now? One GSoC project is in, two more are reportedly ready for merging. What abut the rest?
Alexandre Prokoudine http://libregraphicsworld.org
------------------------------------------------------------------------------ BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA Learn about the latest advances in developing for the BlackBerry® mobile platform with sessions, labs & more. See new tools and technologies. Register for BlackBerry® DevCon today! http://p.sf.net/sfu/rim-devcon-copy1 _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
On Mon, Sep 19, 2011 at 5:54 AM, Alexandre Prokoudine <alexandre.prokoudine@...400...> wrote:
On Sat, Aug 13, 2011 at 6:58 PM, Josh Andler wrote:
On Thu, Jul 28, 2011 at 8:47 PM, Martin Owens <doctormo@...400...> wrote:
Could you make a comprehensive list of all features under development, or link to the place where they might be tracked?
Honestly, other than the things brought up in this thread. The only items I'm aware of being actively worked on are GSoC projects. Those are the rendering caching work, css related work, javascript related work, and the kml<->svg conversion work. Unfortunately the latter 2 are not as communicative as I would like, so I'm unsure of their status.
Nicolas Dufour did some more work on image embedding/linking management dialogs few weeks ago. Not sure what the current status is, but I'd probably take a risk of trying to fit it in.
I haven't tested it yet, but he said it was not quite ready for primetime. I do plan on taking a look sometime this week though.
So, what's the plan for 0.49 as of now? One GSoC project is in, two more are reportedly ready for merging. What abut the rest?
According to the respective mentors, more cleanup work needs to be done on both of the projects prior to merging (in other words, not ready for merging). Given the issues we have with the new renderer and that it seems some patches will be necessary for pixman (bitmaps resized smaller for example) and possibly cairo too, don't count on it too soon.
Cheers, Josh
2011/7/29 Josh Andler <scislac@...400...>:
Campbell Barton has been plugging away on cmake related stuff. I'm not sure of the status of it, especially cross-platform-wise.
I recall that Johan reported that CMake build does not work on Windows due to extremely long command lines that exceed the 8kiB command line limit. http://support.microsoft.com/kb/830473
I was close to hitting this limit with Waf as well, but because Waf uses much shorter filenames for intermediate object files, the build did work and I got a functioning Inkscape.
Regards, Krzysztof
Regarding the status of cmake, only tested on linux, the resulting installed inkscape binary opens and runs for me. AFAICS it should work well for development - edit, compile, run.
it includes all source & headers so resulting project files load in IDE's - tested eclipse/netbeans/qtcreator.
Its still missing some build time options - color management for example, but these are not that hard to add.
Main TODO's are... - installing translations - building Inkview binary. - getting it working on mac/win.
Regarding mingw not building, suspect this is because the library for inkscapes main src dir needs to be split up into pieces, need to check on that.
So far the only feedback I have is that it doesn't work on mac/windows, not sure if anyone got this working or found it useful on linux/bsd.
2011/8/1 Krzysztof Kosiński <tweenk.pl@...400...>:
2011/7/29 Josh Andler <scislac@...400...>:
Campbell Barton has been plugging away on cmake related stuff. I'm not sure of the status of it, especially cross-platform-wise.
I recall that Johan reported that CMake build does not work on Windows due to extremely long command lines that exceed the 8kiB command line limit. http://support.microsoft.com/kb/830473
I was close to hitting this limit with Waf as well, but because Waf uses much shorter filenames for intermediate object files, the build did work and I got a functioning Inkscape.
Regards, Krzysztof
Got Input? Slashdot Needs You. Take our quick survey online. Come on, we don't ask for help often. Plus, you'll get a chance to win $100 to spend on ThinkGeek. http://p.sf.net/sfu/slashdot-survey _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
2011/8/1 Campbell Barton <ideasman42@...400...>:
Main TODO's are...
- installing translations
- building Inkview binary.
- getting it working on mac/win.
OK, so it seems my Waf attempt was significantly more advanced when I stopped working on it. It compiled and installed translations, handled the Bazaar revision number, built Inkview, built separate debug symbol files (something missing from Autotools but present in the Windows buildtool), worked on Windows, built the Windows NSIS installer, and had a special command to regenerate the translation templates; the only thing missing for feature parity with Autotools was OSX support.
Regards, Krzysztof
2011/8/2 Krzysztof Kosiński <tweenk.pl@...400...>:
2011/8/1 Campbell Barton <ideasman42@...400...>:
Main TODO's are...
- installing translations
- building Inkview binary.
- getting it working on mac/win.
OK, so it seems my Waf attempt was significantly more advanced when I stopped working on it. It compiled and installed translations, handled the Bazaar revision number, built Inkview, built separate debug symbol files (something missing from Autotools but present in the Windows buildtool), worked on Windows, built the Windows NSIS installer, and had a special command to regenerate the translation templates; the only thing missing for feature parity with Autotools was OSX support.
Regards, Krzysztof
Hi Krzysztof, Id be interested to look at you're waf branch to see how you handled translations, is it still available?
2011/8/2 Campbell Barton <ideasman42@...400...>:
2011/8/2 Krzysztof Kosiński <tweenk.pl@...400...>:
2011/8/1 Campbell Barton <ideasman42@...400...>:
Main TODO's are...
- installing translations
- building Inkview binary.
- getting it working on mac/win.
OK, so it seems my Waf attempt was significantly more advanced when I stopped working on it. It compiled and installed translations, handled the Bazaar revision number, built Inkview, built separate debug symbol files (something missing from Autotools but present in the Windows buildtool), worked on Windows, built the Windows NSIS installer, and had a special command to regenerate the translation templates; the only thing missing for feature parity with Autotools was OSX support.
Regards, Krzysztof
Hi Krzysztof, Id be interested to look at you're waf branch to see how you handled translations, is it still available?
I believe this is it: https://launchpad.net/inkwaf
Cheers, Josh
W dniu 2 sierpnia 2011 18:20 użytkownik Josh Andler <scislac@...400...> napisał:
Hi Krzysztof, Id be interested to look at you're waf branch to see how you handled translations, is it still available?
I believe this is it: https://launchpad.net/inkwaf
That's only the source for the Waf script, which has some modifications compared to stock Waf 1.5. The branch itself is at lp:~tweenk/inkscape/waf-build
Regards, Krzysztof
On Jul 28, 2011, at 7:12 PM, Josh Andler wrote:
Hey All!
Are there any larger features people are planning on still for this cycle that aren't well known? If you want to get something in that is unknown, please speak up soon because we want to help you test it. :)
Navigator window More for the adaptive UI Might be a little more once my brain thaws from the trip.
Obviously, Krzysztof Konsinski's GSoC work from last year has been merged and all I can say is... please stress test this the best you can. Pretend you don't know how to use Inkscape and break it like a newb. ;)
There was mention of a fallback that wouldn't require cairo 1.10+, but that would most likely have to wait for post-GSoC. However... given potential loss of LTS support, having a fallback would be very beneficial for our users and for promoting use.
Are there any big refactoring goals we're still missing out on that people think we should shoot for? (please be reasonable)
Some tuning of the export/save API to enhance 'publishing'.
This would affect Open Clipart Library, Deviant Art and possibly Wikipedia/Wikimedia commons. At OSCON I had a chance to talk to some of the wikipedia people, and they were very interested in connecting me with the correct people on their side. Martin Owens and I had initially started trying to figure this out at LGM this year.
All of that aside, here is a VERY loose and preliminary proposed release plan:
Mid-August for Chill Beginning of September for Frost (Bug Hunt begins) End of September for Feature Freeze End of October for Hard Freeze Sometime in November for Branch & Release
Seems fairly reasonable, given we take an aggressive stance on testing and integrating the GSoC projects.
Lastly... version numbering... we have way too many opinions about this. I do want to reiterate, Inkscape deserves a more "grown-up" version numbering scheme for users. I very much think Mental's comment about we should have a public version number and then stick with our current numbering scheme for development purposes. It's akin to code-names internally and solid numbers publicly. So, are date formats appealing? YY.MM or YYYY, some arbitrary number we just agree on starting with, bump the decimal place from with the current numbering, or what? If we get too many opinions again, I'll propose handing it
We might want to take another look at this after pondering a few things. For some reason going to version 4.9 has started sounding very interesting. This most likely needs to be looked at on another thread.
Josh Andler <scislac@...400...> writes:
Hey All!
Are there any larger features people are planning on still for this cycle that aren't well known? If you want to get something in that is unknown, please speak up soon because we want to help you test it. :) I know of the following items which we're looking to get in: *All of the current GSoC projects. :) *fingers crossed* *What will also probably be more work towards GTK3 compatibility.
On the refactoring front I can report good news that Abhishek Sharma has gotten all proper libcroco stuff submitted upstream. If lucky, we may be just a few distribution releases away from being able to take libcroco out of trunk!
Additionally, Alex Valavanis has brought our in-trunk copy of libgdl up-to-par with the 2.X (whatever is "current") branch of libgdl. I'm unsure if patch submissions have been made in that direction for the couple of custom features that we have in our copy. Either way, hopefully we'll be able to get our copy out of trunk around the same time.
Campbell Barton has been plugging away on cmake related stuff. I'm not sure of the status of it, especially cross-platform-wise.
Obviously, Krzysztof Konsinski's GSoC work from last year has been merged and all I can say is... please stress test this the best you can. Pretend you don't know how to use Inkscape and break it like a newb. ;)
Are there any big refactoring goals we're still missing out on that people think we should shoot for? (please be reasonable)
I'm planning on looking to look into a couple Windows things, but will save that for a different email.
All of that aside, here is a VERY loose and preliminary proposed release plan:
Mid-August for Chill Beginning of September for Frost (Bug Hunt begins) End of September for Feature Freeze End of October for Hard Freeze Sometime in November for Branch & Release
I'd like feedback on the bug hunt goal. I think we've actually gotten a lot accomplished for a release just with the cairo renderer alone. Newly created bugs aside (as in, if you introduce bugs during this cycle, they don't count toward the total), 250 points seems like a reasonable goal. Do note, we will be releasing an uber-stable 0.48.3 more likely than not, so if we release "0.49" to a wider audience to get more testing, it's not so bad.
For those new to the process, our bug hunt will begin at Feature Freeze. Traditionally, we specify a point target for us to reach, and award us points based on the severity of the bug: 3, 6, 9, or 12 points for low, medium, high, and critical.
Lastly... version numbering... we have way too many opinions about this. I do want to reiterate, Inkscape deserves a more "grown-up" version numbering scheme for users. I very much think Mental's comment about we should have a public version number and then stick with our current numbering scheme for development purposes. It's akin to code-names internally and solid numbers publicly. So, are date formats appealing? YY.MM or YYYY, some arbitrary number we just agree on starting with, bump the decimal place from with the current numbering, or what? If we get too many opinions again, I'll propose handing it over to the board...
Thoughts or comments?
I have a dbus branch with several bugfixes and some additional seemingly safe additions:
https://code.launchpad.net/~joakim-verona/inkscape/dbus-fixes
The code is battle-proven by my Inkmacs project:
https://github.com/jave/inkmacs
I also have a fairly small patch to enable embedding of Inkscape in other applications using the Xembed protocoll. I don't think it's clean enough to go into trunk yet except maybe as a configurable experimental option, but I could polish it if theres interest.
It works by providing a --socket-id command line option. When Inkscape starts it then creates a gtkplug toplevel instead of the ordinary toplevel, and embeds itself there. This is similar to how many other applications do it.
What's missing is a dbus function to create more xembedded windows. Currently new windows after the first embedded one become ordinary toplevels again.
Cheers, Josh
Got Input? Slashdot Needs You. Take our quick survey online. Come on, we don't ask for help often. Plus, you'll get a chance to win $100 to spend on ThinkGeek. http://p.sf.net/sfu/slashdot-survey_________________________________________... Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
participants (8)
-
unknown＠example.com -
Alexandre Prokoudine -
Campbell Barton -
Ivan Louette -
Jon Cruz -
Josh Andler -
Krzysztof Kosiński -
Martin Owens