On Mon, Feb 6, 2012 at 11:04 AM, Drew Smathers
<email address hidden> wrote:
>
> Also any coaching on how to mark bugs etc (maybe a link to relevant
> documents) I would really appreciate.
I dont think there's anything in place for that yet...
And I've linked your bug to it. Feel free to file others as you see
them, and link them to that blueprint.
> I've used lp off and on and now I
> think I like it better than github/bitbucket.
I actually *really* like LP for managing tasks and bugs (and building
PPAs, etc.) but I have to say, that after using git for about 6 months
now, I have a hard time going back to bzr. git is sooo much faster and
I really like having all my branches maintained in a single
repo/working directory. It really simplifies my coding workflow.
But compared to svn or cvs pain, the bzr-git gap is a mere speck --
quite easy to live with.
On Mon, Feb 6, 2012 at 11:04 AM, Drew Smathers
<email address hidden> wrote:
>
> Also any coaching on how to mark bugs etc (maybe a link to relevant
> documents) I would really appreciate.
I dont think there's anything in place for that yet...
But I've just created a new blueprint for general EC2 improvements: /blueprints. launchpad. net/txaws/ +spec/ec2- improvements
https:/
And I've linked your bug to it. Feel free to file others as you see
them, and link them to that blueprint.
> I've used lp off and on and now I
> think I like it better than github/bitbucket.
I actually *really* like LP for managing tasks and bugs (and building
PPAs, etc.) but I have to say, that after using git for about 6 months
now, I have a hard time going back to bzr. git is sooo much faster and
I really like having all my branches maintained in a single
repo/working directory. It really simplifies my coding workflow.
But compared to svn or cvs pain, the bzr-git gap is a mere speck --
quite easy to live with.