Yeah, I fully agree. It's overkill for Castle.
On Oct 14, 4:55 am, Daniel Hölbling <[email protected]> wrote:
> Mauricio,the branch strategy you outlined is very reasonable. Yet, it's a
> bit overcomplicated for us (well it comes from one of the biggest OSS
> projects out there).
>
> My thoughts:
>
> I believe we should have one master branch in a blessed repo stable at all
> time.
> Yet, in reality the Castle project was never really unstable. The only
> unstable thing was the todo-before-next-release list (that kept growing).
>
> Also I don't really know if we want to have a dedicated maintenance branch.
> Bugs are fixed and should be available immediately. Since we should review
> patches before pulling them to the master repo, having a dedicated branch
> for them waiting to get applied (again) seems like too bureaucratic.
>
> Yet, it makes sense if we are going to continue releasing maintenance
> updates to outdated versions (something I think nobody really wants to do).
> That would be
>
> For the next branch. Unless we now agree on a totally different release
> strategy, it makes no sense to have such a branch. (But I think we should
> think about changing the release strategy). Features get into the master as
> they come in. There is no formal Beta version of new feature releases, so it
> makes no sense to keep those out.
>
> That all said, Git branches are just insanely lightweight and very very easy
> to work with. So I believe every project leader should work the way he
> thinks (be it topic branches for everything etc) suits the project best, as
> long as /master remains stable and releases are tagged.
>
> greetings Daniel
>
> On Wed, Oct 14, 2009 at 8:59 AM, Fabian Schmied
> <[email protected]>wrote:
>
>
>
>
>
> > > Most of the committers already have github accounts, those who don't
> > > please create one: Krzysztof, hammett, Markus and maybe others.
>
> > Mine is "fschmied".
>
> > Fabian
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Castle Project Development List" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/castle-project-devel?hl=en
-~----------~----~----~----~------~----~------~--~---
