Composer Branch Rewritten Manifest

[Andrew Short]

Hi All,

A quick update on some of the work that's been done as part of my GSOC composer project: I've rewritten the manifest system to operate in a different manner, and to fully support namespaces. You can read about this change on my GSOC blog at http://andrewshort.name/gsoc/posts/manifest/ - it would be great if you could let me know if you have and questions or comments.

Cheers,
Andrew Short.

[Ingo Schommer]

Hello Andrew,

thanks for your awesome work, finally got around to looking around a bit!

Given that GSOC is drawing to a close (with a "soft" deadline on the 13th, hard deadline on 20th),

we need a plan of attack what happens with your work.

First of all, do you think its in a mergeable state (into master, which will eventually become 3.1)?

If not, is the remaining work clearly outlined in tickets somewhere?

Can any unfinished parts be isolated into feature branches, in the interest of merging quickly?

Then, would you like to point out any specific areas which need peer review,

or wider architectural decisions you had no time to validate with the community?

I know its all out there in commits somewhere, and you've been pretty vocal on the mailinglist,

but its a huge piece of work, so any pointers from you are appreciated.

I think for the next two weeks, documenting your work should be a priority.

From what I see, we need the following:

- Module (and Manifest) handling overview (incl. reviewing+fixing existing docs)

- Upgrade guide for module users

- Upgrade guide for module developers

- Rewritten install docs around composer

- Updated security instructions about webroot locations etc

- Update coding conventions with namespace usage

- Update all code examples with namespace

- Update tutorials with quick intro about PHP namespaces and how to use them

I'm sure there's a whole raft of TODOs which aren't directly code related,

and we should get this process going sooner rather than later. Can you think of any already?

Thanks

Ingo

[Hamish Friedlander]

I'm keen to check this out too.

Something I don't have a clear picture of yet is what affect this will have on existing projects when upgrading. Ideally people should be able to upgrade from 3.0 to 3.1 without significant issues (although not necessarily _none_, but less than 2.4 to 3.0). 

Ingo, we'll need to update our internal tools pretty soon after this is merged too yeah? Thinking TeamCity, demo & test sites, release scripts, etc.

Hamish Friedlander

--
You received this message because you are subscribed to the Google Groups "SilverStripe Core Development" group.

To view this discussion on the web visit https://groups.google.com/d/msg/silverstripe-dev/-/RdTIDhqvyN4J.

To post to this group, send email to silverst...@googlegroups.com.
To unsubscribe from this group, send email to silverstripe-d...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/silverstripe-dev?hl=en.