On Thu, Aug 2, 2012 at 3:37 AM, Ken Dreyer ktdre...@ktdreyer.com wrote:
On Wed, Aug 1, 2012 at 4:17 AM, dpwrussell r...@dpwrussell.com wrote:
I see that there is the concept of versioning for some time now in
Gitorious, but all the installation instructions I have seen involve a
checkout
On Thu, Aug 2, 2012 at 3:37 AM, Ken Dreyer ktdre...@ktdreyer.com wrote:
Speaking as a packager, even if we didn't have backports and multiple
supported branches, it would be cool if Gitorious AS cut new versions
a bit more often. If that were the case, who knows, we might get a
step closer to
Thanks, I discovered I was in fact on 2.2.1 and could just enable
private repositories.
--
To post to this group, send email to gitorious@googlegroups.com
To unsubscribe from this group, send email to
gitorious+unsubscr...@googlegroups.com
I see that there is the concept of versioning for some time now in
Gitorious, but all the installation instructions I have seen involve a
checkout from mainline (If versioning is active I'd have expected a
checkout of a certain version branch). I've spent ages looking, but I can't
find out
On Wed, Aug 1, 2012 at 4:17 AM, dpwrussell r...@dpwrussell.com wrote:
I see that there is the concept of versioning for some time now in
Gitorious, but all the installation instructions I have seen involve a
checkout from mainline (If versioning is active I'd have expected a checkout
of a
So, please, take a look at ditz: http://ditz.rubyforge.org/
It's ruby.
It has plugable system.
It offers UI.
And it's a distributed issue tracking.
I have looked at it, and I find it very interesting. If memory serves me
right, I think the missing piece in Ditz was the UI. But that can be
2011/7/5 Christian Johansen christ...@cjohansen.no:
As for the discussion on issue tracking and Gitorious in general: I agree
that if/when issue tracking becomes a part of Gitorious (pluggable in some
way) - i.e. something we offer projects hosted with us - shipping something
which is
I'm impressed! One just probably need a bugs branch to get things
working and gitorious can look into this and show issues related to the
repo (or project if needed). Thanks for the pointer.
On 05/07/2011 16:53, Guilhem Bonnefille wrote:
2011/7/5 Christian Johansenchrist...@cjohansen.no:
As
I don't see any advantage in having a distributed issue tracker, maybe there
are some, but I think issue tracking is a central and unique service. You
don't want (at least I don't see a reason for) QA, testing and management
to have a clone of your repositories for adding bug reports. And you
2011/7/3 Rodrigo Rosenfeld Rosas rr.ro...@gmail.com:
Then, I would like to start a discussion of a feature I always missed in
Gitorious. That discussion is also in alignment with the recent concerns
about Gitorious versioning.
Mailing list are ineffective as an issue tracking system and
Em 04-07-2011 09:43, Guilhem Bonnefille escreveu:
2011/7/3 Rodrigo Rosenfeld Rosasrr.ro...@gmail.com:
Then, I would like to start a discussion of a feature I always missed in
Gitorious. That discussion is also in alignment with the recent concerns
about Gitorious versioning.
Mailing list are
Em 04-07-2011 13:27, Guilhem Bonnefille escreveu:
2011/7/4 Rodrigo Rosenfeld Rosasrr.ro...@gmail.com:
Em 04-07-2011 09:43, Guilhem Bonnefille escreveu:
2011/7/3 Rodrigo Rosenfeld Rosasrr.ro...@gmail.com:
Then, I would like to start a discussion of a feature I always missed in
Gitorious. That
Hi there!
First of all, since I'm moving my job I'm using my free time and energy
focusing on this change, so I'm delaying the OpenID test writing for
now, sorry.
Then, I would like to start a discussion of a feature I always missed in
Gitorious. That discussion is also in alignment with
13 matches
Mail list logo
