-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Convert worklog.adoc into formal, trackable issues. #22
Comments
I agree. That's definitely the plan. I should probably call the file BANKRUPT.adoc because the only reason it exists is because I haven't had a chance to file the issues (mostly from issues that I jotted down before I had a repository setup). |
I'll do it for you. We've seen what it did for the docs project, and this On Thu, 3 Mar 2016, 04:39 Dan Allen [email protected] wrote:
Sent from Mobile. |
That would be great. First, though, let me scan through it and mark items that should be transferred. Some of them I haven't committed to doing yet, and may have since decided not to do, so I want to downgrade those. I'll let you know when I push the update. |
All good. Ping me once ready. On Thu, 3 Mar 2016, 07:37 Dan Allen [email protected] wrote:
Sent from Mobile. |
I pushed an update that marks the first batch of candidate issues with a trailing asterisk. Some of the other items I'm not even sure what I meant exactly, or they aren't really a priority, so I didn't mark those. See https://github.com/opendevise/docbookrx/blob/master/WORKLOG.adoc#todo |
Carpe Diem. The bugs are now created @mojavelinux 👍 |
👍 |
Made some minor changes to structure to back up tracker bugs created in #22
Atomising the Worklog into discreet tasks may just allow some contributors to have a go at resolving them. And it will look great when you do a release: all those bugs!!! ;)
The text was updated successfully, but these errors were encountered: