"The next release" page: Update required
Hi everyone,
I only just noticed that Bryce had appended a new overview of the release process to his email to the dev mailing list about looking for volunteers, and that it looks quite different from the list we have on the website.
Would anyone have the time to update the English page (https://inkscape.org/en/develop/next-release/) and tell translators about the change?
This is Bryce's new list (I think we can leave 6. out, and don't need to specifically have the sub-item 'string freeze'):
"""""""""" # Period Tasks -------------------------------------------------------------------------------- √1. Open development. √ Implement new build system √ Begin switching packaging to use new build system
2. Chill. √ Development focuses on wrapping up √ Post inkscape-0.92-pre0.tar.gz √ Disable features that aren't finished √ Identify 'make distcheck' issues √ Identify remaining writing needed for Release Notes. √ Identify any release blocker bugs [scislac] √ Recruit Release Wardens for Hard Freeze
3. Frost. √ Only production-ready code committed to Mainline Finalize any major changes to platform packaging Inkscape must pass 'make distcheck' √ Finalize Release Notes except Known Issues Start an About Screen contest √ Post additional inkscape-0.92-pre*.tar.gz releases Packagers test creating pkgs of the -pre* releases
4. Freeze. √ Stable Branch is forked from Mainline √ Regular development resumes on Mainline. Only Release Wardens can commit to Stable Branch √ Cherrypick bug fixes from Mainline to Stable √ Complete any late work under advisement of Wardens Focus on release-critical bug fixing. String Freeze √ No further string changes allowed on Stable Branch. √ Translators work on translations. √ Finalize all extensions √ Finalize codebase translations Finalize about screen Finalize Known Issues section of Release Notes Finalize packaging scripts Post additional inkscape-0.92-pre*.tar.gz releases
5. Release. Post inkscape-0.92.tar.gz to website launchpad project page Post Windows build, MSI or EXE installer to website Post MacOSX build, dmg installer to website Make Debian build available in stable ppa or distribution archive Make Fedora build available in stable yum repo or distribution archive Post official announcements Plan 0.92.1+ release(s), if needed
6. Open development.
"""""""""""
If nobody else does, I can do it Tuesday night (UTC).
Regards, Maren
Hi Maren,
We’re Tuesday night!
The checks below are the very same on the Next Release page. There are some additional items and some missing items but I don’t think there’s a need for an update… Otherwise Bryce would have involved, wouldn’t he?
Sylvain
Le 10/10/2016 à 03:22, Maren Hachmann a écrit :
Hi everyone,
I only just noticed that Bryce had appended a new overview of the release process to his email to the dev mailing list about looking for volunteers, and that it looks quite different from the list we have on the website.
Would anyone have the time to update the English page (https://inkscape.org/en/develop/next-release/) and tell translators about the change?
This is Bryce's new list (I think we can leave 6. out, and don't need to specifically have the sub-item 'string freeze'):
""""""""""
# Period Tasks
√1. Open development. √ Implement new build system √ Begin switching packaging to use new build system
Chill. √ Development focuses on wrapping up √ Post inkscape-0.92-pre0.tar.gz √ Disable features that aren't finished √ Identify 'make distcheck' issues √ Identify remaining writing needed for Release Notes. √ Identify any release blocker bugs [scislac] √ Recruit Release Wardens for Hard Freeze
Frost. √ Only production-ready code committed to Mainline Finalize any major changes to platform packaging Inkscape must pass 'make distcheck' √ Finalize Release Notes except Known Issues Start an About Screen contest √ Post additional inkscape-0.92-pre*.tar.gz releases Packagers test creating pkgs of the -pre* releases
Freeze. √ Stable Branch is forked from Mainline √ Regular development resumes on Mainline. Only Release Wardens can commit to Stable Branch √ Cherrypick bug fixes from Mainline to Stable √ Complete any late work under advisement of Wardens Focus on release-critical bug fixing. String Freeze √ No further string changes allowed on Stable Branch. √ Translators work on translations. √ Finalize all extensions √ Finalize codebase translations Finalize about screen Finalize Known Issues section of Release Notes Finalize packaging scripts Post additional inkscape-0.92-pre*.tar.gz releases
Release. Post inkscape-0.92.tar.gz to website launchpad project page Post Windows build, MSI or EXE installer to website Post MacOSX build, dmg installer to website Make Debian build available in stable ppa or distribution archive Make Fedora build available in stable yum repo or distribution archive Post official announcements Plan 0.92.1+ release(s), if needed
Open development.
"""""""""""
If nobody else does, I can do it Tuesday night (UTC).
Regards, Maren
Am 11.10.2016 um 20:15 schrieb Sylvain Chiron:
Hi Maren,
We’re Tuesday night!
- You can safely assume that I do own a calendar and a clock, Sylvain.
The checks below are the very same on the Next Release page. There are some additional items and some missing items but I don’t think there’s a need for an update… Otherwise Bryce would have involved, wouldn’t he?
- I can't remember ever having been asked to update that page, no. It's our responsibility to do that, to prevent the website from being outdated.
As I suspect the subsequent updates will follow the below scheme, adapting the page now can save us work later, when there's more to do, due to the release and news etc. I prefer only changing a couple of checkmarks then to changing/rearranging a big part of the text, like I did now.
Regards, Maren
Sylvain
Le 10/10/2016 à 03:22, Maren Hachmann a écrit :
Hi everyone,
I only just noticed that Bryce had appended a new overview of the release process to his email to the dev mailing list about looking for volunteers, and that it looks quite different from the list we have on the website.
Would anyone have the time to update the English page (https://inkscape.org/en/develop/next-release/) and tell translators about the change?
This is Bryce's new list (I think we can leave 6. out, and don't need to specifically have the sub-item 'string freeze'):
""""""""""
# Period Tasks
√1. Open development. √ Implement new build system √ Begin switching packaging to use new build system
Chill. √ Development focuses on wrapping up √ Post inkscape-0.92-pre0.tar.gz √ Disable features that aren't finished √ Identify 'make distcheck' issues √ Identify remaining writing needed for Release Notes. √ Identify any release blocker bugs [scislac] √ Recruit Release Wardens for Hard Freeze
Frost. √ Only production-ready code committed to Mainline Finalize any major changes to platform packaging Inkscape must pass 'make distcheck' √ Finalize Release Notes except Known Issues Start an About Screen contest √ Post additional inkscape-0.92-pre*.tar.gz releases Packagers test creating pkgs of the -pre* releases
Freeze. √ Stable Branch is forked from Mainline √ Regular development resumes on Mainline. Only Release Wardens can commit to Stable Branch √ Cherrypick bug fixes from Mainline to Stable √ Complete any late work under advisement of Wardens Focus on release-critical bug fixing. String Freeze √ No further string changes allowed on Stable Branch. √ Translators work on translations. √ Finalize all extensions √ Finalize codebase translations Finalize about screen Finalize Known Issues section of Release Notes Finalize packaging scripts Post additional inkscape-0.92-pre*.tar.gz releases
Release. Post inkscape-0.92.tar.gz to website launchpad project page Post Windows build, MSI or EXE installer to website Post MacOSX build, dmg installer to website Make Debian build available in stable ppa or distribution archive Make Fedora build available in stable yum repo or distribution archive Post official announcements Plan 0.92.1+ release(s), if needed
Open development.
"""""""""""
If nobody else does, I can do it Tuesday night (UTC).
Regards, Maren
Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ Inkscape-docs mailing list Inkscape-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-docs
Sorry, Sylvain, for the harsh tone, you caught me on the wrong foot. I was actually hurrying all day to get this done now.
Regards, Maren
Am 11.10.2016 um 22:49 schrieb Maren Hachmann:
Am 11.10.2016 um 20:15 schrieb Sylvain Chiron:
Hi Maren,
We’re Tuesday night!
- You can safely assume that I do own a calendar and a clock, Sylvain.
The checks below are the very same on the Next Release page. There are some additional items and some missing items but I don’t think there’s a need for an update… Otherwise Bryce would have involved, wouldn’t he?
- I can't remember ever having been asked to update that page, no. It's
our responsibility to do that, to prevent the website from being outdated.
As I suspect the subsequent updates will follow the below scheme, adapting the page now can save us work later, when there's more to do, due to the release and news etc. I prefer only changing a couple of checkmarks then to changing/rearranging a big part of the text, like I did now.
Regards, Maren
Sylvain
Le 10/10/2016 à 03:22, Maren Hachmann a écrit :
Hi everyone,
I only just noticed that Bryce had appended a new overview of the release process to his email to the dev mailing list about looking for volunteers, and that it looks quite different from the list we have on the website.
Would anyone have the time to update the English page (https://inkscape.org/en/develop/next-release/) and tell translators about the change?
This is Bryce's new list (I think we can leave 6. out, and don't need to specifically have the sub-item 'string freeze'):
""""""""""
# Period Tasks
√1. Open development. √ Implement new build system √ Begin switching packaging to use new build system
Chill. √ Development focuses on wrapping up √ Post inkscape-0.92-pre0.tar.gz √ Disable features that aren't finished √ Identify 'make distcheck' issues √ Identify remaining writing needed for Release Notes. √ Identify any release blocker bugs [scislac] √ Recruit Release Wardens for Hard Freeze
Frost. √ Only production-ready code committed to Mainline Finalize any major changes to platform packaging Inkscape must pass 'make distcheck' √ Finalize Release Notes except Known Issues Start an About Screen contest √ Post additional inkscape-0.92-pre*.tar.gz releases Packagers test creating pkgs of the -pre* releases
Freeze. √ Stable Branch is forked from Mainline √ Regular development resumes on Mainline. Only Release Wardens can commit to Stable Branch √ Cherrypick bug fixes from Mainline to Stable √ Complete any late work under advisement of Wardens Focus on release-critical bug fixing. String Freeze √ No further string changes allowed on Stable Branch. √ Translators work on translations. √ Finalize all extensions √ Finalize codebase translations Finalize about screen Finalize Known Issues section of Release Notes Finalize packaging scripts Post additional inkscape-0.92-pre*.tar.gz releases
Release. Post inkscape-0.92.tar.gz to website launchpad project page Post Windows build, MSI or EXE installer to website Post MacOSX build, dmg installer to website Make Debian build available in stable ppa or distribution archive Make Fedora build available in stable yum repo or distribution archive Post official announcements Plan 0.92.1+ release(s), if needed
Open development.
"""""""""""
If nobody else does, I can do it Tuesday night (UTC).
Regards, Maren
Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ Inkscape-docs mailing list Inkscape-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-docs
Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ Inkscape-docs mailing list Inkscape-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-docs
Le 11/10/2016 à 22:58, Maren Hachmann a écrit :
Sorry, Sylvain, for the harsh tone, you caught me on the wrong foot. I was actually hurrying all day to get this done now.
It’s immediately mollified by your usual too-polite tone. I often lay a context before talking, and I like taking info that is the most related to right now, with an ironical tone. I was a bit surprised by your reply. I know you’re reliable, don’t worry. I often have a behavior that can look stressing, I think. Many geeks do.
Well, I’d say it’s a bit weird having changed the page like that from a mail without an explicit request for doing it; to me, you should have asked Bryce before. But you might know what you’re doing. -- Sylvain
participants (2)
-
Maren Hachmann -
Sylvain Chiron