[oe] TSC Meetings for the meeting of June
raj.khem at gmail.com
Wed Jun 9 19:37:18 CEST 2010
On Wed, Jun 9, 2010 at 9:53 AM, Philip Balister <philip at balister.org> wrote:
> On 06/09/2010 10:57 AM, Chris Larson wrote:
>> On Wed, Jun 9, 2010 at 6:53 AM, Frans Meulenbroeks<
>> fransmeulenbroeks at gmail.com> wrote:
>>> 2010/6/9 Holger Freyther<holger+oe at freyther.de<holger%2Boe at freyther.de>
>>>> We were carrying the org.openembedd.dev branch name from the monotone
>>>> era into the git era and the TSC was asked to consider renaming it to
>>>> 'master' which is the git default for the main development tree. Now the
>>>> actual change on the server will be minor what is of a bigger concern
>>>> are the existing users and documentation.
>>> Technically speaking I think we should have run an RFC for this before
>>> it was brought to the table of the TSC.
>>> Personally the org.openembedded.dev branch name does not bother me
>>> although I know master is the 'standard' git name.
>>> Afaik renaming does not really solve a problem.
>> Personally, I have to type it at least a few times a day, it gets old, and
>> think its time we ditched monotone remnants where we're able to do so.
> I'm with Chris. The name is long and annoying. It is time to drop the
> monotone/bitkeeper remnants.
yes I am also in favor of getting it simpler. Although I do have
bash_completion for git
still its annoying because there are more than one branch names that
start with org.openembedded.
>> I am not too sure how much this affects the current users. Actually I
>>> doubt if the change is bigger than the packages -> recipes renaming
>>> Isse is that if we do that we should make sure all relevant
>>> documentation is updated, otherwise we only create confusion (which
>>> might still creep up as people use old mailing list articles).
>>> Considering this, I am in favour of keeping things as they are.
>> If we implement this, I don't really see a problem doing it for the users:
>>> > c.) To ease this for existing users and to reduce the amount of
>>>> support org.openembedded.dev will track master and remains
>>>> available for a limited but long amount of time.
> Openembedded-devel mailing list
> Openembedded-devel at lists.openembedded.org
More information about the Openembedded-devel