Opened 7 years ago

Closed 2 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:
Has a Patch: no Platform: All


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

Attachments (2)

haiku-R1A5v5.odt (58.7 KB ) - added by kallisti5 6 years ago.
R1A5v5 release notes
haiku-R1B1v1.odt (38.3 KB ) - added by kallisti5 5 years ago.
R1B1 release notes, for whenever we actually get R1B1 out.

Download all attachments as: .zip

Change History (16)

comment:1 by techtonik, 7 years ago

Component: - GeneralDocumentation
Owner: changed from nobody to nielx

comment:2 by nielx, 7 years ago

Owner: changed from nielx to mmadia
Status: newassigned

Where do the release notes come from?

comment:3 by mmadia, 7 years ago

The text version is grabbed from wiki:R1/Alpha4/ReleaseNotes via wget.

comment:4 by mmadia, 7 years ago

Milestone: R1R1/beta1

Bumping this to the next currently listed milestone as a reminder.

comment:5 by kallisti5, 6 years ago

Milestone: R1/beta1R1/alpha5
Priority: normalblocker

comment:6 by pulkomandy, 6 years ago

We could add to our Trac to make it possible to download the wiki page with the HTML formatting.

by kallisti5, 6 years ago

Attachment: haiku-R1A5v5.odt added

R1A5v5 release notes

comment:7 by waddlesplash, 6 years ago

Component: DocumentationWebsite/Trac
Owner: changed from mmadia to zooey
Priority: blockerlow

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 zooey, 6 years ago

Owner: changed from zooey to nobody

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 pulkomandy, 6 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 pulkomandy, 5 years ago

Milestone: R1/alpha5R1/beta1

comment:11 by Feveth, 5 years ago

So, should we do HTML? If so, I'm up for working on this.

comment:12 by richienyhus, 5 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.

Last edited 5 years ago by richienyhus (previous) (diff)

comment:13 by pulkomandy, 5 years ago

Type: bugtask

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 kallisti5, 5 years ago

Attachment: haiku-R1B1v1.odt added

R1B1 release notes, for whenever we actually get R1B1 out.

comment:14 by waddlesplash, 2 years ago

Resolution: fixed
Status: assignedclosed

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.

Note: See TracTickets for help on using tickets.