[Geany-devel] geany on github; why not?
lists.ban at xxxxx
Tue Oct 4 21:50:06 UTC 2011
Le 04/10/2011 23:37, Jiří Techet a écrit :
> I'm trying to get everything ready for the conversion and there are
> still a few points unresolved:
>> I have a few comments (and questions) myself:
>> 1. Some branch names should be renamed (e.g. Geany-0_19_1) because
>> they have the same name as tags and they are ambiguous when doing "git
>> checkout". Some naming scheme for stable branches should be invented.
> I was proposing to have two digit branches and three digit tags:
> Geany-0_19 - maintenance branch
> Geany-0_19_0 - tag
> Geany-0_19_1 - tag
> Geany-0_19_2 - tag
> Do you agree or do you prefer some different naming scheme?
I don't mind much, but it looks sensible since it quite follows current
scheme and is clear. So yes, I agree.
>> 3. I haven't found a merge point for the "dynamic-editor-menu" branch.
>> Has it been merged to trunk?
> Does anyone know? If not, I'd just delete this branch.
AFAIK it hasn't been merged, but I'm not sure the code it holds is still
relevant, although the idea looks interesting. Maybe Enrico or Nick
would know more?
>> 5. I kept the bs2 and sm branches in the repository but once the
>> migration is done, they should be cloned by their owners and should be
>> removed from the main repository.
> I can create official Geany repository without them and one clone that
> contains them so their authors can pick them after the conversion.
Seems sensible too, since not everybody will (need to) have write access
to the official repo, the branches should be in their author's clones.
However if one branch is ready yet, it may be not worth the effort of
removing and re-getting it? (honestly I don't really know the status of
these branches, my bad)
More information about the Devel