Opened 12 years ago
Closed 7 years ago
#9831 closed task (fixed)
Release notes are hard to read
Reported by: | techtonik | Owned by: | nobody |
---|---|---|---|
Priority: | low | Milestone: | R1/beta1 |
Component: | Website/Trac | Version: | R1/alpha4.1 |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description
release_notes_r1alpha4.1.txt
included in .zip downloads contains overly long lines that are hard to read. This file is also can not be found in repository, so it is hard to patch.
The information about release notes location can be added to https://dev.haiku-os.org/wiki/ReleaseCookbook
Attachments (2)
Change History (16)
comment:1 by , 12 years ago
Component: | - General → Documentation |
---|---|
Owner: | changed from | to
comment:2 by , 12 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:4 by , 11 years ago
Milestone: | R1 → R1/beta1 |
---|
Bumping this to the next currently listed milestone as a reminder.
comment:5 by , 11 years ago
Milestone: | R1/beta1 → R1/alpha5 |
---|---|
Priority: | normal → blocker |
comment:6 by , 11 years ago
We could add http://trac-hacks.org/wiki/TracWikiPrintPlugin to our Trac to make it possible to download the wiki page with the HTML formatting.
comment:7 by , 10 years ago
Component: | Documentation → Website/Trac |
---|---|
Owner: | changed from | to
Priority: | blocker → low |
Indeed, this should be fixed by installing PrintPlugin that Adrien mentioned. Reassigning to Oliver so he can install that.
Also, I see no reason why this is a blocker. It doesn't prevent anyone from using Haiku and most sane editors have a word wrap option anyway.
comment:8 by , 10 years ago
Owner: | changed from | to
---|
Hm, I'm having a hard time following this discussion.
If the actual problem is a non-wrapped text file, why don't we hard-wrap it or use html instead?
comment:9 by , 10 years ago
I was assuming we wanted the file to be extracted from the trac wiki in some way. That makes it easy for everyone to edit it before the release, and easy to grab for packaging into the final release archive.
I'm fine with other solutions (HTML, hard-wrapped text file, StyledEdit document, whatever). But in that case we need to decide where to store the file and how it gets included in the release.
The trac plugin is a way to keep the source on the wiki and export as HTML. This sounded like a good solution when I started researching it, then I found plain Trac can't do it and it needs a plugin. I didn't say this was the best thing to do, more noting that I found that this is apparently the only solution to get clean html from our wiki page. Storing the file elsewhere is probably simpler.
comment:10 by , 10 years ago
Milestone: | R1/alpha5 → R1/beta1 |
---|
comment:12 by , 10 years ago
It could be put on Google docs.
Plus Haiku is entitled to the premium version of Google Apps for free.
Also I investigated using Alfresco CE for tracking GCI documentation tasks, but I felt it was overkill for that job. I still have my testing server up online for the next three weeks if anyone is intrested in playing around with it.
comment:13 by , 10 years ago
Type: | bug → task |
---|
Converting to a task, all we need to do is convert the release notes to HTML instead of using the txt export from the wiki directly. We'll do that when times come to publish the release.
by , 10 years ago
Attachment: | haiku-R1B1v1.odt added |
---|
R1B1 release notes, for whenever we actually get R1B1 out.
comment:14 by , 7 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
The new release notes are being written in the website repository, and look just fine in both plain text and HTML renderings. Closing as fixed.
Where do the release notes come from?