Re: 3.4 Release Notes
On Tue, Mar 06, 2012 at 01:31:41PM +0100, Andre Klapper wrote: @fpeters: Could you please set up http://library.gnome.org/misc/release-notes/3.4/ with password protection? To get in: gnome / 3.4 Please remember: it is all lies until the password protection has been removed (not kidding, I've made huge mistakes the one time I helped). Also had issues getting above site to automatically update again. I really hope it has been resolved, but not sure. I've mentioned in the release candidate tarballs due email that maintainers should have a look at the release notes. Hopefully they do. -- Regards, Olav -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
Re: 3.4 Release Notes
On Thu, Mar 15, 2012 at 12:03:43AM +0100, Andre Klapper wrote: On Wed, 2012-03-14 at 15:50 -0700, Sriram Ramkrishna wrote: We're pretty much out of time for this. We should really have a draft of the release notes finished already. I'm busy working on them using the existing infrastructure. Thanks for your help, Allan! Let me know if you need help.. I can help edit, or even add content. Just point me at a task and I'll try to help. Oh, it's easy and everybody is welcome: 1) git clone ssh://developern...@git.gnome.org/git/release-notes 2) cd release-notes 3) git checkout -b gnome-3-4 origin/gnome-3-4 4) cd help/C/ 5) grep -r TODO . 6) hack away on your favorite TODO items 7) yelp release-notes.xml // to check for syntax errors 7) git commit -m Fixed it all! -a then after 7/8: 9) git push if 9) fails, then git pull -r, then git push again Please focus on the user btw. Write for the users point of view. They might like focus-follows-mouse, etc. -- Regards, Olav -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
Re: 3.4 Release Notes
On Fri, Mar 9, 2012 at 3:53 PM, Vinicius Depizzol vdepiz...@gmail.com wrote: On Thu, Mar 8, 2012 at 18:53, Sriram Ramkrishna s...@ramkrishna.me wrote: My main objection would be translation. One of the problems is that I would like to see our content/news/release notes translated so that we can have greater coverage. I feel that english makes us somewhat limited. We can have WordPress content translated and integrated with damned-lies with the plugin I developed during the last Summer of Code[1]. I'm in contact with Claude Paroz (damned-lies maintainer) and Andrea Veri (sysadmin) to get a testing version of it running ASAP. [1] http://git.gnome.org/browse/gnome-web-wppo We're pretty much out of time for this. We should really have a draft of the release notes finished already. I'm busy working on them using the existing infrastructure. It will be great to have gnome.org translatable anyway, of course, and I really hope that we can use the site for the 3.6 release notes. Allan -- IRC: aday on irc.gnome.org Blog: http://afaikblog.wordpress.com/ -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
Re: 3.4 Release Notes
On Wed, Mar 14, 2012 at 3:48 PM, Allan Day allanp...@gmail.com wrote: On Fri, Mar 9, 2012 at 3:53 PM, Vinicius Depizzol vdepiz...@gmail.com wrote: On Thu, Mar 8, 2012 at 18:53, Sriram Ramkrishna s...@ramkrishna.me wrote: My main objection would be translation. One of the problems is that I would like to see our content/news/release notes translated so that we can have greater coverage. I feel that english makes us somewhat limited. We can have WordPress content translated and integrated with damned-lies with the plugin I developed during the last Summer of Code[1]. I'm in contact with Claude Paroz (damned-lies maintainer) and Andrea Veri (sysadmin) to get a testing version of it running ASAP. [1] http://git.gnome.org/browse/gnome-web-wppo We're pretty much out of time for this. We should really have a draft of the release notes finished already. I'm busy working on them using the existing infrastructure. It will be great to have gnome.org translatable anyway, of course, and I really hope that we can use the site for the 3.6 release notes. Let me know if you need help.. I can help edit, or even add content. Just point me at a task and I'll try to help. sri Allan -- IRC: aday on irc.gnome.org Blog: http://afaikblog.wordpress.com/ -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
Re: 3.4 Release Notes
On Wed, 2012-03-14 at 15:50 -0700, Sriram Ramkrishna wrote: We're pretty much out of time for this. We should really have a draft of the release notes finished already. I'm busy working on them using the existing infrastructure. Thanks for your help, Allan! Let me know if you need help.. I can help edit, or even add content. Just point me at a task and I'll try to help. Oh, it's easy and everybody is welcome: 1) git clone ssh://developern...@git.gnome.org/git/release-notes 2) cd release-notes 3) git checkout -b gnome-3-4 origin/gnome-3-4 4) cd help/C/ 5) grep -r TODO . 6) hack away on your favorite TODO items 7) yelp release-notes.xml // to check for syntax errors 7) git commit -m Fixed it all! -a Simple proofreading or adding screenshots is also welcome. :) andre -- mailto:ak...@gmx.net | failed http://blogs.gnome.org/aklapper -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
Re: 3.4 Release Notes
On Wed, Mar 14, 2012 at 4:03 PM, Andre Klapper ak...@gmx.net wrote: On Wed, 2012-03-14 at 15:50 -0700, Sriram Ramkrishna wrote: We're pretty much out of time for this. We should really have a draft of the release notes finished already. I'm busy working on them using the existing infrastructure. Thanks for your help, Allan! Let me know if you need help.. I can help edit, or even add content. Just point me at a task and I'll try to help. Oh, it's easy and everybody is welcome: 1) git clone ssh://developern...@git.gnome.org/git/release-notes 2) cd release-notes 3) git checkout -b gnome-3-4 origin/gnome-3-4 4) cd help/C/ 5) grep -r TODO . 6) hack away on your favorite TODO items 7) yelp release-notes.xml // to check for syntax errors 7) git commit -m Fixed it all! -a Simple proofreading or adding screenshots is also welcome. :) andre Thanks, Andre. I'll work on something tonight! -- mailto:ak...@gmx.net | failed http://blogs.gnome.org/aklapper -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
Re: 3.4 Release Notes
On Thu, 2012-03-08 at 19:59 +, Allan Day wrote: On Wed, Mar 7, 2012 at 10:25 PM, Sriram Ramkrishna s...@ramkrishna.me wrote: On Wed, Mar 7, 2012 at 1:08 PM, Andre Klapper ak...@gmx.net wrote: I was thinking of switching from Docbook to Mallard for 3.6 (I didn't have time to prepare this for 3.4 already). The advantages of GNOME 3 page style are unclear to me currently, Advantages of moving over to using Wordpress for the release notes (that I can think of): 1. The notes will be on gnome.org rather than under library.gnome.org/misc (why are the notes for our new release in a 'library'? why are they 'miscellaneous'?) 2. Avoid the bookishness of the format (sub-headings everywhere, boxes of links interrupting the flow of the document), which is rather stilted. 3. Allow embedding of richer media, such as lightboxes, image galleries and videos. 4. Allow flexible design, facilitating a more stylish and attractive layout. 5. Allow division of the notes into separate pages, rather than being a single *huge* page. Apart from point 1 and maybe partially point 4: Isn't this all also fixable by just switching from Docbook to Mallard? :) andre -- mailto:ak...@gmx.net | failed http://blogs.gnome.org/aklapper -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
Re: 3.4 Release Notes
On 03/09/2012 11:17 AM, Andre Klapper wrote: Apart from point 1 and maybe partially point 4: Isn't this all also fixable by just switching from Docbook to Mallard? :) That will only happen for 3.6 right? Is there anything we can do with the docbook format css-wise to make it look and behave nicer for this release? - Andreas -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
Re: 3.4 Release Notes
Go Vinicius! Christy On Fri, Mar 9, 2012 at 7:53 AM, Vinicius Depizzol vdepiz...@gmail.comwrote: On Thu, Mar 8, 2012 at 18:53, Sriram Ramkrishna s...@ramkrishna.me wrote: My main objection would be translation. One of the problems is that I would like to see our content/news/release notes translated so that we can have greater coverage. I feel that english makes us somewhat limited. We can have WordPress content translated and integrated with damned-lies with the plugin I developed during the last Summer of Code[1]. I'm in contact with Claude Paroz (damned-lies maintainer) and Andrea Veri (sysadmin) to get a testing version of it running ASAP. [1] http://git.gnome.org/browse/gnome-web-wppo -- Vinicius -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
Re: 3.4 Release Notes
Oh, great! That is perfect. In fact Andrea did mention thus to me on irc. I can help here as well if you need something going. Sri On Mar 9, 2012 2:54 PM, Vinicius Depizzol vdepiz...@gmail.com wrote: On Thu, Mar 8, 2012 at 18:53, Sriram Ramkrishna s...@ramkrishna.me wrote: My main objection would be translation. One of the problems is that I would like to see our content/news/release notes translated so that we can have greater coverage. I feel that english makes us somewhat limited. We can have WordPress content translated and integrated with damned-lies with the plugin I developed during the last Summer of Code[1]. I'm in contact with Claude Paroz (damned-lies maintainer) and Andrea Veri (sysadmin) to get a testing version of it running ASAP. [1] http://git.gnome.org/browse/gnome-web-wppo -- Vinicius -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
Re: 3.4 Release Notes
On Wed, Mar 7, 2012 at 10:41 AM, Dave Neary dne...@gnome.org wrote: Hi, On 03/07/2012 10:28 AM, Allan Day wrote: Now, a question. We typically keep the release notes secret until the release itself. At least one member of the press has told me that this makes it quite difficult for him to cover GNOME releases, since there is little information about the release until it is actually out. Is there a way we can disclose what will be in the release prior to release day itself? Maybe the release notes could be made public with the release candidate, for example? It would be really useful to know what other projects do in this regard. I'm all in favour of working on the release notes in a publicly accessible repository, even in the wiki (although adding pretty screenshots is not easy in the wiki). We can of course avoid publicising the URL until the release comes out, but having the notes developed in the open will allow people to get a head-start, as you point out Allan. Cheers, Dave. That might help. However, I feel that we need something a bit more proactive to get the word out to journalists. We might struggle to do it for this release, but having a separate press release and some kind of release notes for the release candidate could be a good way to get the word out. Allan -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
Re: 3.4 Release Notes
On Thu, Mar 8, 2012 at 10:47 AM, Andre Klapper ak...@gmx.net wrote: On Thu, 2012-03-08 at 09:59 +, Allan Day wrote: We might struggle to do it for this release, but having a separate press release and some kind of release notes for the release candidate could be a good way to get the word out. Release Candidate = two weeks before the release. Oh? The schedule [1] says it's one week before the release. String freeze is three weeks before the release and we are always late starting with writing release notes and finding volunteers so rather unlikely. It was just an idea. But I don't see why we couldn't aim to have *something* (it doesn't have to be the full, finished release notes) ready a week in advance. Allan [1] https://live.gnome.org/ThreePointThree -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
Re: 3.4 Release Notes
On Thu, 2012-03-08 at 10:57 +, Allan Day wrote: On Thu, Mar 8, 2012 at 10:47 AM, Andre Klapper ak...@gmx.net wrote: On Thu, 2012-03-08 at 09:59 +, Allan Day wrote: We might struggle to do it for this release, but having a separate press release and some kind of release notes for the release candidate could be a good way to get the word out. Release Candidate = two weeks before the release. Oh? The schedule [1] says it's one week before the release. Argh. So much for my reading skills. :) Sometimes it's one week and sometimes it's two weeks, also depends on external influences on the schedule (releases vs public holidays; no freezes yet when conferences like GUADEC or hackfests take place; etc). It was just an idea. But I don't see why we couldn't aim to have *something* (it doesn't have to be the full, finished release notes) ready a week in advance. I agree, but I'm afraid that reality (and its manpower) will bite us. (We also dream of documentation freezes for translators. :-) andre -- mailto:ak...@gmx.net | failed http://blogs.gnome.org/aklapper -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
Re: 3.4 Release Notes
On Thu, Mar 8, 2012 at 13:10, Andre Klapper ak...@gmx.net wrote: On Thu, 2012-03-08 at 10:57 +, Allan Day wrote: On Thu, Mar 8, 2012 at 10:47 AM, Andre Klapper ak...@gmx.net wrote: On Thu, 2012-03-08 at 09:59 +, Allan Day wrote: We might struggle to do it for this release, but having a separate press release and some kind of release notes for the release candidate could be a good way to get the word out. Release Candidate = two weeks before the release. Oh? The schedule [1] says it's one week before the release. Argh. So much for my reading skills. :) Sometimes it's one week and sometimes it's two weeks, also depends on external influences on the schedule (releases vs public holidays; no freezes yet when conferences like GUADEC or hackfests take place; etc). It was just an idea. But I don't see why we couldn't aim to have *something* (it doesn't have to be the full, finished release notes) ready a week in advance. I agree, but I'm afraid that reality (and its manpower) will bite us. (We also dream of documentation freezes for translators. :-) Yes! :-) -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
Re: 3.4 Release Notes
On Thu, March 8, 2012 4:59 am, Allan Day wrote: On Wed, Mar 7, 2012 at 10:41 AM, Dave Neary dne...@gnome.org wrote: Hi, On 03/07/2012 10:28 AM, Allan Day wrote: Now, a question. We typically keep the release notes secret until the release itself. At least one member of the press has told me that this makes it quite difficult for him to cover GNOME releases, since there is little information about the release until it is actually out. Is there a way we can disclose what will be in the release prior to release day itself? Maybe the release notes could be made public with the release candidate, for example? It would be really useful to know what other projects do in this regard. I'm all in favour of working on the release notes in a publicly accessible repository, even in the wiki (although adding pretty screenshots is not easy in the wiki). We can of course avoid publicising the URL until the release comes out, but having the notes developed in the open will allow people to get a head-start, as you point out Allan. Cheers, Dave. That might help. However, I feel that we need something a bit more proactive to get the word out to journalists. We might struggle to do it for this release, but having a separate press release and some kind of release notes for the release candidate could be a good way to get the word out. We've talked about putting together a list of journalists to contact in the past (I think that was Jos's idea). Perhaps this is the time we should put this together and try to contact folks? We could point to the in progress notes, which might prompt them to ask targeted questions that could be easier to address... karen -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
Re: 3.4 Release Notes
On Wed, Mar 7, 2012 at 10:25 PM, Sriram Ramkrishna s...@ramkrishna.me wrote: On Wed, Mar 7, 2012 at 1:08 PM, Andre Klapper ak...@gmx.net wrote: I was thinking of switching from Docbook to Mallard for 3.6 (I didn't have time to prepare this for 3.4 already). The advantages of GNOME 3 page style are unclear to me currently, Advantages of moving over to using Wordpress for the release notes (that I can think of): 1. The notes will be on gnome.org rather than under library.gnome.org/misc (why are the notes for our new release in a 'library'? why are they 'miscellaneous'?) 2. Avoid the bookishness of the format (sub-headings everywhere, boxes of links interrupting the flow of the document), which is rather stilted. 3. Allow embedding of richer media, such as lightboxes, image galleries and videos. 4. Allow flexible design, facilitating a more stylish and attractive layout. 5. Allow division of the notes into separate pages, rather than being a single *huge* page. however I would first have to know what markup language this move would imply, Wordpress reduces the need for markup. The only markup you need is html for formatting and embedding media, plus for bits of fancier page layout. plus if anybody would be actually willing to prepare this move. Actually writing the notes and doing the markup would be less work than with Docbook or Mallard, so in that respect we'd save time and effort. However, we would need a bit of extra help on the web development side if we wanted to make the notes look really nice. I'm interested in this as well. As Shaun noted about translations I would like to see this translated in as many languages as possible. We'll need to start on this soon. Most of the pieces are in place to make gnome.org translatable using the standard GNOME infrastructure. We just need to hook it up to damn lies [1]. I've spoken to Vinicius and he's confident that we can have it ready in time to get the release notes translated. Allan [1] https://bugzilla.gnome.org/show_bug.cgi?id=671647 -- IRC: aday on irc.gnome.org Blog: http://afaikblog.wordpress.com/ -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
Re: 3.4 Release Notes
On Thu, Mar 8, 2012 at 11:59 AM, Allan Day allanp...@gmail.com wrote: On Wed, Mar 7, 2012 at 10:25 PM, Sriram Ramkrishna s...@ramkrishna.me wrote: On Wed, Mar 7, 2012 at 1:08 PM, Andre Klapper ak...@gmx.net wrote: I was thinking of switching from Docbook to Mallard for 3.6 (I didn't have time to prepare this for 3.4 already). The advantages of GNOME 3 page style are unclear to me currently, Advantages of moving over to using Wordpress for the release notes (that I can think of): My main objection would be translation. One of the problems is that I would like to see our content/news/release notes translated so that we can have greater coverage. I feel that english makes us somewhat limited. At least, let's agree that if we do it on wordpress that we have it in English and Spanish. sri 1. The notes will be on gnome.org rather than under library.gnome.org/misc (why are the notes for our new release in a 'library'? why are they 'miscellaneous'?) 2. Avoid the bookishness of the format (sub-headings everywhere, boxes of links interrupting the flow of the document), which is rather stilted. 3. Allow embedding of richer media, such as lightboxes, image galleries and videos. 4. Allow flexible design, facilitating a more stylish and attractive layout. 5. Allow division of the notes into separate pages, rather than being a single *huge* page. however I would first have to know what markup language this move would imply, Wordpress reduces the need for markup. The only markup you need is html for formatting and embedding media, plus for bits of fancier page layout. plus if anybody would be actually willing to prepare this move. Actually writing the notes and doing the markup would be less work than with Docbook or Mallard, so in that respect we'd save time and effort. However, we would need a bit of extra help on the web development side if we wanted to make the notes look really nice. I'm interested in this as well. As Shaun noted about translations I would like to see this translated in as many languages as possible. We'll need to start on this soon. Most of the pieces are in place to make gnome.org translatable using the standard GNOME infrastructure. We just need to hook it up to damn lies [1]. I've spoken to Vinicius and he's confident that we can have it ready in time to get the release notes translated. Allan [1] https://bugzilla.gnome.org/show_bug.cgi?id=671647 -- IRC: aday on irc.gnome.org Blog: http://afaikblog.wordpress.com/ -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
Re: 3.4 Release Notes
On Thu, Mar 8, 2012 at 23:53, Sriram Ramkrishna s...@ramkrishna.me wrote: On Thu, Mar 8, 2012 at 11:59 AM, Allan Day allanp...@gmail.com wrote: On Wed, Mar 7, 2012 at 10:25 PM, Sriram Ramkrishna s...@ramkrishna.me wrote: On Wed, Mar 7, 2012 at 1:08 PM, Andre Klapper ak...@gmx.net wrote: I was thinking of switching from Docbook to Mallard for 3.6 (I didn't have time to prepare this for 3.4 already). The advantages of GNOME 3 page style are unclear to me currently, Advantages of moving over to using Wordpress for the release notes (that I can think of): My main objection would be translation. One of the problems is that I would like to see our content/news/release notes translated so that we can have greater coverage. I feel that english makes us somewhat limited. At least, let's agree that if we do it on wordpress that we have it in English and Spanish. IMHO translation is essential for introductions, presentations, overviews, news, release notes and such. These are the documents that can reach people who do not know/use GNOME. There should not be language barriers for potential new adopters. I like all the WP benefits listed, though it would be a severe regression to leave translation behind. So, what does supporting translation implies? Is it about 1. getting the right plugin https://www.google.com/search?q=wordpress+multilingual 2. interfacing with DL workflow (po files, git) Or? sri 1. The notes will be on gnome.org rather than under library.gnome.org/misc (why are the notes for our new release in a 'library'? why are they 'miscellaneous'?) 2. Avoid the bookishness of the format (sub-headings everywhere, boxes of links interrupting the flow of the document), which is rather stilted. 3. Allow embedding of richer media, such as lightboxes, image galleries and videos. 4. Allow flexible design, facilitating a more stylish and attractive layout. 5. Allow division of the notes into separate pages, rather than being a single *huge* page. however I would first have to know what markup language this move would imply, Wordpress reduces the need for markup. The only markup you need is html for formatting and embedding media, plus for bits of fancier page layout. plus if anybody would be actually willing to prepare this move. Actually writing the notes and doing the markup would be less work than with Docbook or Mallard, so in that respect we'd save time and effort. However, we would need a bit of extra help on the web development side if we wanted to make the notes look really nice. I'm interested in this as well. As Shaun noted about translations I would like to see this translated in as many languages as possible. We'll need to start on this soon. Most of the pieces are in place to make gnome.org translatable using the standard GNOME infrastructure. We just need to hook it up to damn lies [1]. I've spoken to Vinicius and he's confident that we can have it ready in time to get the release notes translated. Allan [1] https://bugzilla.gnome.org/show_bug.cgi?id=671647 -- IRC: aday on irc.gnome.org Blog: http://afaikblog.wordpress.com/ -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
Re: 3.4 Release Notes
Thanks for kicking this off, Andre! I'll be sure to chip in where I can. My last blog post [1] might be useful, too. Now, a question. We typically keep the release notes secret until the release itself. At least one member of the press has told me that this makes it quite difficult for him to cover GNOME releases, since there is little information about the release until it is actually out. Is there a way we can disclose what will be in the release prior to release day itself? Maybe the release notes could be made public with the release candidate, for example? It would be really useful to know what other projects do in this regard. One other thing that we've spoken about is moving away from the library/documentation format for the release notes. Hosting them directly on gnome.org would give us a lot more freedom in terms of how we present the notes (so they would look more like the GNOME 3 page [2], for example). Allan [1] http://afaikblog.wordpress.com/2012/02/28/looking-forward-to-gnome-3-4/ [2] http://www.gnome.org/gnome-3/ On Tue, Mar 6, 2012 at 12:31 PM, Andre Klapper ak...@gmx.net wrote: I've committed an initial stub for the 3.4 release notes: http://git.gnome.org/browse/release-notes/commit/?h=gnome-3-4id=87991dfb2c52704db6481ab3c3d78d7dc73d22e7 The required steps are (hopefully) documented on https://live.gnome.org/AndreKlapper/WritingReleaseNotes @fpeters: Could you please set up http://library.gnome.org/misc/release-notes/3.4/ with password protection? andre -- mailto:ak...@gmx.net | failed http://blogs.gnome.org/aklapper -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
Re: 3.4 Release Notes
On Wed, Mar 7, 2012 at 4:28 AM, Allan Day allanp...@gmail.com wrote: Is there a way we can disclose what will be in the release prior to release day itself? Maybe the release notes could be made public with the release candidate, for example? It would be really useful to know what other projects do in this regard. Don't the feature pages serve this need, at least partially ? Of course, before we advertise them as 'this is whats coming', we need to weed out the features that did not make it in the end, and make sure the remaining ones reflect somewhat acurately what was actually done. -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
Re: 3.4 Release Notes
On Wed, 2012-03-07 at 09:28 +, Allan Day wrote: One other thing that we've spoken about is moving away from the library/documentation format for the release notes. Hosting them directly on gnome.org would give us a lot more freedom in terms of how we present the notes (so they would look more like the GNOME 3 page [2], for example). How would we handle translations? -- Shaun -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
Re: 3.4 Release Notes
On Wed, 2012-03-07 at 09:28 +, Allan Day wrote: Now, a question. We typically keep the release notes secret until the release itself. At least one member of the press has told me that this makes it quite difficult for him to cover GNOME releases, since there is little information about the release until it is actually out. Is there a way we can disclose what will be in the release prior to release day itself? Maybe the release notes could be made public with the release candidate, for example? It would be really useful to know what other projects do in this regard. I don't have any opinion on this. In the past we've been having a password protection, but we could drop that and add a This is not the final version, things might be wrong and change header - same as on https://live.gnome.org/ThreePointThree/ReleaseNotes . One other thing that we've spoken about is moving away from the library/documentation format for the release notes. Hosting them directly on gnome.org would give us a lot more freedom in terms of how we present the notes What would you like to see that Mallard cannot do? (so they would look more like the GNOME 3 page [2], for example). I was thinking of switching from Docbook to Mallard for 3.6 (I didn't have time to prepare this for 3.4 already). The advantages of GNOME 3 page style are unclear to me currently, however I would first have to know what markup language this move would imply, plus if anybody would be actually willing to prepare this move. andre -- mailto:ak...@gmx.net | failed http://blogs.gnome.org/aklapper -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
