[Pkg-x2go-devel] [X2go-dev] Git repos at git.x2go.org (Was: Packaging)

[Mike Gabriel]

Hi Morty, dear Heinz, dear Alex,

On Mo 21 Feb 2011 21:52:51 CET Moritz Strübe wrote:

> Hi there,
>
> I've noticed that all the repos at http://code.x2go.org/gitweb were
> renamed with a prefix _old_. What is the reason for this? Renaming repos
> really is not a nice thing to do, as all clones must be adjusted. And if
> you set up new repos the checksums will not match anymore, breaking the
> part of the cool features of git. What is the reason for doing so?
> I'm also still missing a road map. This would really help to avoid doing
> duplicate work. And if there is talk in the back ground: Please(!) make
> it public.
>
> Cheers
> Morty

First: the Git at code.x2go.org has so far not been officially  
announced on any channel. The main reason for this is (from my  
perspective) that I have had no definite confirmation from Heinz and  
Alex, yet, that they will really change over X2go development to a  
publically available Git based release model. From my point of view,  
there has been good will so far, but no definite: YES. That means:

   o upstream code is comitted into upstream Git and reflects the upstream
     development process (i.e. there are more commits than releases)
   o at some stages the upstream developers ask a release manager to tag a
     release
   o the release tagging informs distro packagers that there is a new upstream
     version of one of the X2go projects

The Git on code.x2go.org was already ,,nice'', but it's main flaw was  
the lack of history. Also: the lack of being able to extract the  
original tarball releases from the git directly. However, that shall  
be possible in the future.

In the run of meeting Heinz and Jonas in Zweibrücken and talking to  
Heinz on the phone later, a slightly different Git model has come up  
that I am preparing now for proposal.

I have asked Heinz and Alex internally for an opinion on the new  
model, but have not received a reply within the last week. I must  
confess that I explained the gains of the new structure only shorly

Thus my basic idea with the latest work on code.x2go.org was to show  
the new structure to the world and discuss the following advantages of  
upstream Git projects that:

  o contain a pristine-tar branch
  o contain a nearly complete history
    (that is as many of the older releases as possible) on the x2go-dev ML.
  o release numbers do not contain hyphens (''-'') anymore
  o all X2go projects have a a.b.c.d version number (major.minor.micro.nano(?))

Everything I do currently is reversible and in upstream we (Heinz,  
Alex, Mike) are still in the middle of a discussion process. There is  
not yet a consensus on how the Git will be used and there is no  
roadmap yet either. However, I urge everyone involved (and this not  
for the first time, but maybe the first time in public) to focus on  
that in the oncoming days and weeks before diving into new absorbing  
coding work. That is: I recommend to sharpen the tools first.

@Heinz+Alex: we have to get this to a definite state now. I feel  
myself getting gradually impatient about the sluggyness of this  
process. Please, contribute to this thread. My personal goal is that  
we have a definite result on X2go upstream git usage at the end of  
this discussion thread.

@Morty: thanks for re-addressing this topic!!!

Greets,
Mike



-- 

DAS-NETZWERKTEAM
mike gabriel, dorfstr. 27, 24245 barmissen
fon: +49 (4302) 281418, fax: +49 (4302) 281419

GnuPG Key ID 0xB588399B
mail: mike.gabriel at das-netzwerkteam.de, http://das-netzwerkteam.de

freeBusy:
https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 489 bytes
Desc: Digitale PGP-Unterschrift
URL: <http://lists.alioth.debian.org/pipermail/pkg-x2go-devel/attachments/20110221/0be20a33/attachment.pgp>