Re: [mylyn-dev] sub-project provisioning status

[Steffen Pingel <steffen.pingel@xxxxxxxxxxx>]

I expect that we'll keep all cross-sub-project communication on
mylyn-dev, e.g. for coordinated release planning. It's an EDP
requirement for committers though to be subscribed to the project
mailing list to get notified about committer nominations etc. I don't
think there will be a lot of traffic.

Steffen


On Mon, Dec 13, 2010 at 10:14 AM, Mik Kersten <mik@xxxxxxxxxxx> wrote:
> I assume it's OK if I'm only on mylyn-dev and you percolate anything you
> want me to see up to that list.
>
> Mik
>
> --
> Dr. Mik Kersten
> Tasktop CEO, Mylyn Lead, http://twitter.com/mik_kersten
> Assistant: zoe.jong@xxxxxxxxxxx, +1-778-588-6896, Skype: zoe.e.jong
>
>
>> -----Original Message-----
>> From: mylyn-dev-bounces@xxxxxxxxxxx [mailto:mylyn-dev-
>> bounces@xxxxxxxxxxx] On Behalf Of Steffen Pingel
>> Sent: December-07-10 12:53 AM
>> To: Mylyn developer discussions
>> Subject: Re: [mylyn-dev] sub-project provisioning status
>>
>> These links work better :)
>>
>>  https://dev.eclipse.org/mailman/listinfo/mylyn-commons-dev
>>  https://dev.eclipse.org/mailman/listinfo/mylyn-context-dev
>>  https://dev.eclipse.org/mailman/listinfo/mylyn-incubator-dev
>>  https://dev.eclipse.org/mailman/listinfo/mylyn-tasks-dev
>>
>> Steffen
>>
>>
>> On Tue, Dec 7, 2010 at 12:50 AM, Steffen Pingel
>> <steffen.pingel@xxxxxxxxxxx> wrote:
>> > Mailing lists for the Commons, Context, Incubator and Tasks Project
> exist
>> now:
>> >
>> > https://dev.eclipse.org/mailman/subscribe/mylyn-commons-dev
>> > https://dev.eclipse.org/mailman/subscribe/mylyn-context-dev
>> > https://dev.eclipse.org/mailman/subscribe/mylyn-incubator-dev
>> > https://dev.eclipse.org/mailman/subscribe/mylyn-tasks-dev
>> >
>> > Please subscribe if you are committer on any these projects or
> interested
>> in development related discussions.
>> >
>> > I have added an item to the agenda of Thurday's call to discuss CVS
> and
>> Bugzilla migration.
>> >
>> > Steffen
>> >
>> >
>> > On Thu, Dec 2, 2010 at 8:19 AM, Steffen Pingel
>> <steffen.pingel@xxxxxxxxxxx> wrote:
>> >> Hi,
>> >> it's likely that me and Mik won't be able to join this week's call.
>> >> The current status of the restructuring is that the remaining
>> >> sub-projects, Commons, Context, Incubator, Tasks, have been created
>> >> and are currently being provisioned.
>> >> We also formed the Mylyn PMC this week with the following members:
>> >> Mik Kersten, Chris Aniszczyk, Wayne Beaton and Steffen Pingel.
>> >> Thanks to everyone who submitted proposals for EclipseCon! With a bit
>> >> of luck we'll have a number of interesting talks about Mylyn and its
>> >> sub-projects.
>> >> Steffen
>> >>
>> >> On Thu, Nov 25, 2010 at 2:19 PM, Steffen Pingel
>> >> <steffen.pingel@xxxxxxxxxxx>
>> >> wrote:
>> >>>
>> >>> Hi,
>> >>>
>> >>> due to a conflict I won't be able to join today's call. Here is a
>> >>> quick summary of the current sub-project provisioning status:
>> >>>
>> >>> These projects are fully provisioned:
>> >>>
>> >>> - Mylyn Builds: All committers were approved. Torkild has already
>> >>> pushed enhancements to the new Git repository :).
>> >>> - Mylyn Reviews: New committers were added, some still blocked on
>> >>> paper work.
>> >>> - Mylyn Versions: Most committers were added, some still blocked on
>> >>> paper work.
>> >>>
>> >>> These projects are waiting for Git migration:
>> >>>
>> >>> - Mylyn Docs: Waiting on import of CVS modules to new Git
> repository.
>> >>> David, if you want to me to help out with that I would need
>> >>> committer status on the project. Move of Vex component is pending.
>> >>>
>> >>> These projects are waiting to get created by the EMO (requests have
>> >>> been
>> >>> filed):
>> >>>
>> >>> - Mylyn Commons
>> >>> - Mylyn Context
>> >>> - Mylyn Incubator
>> >>> - Mylyn Tasks
>> >>>
>> >>> More details can be found on the subtasks of this bug:
>> >>>
>> >>>  328393: provision Mylyn sub projects
>> >>>  https://bugs.eclipse.org/bugs/show_bug.cgi?id=328393
>> >>>
>> >>> My goal is to complete the provisioning within then next two weeks.
>> >>> Once we have a working build I am planning to request that Commons,
>> >>> Context, Tasks, and Versions join the Indigo release train. If I
>> >>> remember correctly, we said that Builds and Reviews would do a
>> >>> parallel release to the train but join for Indigo+1.
>> >>>
>> >>> Steffen
>> >>>
>> >>> --
>> >>> Steffen Pingel
>> >>> Committer, http://eclipse.org/mylyn
>> >>> Senior Developer, http://tasktop.com
>> >>
>> >>
>> >>
>> >> --
>> >> Steffen Pingel
>> >> Committer, http://eclipse.org/mylyn
>> >> Senior Developer, http://tasktop.com
>> >>
>> >
>> >
>> >
>> > --
>> > Steffen Pingel
>> > Committer, http://eclipse.org/mylyn
>> > Senior Developer, http://tasktop.com
>> >
>> >
>>
>>
>>
>> --
>> Steffen Pingel
>> Committer, http://eclipse.org/mylyn
>> Senior Developer, http://tasktop.com
>> _______________________________________________
>> mylyn-dev mailing list
>> mylyn-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/mylyn-dev
> _______________________________________________
> 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