On Apr 24, 2007, at 12:20 AM, Sergiu Dumitriu wrote:
Hi,
I agree with 1, 2 and 4. I think that the most important things for users are 1 and 2, with strong emphasis on fixing the security holes, and making the skin+wiki the best on the market. For developers and administrators, 4 is important too.
I'm not so sure about 3. It depends on the elements, and how stable is the architecture. I don't see the point of committing the component based engine, if we don't have any components defined.
oh that's not what I meant. I meant once we have a first component implemented (like for example the refactored Import) in the 2.0 branch we could backport it to the trunk. It may or may not be possible though but I think that's an experiment we'll need to make.
On the other hand, 4 months after 1.0 should be after the SoC deadline, so we could introduce some new features deployed in the program, if they are well written and stable enough.
Good point. However I think they might come too late for 1.1 so I'd rather we schedule them for 1.2, unless of course some of the soc projects bring small and easy improvements to the core. That said, it's really on a case by case basis as they're all different. Some like the IDE editor don't have much impact on XWiki core, other like the storage engine improvements have important impacts.
Thanks
-Vincent
On 4/23/07, Vincent Massol <vincent@massol.net> wrote: Hi,
As we're getting closer to the 1.0 release we need to start thinking
about the 1.1 goals.
Things I'd like to propose for 1.1:
------------------------------------------
Note 1: I proposed a few weeks ago that we should a main release
every 3-4 months, with beta releases every 2-3 weeks. I didn't get
much answer and I concluded that it was ok for most of you. So we
need to consider that time frame in mind for deciding the overall
goal of the 1.1 release. Let's not be too ambitious...
Note 2: The points below are listed by order of importance to me
1) There are still 108 bugs in JIRA. As a consequence I think one
main goal of 1.1 is going to be the consolidation of 1.0.
2) Focus on making the default wiki a wiki that is a good as the
wikis out there. This includes improvements to the look & feel/skin
and to its usability. I don't think we need more features, we just
need each feature to be better implemented: more polished, more
intuitive, more documented, nicer looking.
3) Start introducing XWiki 2.0 architecture elements in it. Even
though XWiki 2.0 will probably be done in a separate branch I think
we should start backporting stuff that'll be done in that branch to
1.1 when possible.
4) Switch to a Maven2 build
WDYT and what would you want to see in the 1.1 release?
Thanks
-Vincent
Sergiu
--
http://purl.org/net/sergiu
--