1.) Keep existing stable naming scheme
2.) Decide a few simple rules for "namespacing" experimental/feature
work
Does that sound right?
Hi Severin,
I saw the updates you have made to the guide lines. I have some more
thoughts now that Jeff has created a branch using these guidelines.
> 1.) Keep existing stable naming scheme
> 2.) Decide a few simple rules for "namespacing" experimental/feature
> work
>
> Does that sound right?
Sounds great. And put it here:
http://wiki.eclipse.org/Linux_Tools_Project/Git
Andrew
___
linuxtoo
- Original Message -
>
> >> Thanks for proposing this, Severin. In general I like it. My
> >> only
> >> concern is the difference between features and tags for releases.
> >> Will
> >> people be confused by released/{stable-,}0.9 being the maintenance
> >> branch for 0.9 micro releases?
Thanks for proposing this, Severin. In general I like it. My only
concern is the difference between features and tags for releases. Will
people be confused by released/{stable-,}0.9 being the maintenance
branch for 0.9 micro releases?
[...]
Having said that, keeping "stable-x" branches an
* Severin Gehwolf [2011-11-16 09:34]:
> On Mon, 2011-11-14 at 09:29 -0500, Andrew Overholt wrote:
> > * Severin Gehwolf [2011-11-09 10:13]:
> > > 2. Name-space maintenance branches with prefix "released/"
>
> [...]
>
> > My only concern is the difference between features and tags for
> > r
On Mon, 2011-11-14 at 09:29 -0500, Andrew Overholt wrote:
> Hi,
>
> * Severin Gehwolf [2011-11-09 10:13]:
> > 2. Name-space maintenance branches with prefix "released/"
> >
> > [...]
> >
> > What do you think?
>
> Thanks for proposing this, Severin. In general I like it. My only
> conce
Hi,
* Severin Gehwolf [2011-11-09 10:13]:
> 2. Name-space maintenance branches with prefix "released/"
>
> [...]
>
> What do you think?
Thanks for proposing this, Severin. In general I like it. My only
concern is the difference between features and tags for releases. Will
people be con
- Original Message -
> >
> > 1. Branch "master" remains the main development tree.
> > 2. Name-space maintenance branches with prefix "released/"
> > 3. Name-space shared feature branches with prefix "features/"
>
> > The benefits of this would be to encourage collaboratio
>
> 1. Branch "master" remains the main development tree.
> 2. Name-space maintenance branches with prefix "released/"
> 3. Name-space shared feature branches with prefix "features/"
> The benefits of this would be to encourage collaboration on
> experimental
> features and make t
