Lukas Theussl wrote:
>
>
> Dennis Lundberg wrote:
>> Lukas Theussl wrote:
>>> Hi,
>>>
>>> I was looking at the jira roadmap for the site plugin, thinking about a
>>> release plan for 2.1. The main change so far is the upgrade to doxia
>>> 1.1, I think it would be a good idea to concentrate the ne
Dennis Lundberg wrote:
Lukas Theussl wrote:
Hi,
I was looking at the jira roadmap for the site plugin, thinking about a
release plan for 2.1. The main change so far is the upgrade to doxia
1.1, I think it would be a good idea to concentrate the next release on
issues that are related that. In
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Hi,
Hello,
>
> I was looking at the jira roadmap for the site plugin, thinking about a
> release plan for 2.1. The main change so far is the upgrade to doxia
> 1.1, I think it would be a good idea to concentrate the next release on
> issues that a
Lukas Theussl wrote:
>
> Hi,
>
> I was looking at the jira roadmap for the site plugin, thinking about a
> release plan for 2.1. The main change so far is the upgrade to doxia
> 1.1, I think it would be a good idea to concentrate the next release on
> issues that are related that. In particular,
Lukas Theussl wrote:
Right now there are also a number of other issues scheduled that are not
related (eg MSITE-79, MSITE-206, MSITE-326) which I would like to leave
out and schedule for a later release.
Is this ok with everyone?
+1, I don't see the point in blocking a release or even just
Hi,
I was looking at the jira roadmap for the site plugin, thinking about a release
plan for 2.1. The main change so far is the upgrade to doxia 1.1, I think it would
be a good idea to concentrate the next release on issues that are related that. In
particular, I'd like to fix all these annoy
