28 Oct
2010
28 Oct
'10
5:37 p.m.
On Oct 28, 2010, at 5:29 PM, Jerome Velociter wrote:
On Tue, Oct 26, 2010 at 6:44 PM, Vincent Massol
<vincent(a)massol.net> wrote:
Are you proposing to implement these features yourself?
If not, we need someone to volunteer.
Thanks
-Vincent
On Oct 26, 2010, at 5:39 PM, Jerome Velociter wrote:
Yes. I meant at least two things :
* Activate annotations as a default setting
* Have annotations displayed even when JavaScript is not available
(that means moving code from the annotation application to the
platform - but that's another story)
And a third item, a bit more ambitious (so maybe for 2.7 ?) :
* Fusion annotations with comments (at least in the U. Probably in the
storage (read: XClass) by default too - to make the UI easier to
write). Comments would then become annotations without a context.
That would already be great. On Thu, Oct 21, 2010 at 1:08 AM, Sergiu Dumitriu
<sergiu(a)xwiki.com> wrote:
Could you be more specific re annotations? On 10/20/2010 09:31 AM, Vincent Massol wrote:
> Hi,
>
> I'd like to propose that we have a short XE 2.6 release. The
> rationale is that we've been developing lots of new features in the
> past releases and I think it's time to stabilize what we have. By
> stabilize I mean: - fix bugs - homogenize UI - clean up stuff
> (refactoring, etc)
I don't quite agree with only one quick release, but instead I'd propose
to sprint for a winter 3.0 release. I believe that since 2.0 we've added
(or started) enough new features to make up for a major release.
So, I'd propose monthly releases until we get a polished version ready
to be promoted as 3.0. This means that the number of new features should
be kept to a minimum, trying to finish all the stuff that was already
started: gadgets, portlets (a bit difficult, so this is not a hard
requirement), new UIs (administration, multipage export, standard forms,
maybe rights), xwiki/2.1 syntax, extension manager.
I would like to add "annotations" to this list (especially making them
work w/o JS and and activated by default) Jerome.
>
>> I'm OK to work on that if we agree we want it.
>
> For 2.6?
>
> Thanks
> -Vincent
>
>>
>> Jerome.
>>
>>>
>>>> In addition we have 2 features we had planned for 2.5 which have
>>>> slipped and we could finish them in 2.6 too (Sergiu said he was
>>>> almost done with the "Email this page" feature and didn't
have the
>>>> time to slip it in the 2.5):
>>>> - Email this page: Sergiu
>>>> - Recent Activity (refactoring of Recent Changes based on the Activity
>>>> Stream): Raluca + Caty + JV to apply the patch
>>>>
>>>> The idea would be to have the following dates:
>>>> - 2.6RC1: 1st of November 2010 (there's no M1)
>>>> - 2.6 final: 18h of November
>>>
>>> I'd move the RC one week later.
>>>
>>>> If we agree, is there anyone who'd like to be the release manager
for
>>>> this release? If nobody volunteers I can do it.
>>>
>>> I could do it as well, if nobody else volunteers.
>>>
>>>> If we agree, I'll send another mail afterwards with some ideas for
XE
>>>> 2.7 and a potential XE 3.0 release. Note that XE 2.6 would be a first
>>>> step in stabilizing XE for an upcoming 3.0 release :) But even
>>>> without this vision doing a short stabilization release from time to
>>>> time is always a good think I believe. It's also not too long so
that
>>>> people don't need to hold new stuff for too long.
>>>
>>> We could already create a 3.1 branch/trunk for new stuff when needed,
>>> although this will increase the number of maintained branches a bit too
>>> much. To help here, we can decide not to do maintainance releases for
>>> the 2.6+ branches, since these are short releases.