See this blog post about a Google Summer of Code project to create an
open source web portal for writing, editing and reviewing Mallard
documentation. The developer is aiming at mid-August for completion
which means it will be partly usable in July. I don't know how far
you've gotten in implementin
Hello, all.
I wanted to thank everyone who's helped so far with reporting and
fixing bugs in the manual. We really appreciate it!
Unfortunately, we've had a few new bugs slip in to the code in the
process. So here's a quick guide on how to commit code for our
manual:
1. We're commit our code a
On Wed, May 19, 2010 at 7:24 PM, Elizabeth Krumbach wrote:
> I'll close the poll 1 week from now and announce the meeting time, add
> it to fridge, etc.
The time for our meeting will be:
Monday, May 31, 2010 at 16:00:00 UTC time
http://timeanddate.com/worldclock/fixedtime.html?month=5&day=31&ye
Thanks for this guide. I have just started fixing bugs today and I have a
few questions. Each time you change a bug do you need to "commit and push"
or can you change multiple bugs and then "commit and push".
The command to run are when you make a change are:
cd ~/Projects/ubuntu-manual
make clean;
You can fix multiple bugs and then commit and push, yes. Just make sure you
include a commit phrase that has the bug numbers you've fixed, for example:
"Fixed bugs 50481, 28105, 50856"
On Wed, May 26, 2010 at 1:04 PM, Jason Cook wrote:
> Thanks for this guide. I have just started fixing bugs to
Hi Jason,
Yes you can fix multiple bugs and then commit/push, rather than doing so
after each bug. The commit operation will record any changes you have made
across the whole ubuntu-manual branch. Just make sure you list the bug
numbers you have addressed in the [comment] when you run bzr commit -
After fixing some bugs how can I re-release the manual? I have a bunch of
bugs assigned to me that have a "committed" fix but can't make them as
released yet.
___
Mailing list: https://launchpad.net/~ubuntu-manual
Post to : ubuntu-manual@lists.launchp
better yet, use bzr commit --fixed=lp: -m
> wrote:
> Hi Jason,
>
> Yes you can fix multiple bugs and then commit/push, rather than doing so
> after each bug. The commit operation will record any changes you have made
> across the whole ubuntu-manual branch. Just make sure you list the bug
> numbe
They stay fix committed until the next release, in this case, Lucid 2nd
edition :)
On Wed, May 26, 2010 at 1:35 PM, Jason Cook wrote:
> After fixing some bugs how can I re-release the manual? I have a bunch of
> bugs assigned to me that have a "committed" fix but can't make them as
> released ye
On Tue, May 25, 2010 at 8:35 PM, Jason Cook wrote:
> After fixing some bugs how can I re-release the manual? I have a bunch of
> bugs assigned to me that have a "committed" fix but can't make them as
> released yet.
We'll mark them as released when we release the next edition.
Thanks!
--Kevin
On Tue, May 25, 2010 at 9:28 AM, Jeremy Bicha wrote:
> See this blog post about a Google Summer of Code project to create an
> open source web portal for writing, editing and reviewing Mallard
> documentation. The developer is aiming at mid-August for completion
> which means it will be partly usa
11 matches
Mail list logo
