Hey,
Unless the installer needs to be ready within a week for 1.17 I don't see
any issues.
I want to make structural changes, not add new features. The sooner these
are made, the less overall work my GSoC project will be.
As I'll be doing all the work on these changes, and am not skipping any
other work on the new installer to do so, the progress on the new installer
should not be impacted negatively.
Cheers
--
Jeroen De Dauw
*
Don't panic. Don't be evil. 50 72 6F 67 72 61 6D 6D 69 6E 67 20 34 20 6C 69
66 65!
--
On 21 July 2010 04:40, Tim Starling <tstarling(a)wikimedia.org> wrote:
On 20/07/10 19:28, Jeroen De Dauw wrote:
Hey,
Basically splitting core-specific stuff from general installer
functionality
(so the general stuff can also be used for
extensions). Also making
initial
steps towards filesystem upgrades possible.
The point of this mail is not discussing what I want to do though, but
rather avoiding commit conflicts, as I don't know which people are
working
on the code right now, and who has uncommitted
changes.
There's still quite a lot of work to do to get the new installer ready
for 1.17. I think we should focus on that, and avoid expanding the
scope of the project until we've reached that milestone.
There are the issues discussed here:
http://www.mediawiki.org/wiki/New-installer_issues
and more will become apparent as more testing is done.
If the new installer is not ready to replace the old installer when it
comes time to branch 1.17, I will move it out of trunk, back to a
development branch. Hopefully that won't be necessary.
-- Tim Starling
_______________________________________________
Wikitech-l mailing list
Wikitech-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l