cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dharmesh Kakadia <dhkaka...@gmail.com>
Subject Re: [Discuss][CLOUDSTACK-212] Namespace change for ASF
Date Fri, 05 Jul 2013 11:56:30 GMT
Hi,

@Wido good suggestion. Tabs are easy to replace with regex. I am not sure
of trailing whitespace though. Should be able to complete that too by 20th.

@Ryan Thanks for pointing out. I tried to update the version, but version
4.3 doesn't exist yet ;)

Thanks,
Dharmesh


On Fri, Jul 5, 2013 at 1:29 PM, Sebastien Goasguen <runseb@gmail.com> wrote:

>
> On Jul 5, 2013, at 1:28 AM, Ryan Lei <ryanlei@cht.com.tw> wrote:
>
> > Hi, the corresponding CLOUDSTACK-212 is marked as "Improvement," and
> > planned to be fixed in 4.2.0.
> >
> > But since we have passed the feature freeze date, will the namespace
> change
> > be deferred to 4.3.0?
> >
>
> Yes that's the plan, trying to have it reach master asap to be early in
> the 4.3 development cycle.
>
> we will update the bug fix version
>
> >
> -------------------------------------------------------------------------------------------
> > Yu-Heng (Ryan) Lei, Associate Reasearcher
> > Chunghwa Telecom Laboratories / Cloud Computing Laboratory
> > ryanlei@cht.com.tw<
> https://email.cht.com.tw/owa/redir.aspx?C=-wE1FEC3G0SWYpVkiWo8SsDdf3ZqO9AIuAPTzRnFYCUi-z4YljtI_hyVKkNHfn9F1Bn-vUWJnQ4.&URL=mailto%3aryanlei%40cht.com.tw
> >
> > or
> > ryanlei750328@gmail.com
> >
> >
> >
> > On Fri, Jul 5, 2013 at 3:07 AM, Wido den Hollander <wido@widodh.nl>
> wrote:
> >
> >> Hi,
> >>
> >>
> >> On 07/04/2013 01:53 PM, Dharmesh Kakadia wrote:
> >>
> >>> Hi,
> >>>
> >>> Since the cloudstack project has moved to ASF, the suggestion is to
> move
> >>> from com.cloud packages to org.apache java packages .(
> >>> https://issues.apache.org/**jira/browse/CLOUDSTACK-212<
> https://issues.apache.org/jira/browse/CLOUDSTACK-212>
> >>> )
> >>>
> >>> As you might be realize, this is pretty big change. And merging this
> >>> changes with a continuously updating master is non-trivial. So, here is
> >>> the
> >>> planned strategy after discussion over IRC. I am starting this thread
> to
> >>> inform and know everyone's opinions.
> >>>
> >>> 1. I will be pushing code with new packages on branch
> "namespacechanges"
> >>> and will notify on this thread as each refactored module is pushed.
> >>>
> >>> 2. There will be a freeze on master branch commits for some time in
> which
> >>> "namespacechanges" will be applied to master. I suggest the date to be
> >>> 20th
> >>> July.
> >>>
> >>>
> >> +1 on doing this, since we have to do it at some point.
> >>
> >> One question though, since this will break a lot of merges, can we also
> do
> >> a whitespace fix?
> >>
> >> We still have a lot of tabs instead of 4 spaces and with a simple find
> and
> >> sed we can fix that.
> >>
> >> Same goes for trailing spaces.
> >>
> >> We could do one (or multiple) commits which address these issues at
> once?
> >>
> >> Wido
> >>
> >>
> >>
> >> 3. All the branch-owner updates their branch for reflect new packages.
> It
> >>> was suggested that branch owners can look into the "namespacechanges"
> >>> branch as it grows and start doing the package changes early, although
> it
> >>> depends on branch-owners.
> >>>
> >>> Thanks,
> >>> Dharmesh
> >>>
> >>>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message