[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: RE: [mylyn-dev] code freeze
|
There is no technical problem with branching but it causes additional
releng overhead on my end. In addition to branching over 200 projects
in the sometimes slow Eclipse.org cvs it requires updating of map
files, creation of new workspaces and potentially back-porting of
fixes.
We can discuss investing in further automation of this process but for
the past three years freezing cvs for a short period of time hasn't
been a problem and was the better trade of in terms of overhead.
I have added an item to next weeks meeting agenda to discuss whether
the policy should be changed.
Steffen
On Fri, Oct 30, 2009 at 5:16 AM, David Green <dgreen99@xxxxxxxxx> wrote:
> I agree, the freeze feels unnatural. I was under the impression that it was
> due to our build process being unable to easily build off a branch.
>
> Perhaps there are other ways to maintain the same social dynamics.
>
> David
>
> On Oct 30, 2009 5:46 AM, "Mik Kersten" <mik@xxxxxxxxxxx> wrote:
>
> Branching works quite well with CVS within Eclipse. So we don't have any
> technical need for doing a code freeze of this sort. I do like some of the
> social aspects in the sense that it makes everyone focus on the release, but
> with more diversity on the project (eg, WikiText) I'm not sure that's
> needed.
>
> Steffen, what do you think?
>
> Mik
>
> --
> Dr. Mik Kersten
> CEO: http://tasktop.com
> Lead: http://eclipse.org/mylyn
> Follow: http://twitter.com/mik_kersten
>
>> -----Original Message----- > From: mylyn-dev-bounces@xxxxxxxxxxx
>> [mailto:mylyn-dev- > bounces@ecl...
>
> _______________________________________________
> mylyn-dev mailing list
> mylyn-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/mylyn-dev
>
>
--
Steffen Pingel
Committer, http://eclipse.org/mylyn
Senior Developer, http://tasktop.com
