We're having the Inkscape meeting here at LGM
I've put together a page on the website for the next release:
http://inkscape.org/en/develop/next-release/
I've included some details as well as some firm dates for the next release which I want us to hit. Bryce hasn't signed up to a fixed schedule yet, but it's time to get this nailed down and I think we're ready to get a release out now, let alone in a few months. So we should certainly be able to hit it.
What are your thoughts?
Best Regards, Martin Owens
On 4-4-2014 12:32, Martin Owens wrote:
We're having the Inkscape meeting here at LGM
I've put together a page on the website for the next release:
http://inkscape.org/en/develop/next-release/
I've included some details as well as some firm dates for the next release which I want us to hit. Bryce hasn't signed up to a fixed schedule yet, but it's time to get this nailed down and I think we're ready to get a release out now, let alone in a few months. So we should certainly be able to hit it.
What are your thoughts?
Hi Martin, I like that you made a short page where we can check the release status and rough planning. Better than browsing through the list's mails! (the big task now is keeping it up-to-date of course)
Important point: you forgot Josh Andler as the release manager!!! About the dates, from your mail I take it that you didn't discuss with Bryce and Josh? I think it would have been better to do so first. It comes across a bit rude to bypass them and put it on the website just like that. They've put in a lot of effort in this release, please coordinate the content of that page with them. (What does your role as "supervisor" mean?)
For the New Features / bug fixes : I think you can scrap those and point to the release notes instead. What is more interesting to put on this page is links to open bugs, or focus points. So that we know what to work on to move the release along. Perhaps simply a copy of the release status mail.
ciao, Johan
On Mon, 2014-04-07 at 00:25 +0200, Johan Engelen wrote:
Important point: you forgot Josh Andler as the release manager!!! About the dates, from your mail I take it that you didn't discuss with Bryce and Josh? I think it would have been better to do so first. It comes across a bit rude to bypass them and put it on the website just like that.
It is deliberate but hesitant. Inkscape is ready to release and it was clear at LGM that Inkscape is well respected but many of our users came to me with their concerns about our release schedules.
And so this page is basically a template with a good suggestion for timing with lots of space. We can update it if we feel the release needs even more time and it should reflect both the consensus of developers and the release manager.
I know I put myself in a vulnerable position by being bold, and rude in this case, but my hope is that I can ask for forgiveness. Although really the release is a technical matter and so is probably a discussion for developers with the release manager. I'd like to suggest we commit to this release in a firm and adventurous way.
And sooner rather than later. :-)
(What does your role as "supervisor" mean?)
The person who finds the release manager and pushes for firm schedules. I might as well put my name on the line for the job I'm already doing. Not sure about the name for the job though, any suggestions welcome.
For the New Features / bug fixes : I think you can scrap those and point to the release notes instead. What is more interesting to put on this page is links to open bugs, or focus points. So that we know what to work on to move the release along.
The page is public facing, not necessarily developer facing. For that the wiki is the primary vehicle. So bug fixes and new features are useful and should be edited to be more in line with what the public should see (translate into user-speak if possible).
My hope is that this will show something is happening with the project to the outside world and give us a sense of our activity.
Hope this works *cross fingers*
Best Regards, Martin Owens
On 7-4-2014 2:23, Martin Owens wrote:
On Mon, 2014-04-07 at 00:25 +0200, Johan Engelen wrote:
Important point: you forgot Josh Andler as the release manager!!! About the dates, from your mail I take it that you didn't discuss with Bryce and Josh? I think it would have been better to do so first. It comes across a bit rude to bypass them and put it on the website just like that.
It is deliberate but hesitant.
Being deliberately rude I think rarely has the desired effect, and in any case does not create a friendly atmosphere people want to work and spend time in.
Inkscape is ready to release and it was clear at LGM that Inkscape is well respected but many of our users came to me with their concerns about our release schedules.
And so this page is basically a template with a good suggestion for timing with lots of space. We can update it if we feel the release needs even more time and it should reflect both the consensus of developers and the release manager.
Indeed it should, fixed that for you.
I know I put myself in a vulnerable position by being bold, and rude
Please be considerate of others too. I don't think anybody does /not/ want to release; we all want the release sooner than later. To help speed things along, potentially offending people is not so helpful. Instead, a list of current TODO items has a higher chance of success I feel. I've added it to the page.
in this case, but my hope is that I can ask for forgiveness. Although really the release is a technical matter and so is probably a discussion for developers with the release manager. I'd like to suggest we commit to this release in a firm and adventurous way.
And sooner rather than later. :-)
(What does your role as "supervisor" mean?)
The person who finds the release manager and pushes for firm schedules. I might as well put my name on the line for the job I'm already doing. Not sure about the name for the job though, any suggestions welcome.
I don't think we can add all related jobs to that page... The release managers' names are useful for people to direct questions too. But who would want to contact a guy who pushes the ones who are pushing, that he should push the pushers?
For the New Features / bug fixes : I think you can scrap those and point to the release notes instead. What is more interesting to put on this page is links to open bugs, or focus points. So that we know what to work on to move the release along.
The page is public facing, not necessarily developer facing. For that the wiki is the primary vehicle. So bug fixes and new features are useful and should be edited to be more in line with what the public should see (translate into user-speak if possible).
This is exactly what our wiki's Release Notes page is.
My hope is that this will show something is happening with the project to the outside world and give us a sense of our activity.
Hope this works *cross fingers*
Best Regards, Martin Owens
btw, is there someone working on the last blocking bug?
http://inkscape.org/en/contribute/ https://bugs.launchpad.net/inkscape/+bugs?orderby=-importance&field.link...
regards,
Adib. --
On Mon, Apr 7, 2014 at 8:31 PM, Johan Engelen <jbc.engelen@...2592...>wrote:
On 7-4-2014 2:23, Martin Owens wrote:
On Mon, 2014-04-07 at 00:25 +0200, Johan Engelen wrote:
Important point: you forgot Josh Andler as the release manager!!! About the dates, from your mail I take it that you didn't discuss with Bryce and Josh? I think it would have been better to do so first. It comes across a bit rude to bypass them and put it on the website just like that.
It is deliberate but hesitant.
Being deliberately rude I think rarely has the desired effect, and in any case does not create a friendly atmosphere people want to work and spend time in.
Inkscape is ready to release and it was clear at LGM that Inkscape is well respected but many of our users came to me with their concerns about our release schedules.
And so this page is basically a template with a good suggestion for timing with lots of space. We can update it if we feel the release needs even more time and it should reflect both the consensus of developers and the release manager.
Indeed it should, fixed that for you.
I know I put myself in a vulnerable position by being bold, and rude
Please be considerate of others too. I don't think anybody does /not/ want to release; we all want the release sooner than later. To help speed things along, potentially offending people is not so helpful. Instead, a list of current TODO items has a higher chance of success I feel. I've added it to the page.
in this case, but my hope is that I can ask for forgiveness. Although really the release is a technical matter and so is probably a discussion for developers with the release manager. I'd like to suggest we commit to this release in a firm and adventurous way.
And sooner rather than later. :-)
(What does your role as "supervisor" mean?)
The person who finds the release manager and pushes for firm schedules. I might as well put my name on the line for the job I'm already doing. Not sure about the name for the job though, any suggestions welcome.
I don't think we can add all related jobs to that page... The release managers' names are useful for people to direct questions too. But who would want to contact a guy who pushes the ones who are pushing, that he should push the pushers?
For the New Features / bug fixes : I think you can scrap those and point to the release notes instead. What is more interesting to put on this page is links to open bugs, or focus points. So that we know what to work on to move the release along.
The page is public facing, not necessarily developer facing. For that the wiki is the primary vehicle. So bug fixes and new features are useful and should be edited to be more in line with what the public should see (translate into user-speak if possible).
This is exactly what our wiki's Release Notes page is.
My hope is that this will show something is happening with the project
to the outside world and give us a sense of our activity.
Hope this works *cross fingers*
Best Regards, Martin Owens
Put Bad Developers to Shame Dominate Development with Jenkins Continuous Integration Continuously Automate Build, Test & Deployment Start a new project now. Try Jenkins in the cloud. http://p.sf.net/sfu/13600_Cloudbees _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
+1 (Thanks for speaking up, Johan)
On 2014-04-07 20:31 +0100, Johan Engelen wrote:
On 7-4-2014 2:23, Martin Owens wrote:
On Mon, 2014-04-07 at 00:25 +0200, Johan Engelen wrote:
Important point: you forgot Josh Andler as the release manager!!! About the dates, from your mail I take it that you didn't discuss with Bryce and Josh? I think it would have been better to do so first. It comes across a bit rude to bypass them and put it on the website just like that.
It is deliberate but hesitant.
Being deliberately rude I think rarely has the desired effect, and in any case does not create a friendly atmosphere people want to work and spend time in.
Inkscape is ready to release and it was clear at LGM that Inkscape is well respected but many of our users came to me with their concerns about our release schedules.
And so this page is basically a template with a good suggestion for timing with lots of space. We can update it if we feel the release needs even more time and it should reflect both the consensus of developers and the release manager.
Indeed it should, fixed that for you.
I know I put myself in a vulnerable position by being bold, and rude
Please be considerate of others too. I don't think anybody does /not/ want to release; we all want the release sooner than later. To help speed things along, potentially offending people is not so helpful. Instead, a list of current TODO items has a higher chance of success I feel. I've added it to the page.
in this case, but my hope is that I can ask for forgiveness. Although really the release is a technical matter and so is probably a discussion for developers with the release manager. I'd like to suggest we commit to this release in a firm and adventurous way.
And sooner rather than later. :-)
(What does your role as "supervisor" mean?)
The person who finds the release manager and pushes for firm schedules. I might as well put my name on the line for the job I'm already doing. Not sure about the name for the job though, any suggestions welcome.
I don't think we can add all related jobs to that page... The release managers' names are useful for people to direct questions too. But who would want to contact a guy who pushes the ones who are pushing, that he should push the pushers?
For the New Features / bug fixes : I think you can scrap those and point to the release notes instead. What is more interesting to put on this page is links to open bugs, or focus points. So that we know what to work on to move the release along.
The page is public facing, not necessarily developer facing. For that the wiki is the primary vehicle. So bug fixes and new features are useful and should be edited to be more in line with what the public should see (translate into user-speak if possible).
This is exactly what our wiki's Release Notes page is.
My hope is that this will show something is happening with the project to the outside world and give us a sense of our activity.
Hope this works *cross fingers*
Best Regards, Martin Owens
Hi Developers,
I've updated the page with details from Bryce's email back in December.
Also merged the status sections so it's easier to see where we are and where we're going:
http://inkscape.org/en/develop/next-release
Thanks to Johan, Tav and all for pointers and patches.
Best Regards, Martin Owens
On Mon, 2014-04-07 at 00:25 +0200, Johan Engelen wrote:
Hi Martin, I like that you made a short page where we can check the release status and rough planning. Better than browsing through the list's mails! (the big task now is keeping it up-to-date of course)
topmost pending point is "Disable features that aren't finished"
Last year I implemented a pdf import via poppler-cairo - without using poppler internal structures. I think there should not be two import possibilities I would "disable" the import via poppler-cairo. - there are no fine grained import options, - text is converted to strokes always
What is the preffered method to do so? Do we have a -DG_DISABLE_EXPERIMENTAL_FEATURE or similar compile option?
regards, Adib. --
On Tue, Apr 8, 2014 at 4:53 PM, Martin Owens <doctormo@...400...> wrote:
Hi Developers,
I've updated the page with details from Bryce's email back in December.
Also merged the status sections so it's easier to see where we are and where we're going:
http://inkscape.org/en/develop/next-release
Thanks to Johan, Tav and all for pointers and patches.
Best Regards, Martin Owens
On Mon, 2014-04-07 at 00:25 +0200, Johan Engelen wrote:
Hi Martin, I like that you made a short page where we can check the release status and rough planning. Better than browsing through the list's mails! (the big task now is keeping it up-to-date of course)
Put Bad Developers to Shame Dominate Development with Jenkins Continuous Integration Continuously Automate Build, Test & Deployment Start a new project now. Try Jenkins in the cloud. http://p.sf.net/sfu/13600_Cloudbees _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
On 8-4-2014 19:38, the Adib wrote:
topmost pending point is "Disable features that aren't finished"
Last year I implemented a pdf import via poppler-cairo - without using poppler internal structures. I think there should not be two import possibilities I would "disable" the import via poppler-cairo.
- there are no fine grained import options,
- text is converted to strokes always
What is the preffered method to do so? Do we have a -DG_DISABLE_EXPERIMENTAL_FEATURE or similar compile option?
For experimental LPEs, we have a define that you can set to include them: -DLPE_ENABLE_TEST_EFFECTS I think you could mimic that, so instead of a disable option, you should create an enable option (so that per default it is off). Don't think we have a global enable_experiments option.
regards, Johan
the Adib-2 wrote
Last year I implemented a pdf import via poppler-cairo - without using poppler internal structures. I think there should not be two import possibilities I would "disable" the import via poppler-cairo.
- there are no fine grained import options,
- text is converted to strokes always
Please don't do that: FWIU import via poppler-cairo is the only way to import a document with a font not installed in the system. It works perfectly and the only acceptable alternative would be if in the regular PDF import dialog an option to convert fonts to stroke is added and implemented. If I'm missing something, please let me know because the ability to import a document exactly as it appears on a PDF viewer (i.e. without mangling fonts and kerning) is pretty relevant. Thanks.
-- View this message in context: http://inkscape.13.x6.nabble.com/Website-Release-Page-tp4970030p4970114.html Sent from the Inkscape - Dev mailing list archive at Nabble.com.
2014-04-09 8:59 GMT+02:00 LucaDC <dicappello@...2144...>:
the Adib-2 wrote
Last year I implemented a pdf import via poppler-cairo - without using poppler internal structures. I think there should not be two import possibilities I would "disable" the import via poppler-cairo.
- there are no fine grained import options,
- text is converted to strokes always
Please don't do that: FWIU import via poppler-cairo is the only way to import a document with a font not installed in the system. It works perfectly and the only acceptable alternative would be if in the regular PDF import dialog an option to convert fonts to stroke is added and implemented. If I'm missing something, please let me know because the ability to import a document exactly as it appears on a PDF viewer (i.e. without mangling fonts and kerning) is pretty relevant. Thanks.
I have also experienced issues with the default PDF importer which were not present in the poppler-cairo based importer.
I think the import method should be selectable from the PDF import dialog.
Regards, Krzysztof
Hm, Could you then add a bugtracker item and put the Problematic PDF there? Adib.
Am Mittwoch, 9. April 2014 schrieb Krzysztof Kosiński :
2014-04-09 8:59 GMT+02:00 LucaDC <dicappello@...2144...javascript:;
: the Adib-2 wrote
Last year I implemented a pdf import via poppler-cairo - without using poppler internal structures. I think there should not be two import possibilities I would "disable"
the
import via poppler-cairo.
- there are no fine grained import options,
- text is converted to strokes always
Please don't do that: FWIU import via poppler-cairo is the only way to import a document with a font not installed in the system. It works perfectly and the only acceptable alternative would be if in the regular
import dialog an option to convert fonts to stroke is added and
implemented.
If I'm missing something, please let me know because the ability to
import a
document exactly as it appears on a PDF viewer (i.e. without mangling
fonts
and kerning) is pretty relevant. Thanks.
I have also experienced issues with the default PDF importer which were not present in the poppler-cairo based importer.
I think the import method should be selectable from the PDF import dialog.
Regards, Krzysztof
Put Bad Developers to Shame Dominate Development with Jenkins Continuous Integration Continuously Automate Build, Test & Deployment Start a new project now. Try Jenkins in the cloud. http://p.sf.net/sfu/13600_Cloudbees _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net javascript:; https://lists.sourceforge.net/lists/listinfo/inkscape-devel
On 2014-04-09 08:59 +0100, LucaDC wrote:
the Adib-2 wrote
Last year I implemented a pdf import via poppler-cairo - without using poppler internal structures. I think there should not be two import possibilities I would "disable" the import via poppler-cairo.
- there are no fine grained import options,
- text is converted to strokes always
Please don't do that: FWIU import via poppler-cairo is the only way to import a document with a font not installed in the system. It works perfectly and the only acceptable alternative would be if in the regular PDF import dialog an option to convert fonts to stroke is added and implemented. If I'm missing something, please let me know because the ability to import a document exactly as it appears on a PDF viewer (i.e. without mangling fonts and kerning) is pretty relevant.
AFAIU upstream cairo has requests to change it to use <text> with embedded fonts (which Inkscape can't render at the moment): https://bugs.freedesktop.org/show_bug.cgi?id=38516
Personally, I do appreciate having this alternative PDF import available: as mentioned by LucaDC it is great for PDFs with custom fonts not installed locally if one has no need to edit the text as text (as long as upstream cairo doesn't switch to SVG fonts), secondly it is helpful to compare results with Inkscape's own PDF import wrt bugs e.g. with gradients and meshes (mainly for bug triage).
@theAdib: any chance you could review the patch proposed in https://bugs.launchpad.net/inkscape/+bug/1017123 ?
Cheers, V
2014-04-08 16:53 GMT+02:00 Martin Owens <doctormo@...400...>:
Hi Developers,
I've updated the page with details from Bryce's email back in December.
Also merged the status sections so it's easier to see where we are and where we're going:
http://inkscape.org/en/develop/next-release
Thanks to Johan, Tav and all for pointers and patches.
This looks really nice!
I can report on one of the TODO points: 'make distcheck' fails because the path to the extension tests is hardcoded instead of being relative to srcdir. However, automake says that using $(srcdir) in TESTS is broken for some reason. I'm testing a different solution right now.
Regards, Krzysztof
2014-04-08 20:50 GMT+02:00 Krzysztof Kosiński <tweenk.pl@...400...>:
I can report on one of the TODO points: 'make distcheck' fails because the path to the extension tests is hardcoded instead of being relative to srcdir. However, automake says that using $(srcdir) in TESTS is broken for some reason. I'm testing a different solution right now.
The different solution does not work, so we might need to come up with an ugly hack or disable extension tests in the released tarball.
Regards, Krzysztof
2014-04-08 21:23 GMT+02:00 Krzysztof Kosiński <tweenk.pl@...400...>:
2014-04-08 20:50 GMT+02:00 Krzysztof Kosiński <tweenk.pl@...400...>:
I can report on one of the TODO points: 'make distcheck' fails because the path to the extension tests is hardcoded instead of being relative to srcdir. However, automake says that using $(srcdir) in TESTS is broken for some reason. I'm testing a different solution right now.
The different solution does not work, so we might need to come up with an ugly hack or disable extension tests in the released tarball.
Regards, Krzysztof
Update on this: distcheck now correctly finds the test script, but one of the extension tests fails (render_barcode).
Regards, Krzysztof
On 2014-04-09 16:18 +0100, Krzysztof Kosiński wrote:
2014-04-08 21:23 GMT+02:00 Krzysztof Kosiński <tweenk.pl@...400...>:
2014-04-08 20:50 GMT+02:00 Krzysztof Kosiński <tweenk.pl@...400...>:
I can report on one of the TODO points: 'make distcheck' fails because the path to the extension tests is hardcoded instead of being relative to srcdir. However, automake says that using $(srcdir) in TESTS is broken for some reason. I'm testing a different solution right now.
The different solution does not work, so we might need to come up with an ugly hack or disable extension tests in the released tarball.
Regards, Krzysztof
Update on this: distcheck now correctly finds the test script, but one of the extension tests fails (render_barcode).
Just curious: the extensions tests are no longer run as part of the test suite with 'make check' with r13276 - is this to be expcted? Before, the result of the extensions test used to be included in the test suite summary.
Same with local builds, and on the build bots, e.g. Ubuntu 13.10: r13275 https://launchpadlibrarian.net/172244919/buildlog_ubuntu-saucy-amd64.inkscape-trunk_1%3A0.48%2Bdevel%2B13275%2B47~ubuntu13.10.1_UPLOADING.txt.gz r13276 https://launchpadlibrarian.net/172360701/buildlog_ubuntu-saucy-amd64.inkscape-trunk_1%3A0.48%2Bdevel%2B13276%2B47~ubuntu13.10.1_UPLOADING.txt.gz
Regards, V
2014-04-09 20:03 GMT+02:00 su_v <suv-sf@...58...>:
Just curious: the extensions tests are no longer run as part of the test suite with 'make check' with r13276 - is this to be expcted? Before, the result of the extensions test used to be included in the test suite summary.
The tests do run, but they are not visible in the summary, because they run as part of the "check-local" target. This is a workaround for a limitation in Automake. The log says that the following command is being run: ../../share/extensions/test/run-all-extension-tests
I have verified that "make check" will return an error if this script fails.
Regards, Krzysztof
On Wed, 2014-04-09 at 16:18 +0200, Krzysztof Kosiński wrote:
Update on this: distcheck now correctly finds the test script, but one of the extension tests fails (render_barcode).
The tests for render_barcode are working this end. Could you copy the error you're seeing?
I see the warning printed when the test makes a blank barcode, is this the error you see?
Martin,
2014-04-09 22:21 GMT+02:00 Martin Owens <doctormo@...400...>:
On Wed, 2014-04-09 at 16:18 +0200, Krzysztof Kosiński wrote:
Update on this: distcheck now correctly finds the test script, but one of the extension tests fails (render_barcode).
The tests for render_barcode are working this end. Could you copy the error you're seeing?
I see the warning printed when the test makes a blank barcode, is this the error you see?
This error only happens during "make distcheck", not "make check". I already found the cause - render_barcode.data is not included in the list of distributed files.
Regards, Krzysztof
make distcheck now passes (r13278).
I added render_barcode.data to EXTRA_DIST, fixed the generate_POTFILES.sh script (it did not exclude the files in po/POTFILES.skip) and regenerated POTFILES.in.
Regards, Krzysztof
On 8-4-2014 20:50, Krzysztof Kosiński wrote:
2014-04-08 16:53 GMT+02:00 Martin Owens <doctormo@...400...>:
Hi Developers,
I've updated the page with details from Bryce's email back in December.
Also merged the status sections so it's easier to see where we are and where we're going:
http://inkscape.org/en/develop/next-release
Thanks to Johan, Tav and all for pointers and patches.
This looks really nice!
+1 !
On Fri, Apr 04, 2014 at 12:32:27PM +0200, Martin Owens wrote:
We're having the Inkscape meeting here at LGM
I've put together a page on the website for the next release:
http://inkscape.org/en/develop/next-release/
I've included some details as well as some firm dates for the next release which I want us to hit. Bryce hasn't signed up to a fixed schedule yet, but it's time to get this nailed down and I think we're ready to get a release out now, let alone in a few months. So we should certainly be able to hit it.
What are your thoughts?
Can you change the 'x' into something that looks more like a checkbox '◻'?
Does the status of the items in the roadmap get loaded from wiki, or will I need to update status in both places? If the latter, what's the process for changing items to done (I fiddled with it on the site but wasn't obvious.)
Bryce
participants (7)
-
Bryce Harrington -
Johan Engelen -
Krzysztof Kosiński -
LucaDC -
Martin Owens -
su_v -
the Adib