You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by Eric Charles <er...@apache.org> on 2016/05/29 07:42:27 UTC
Actions for V3 release
What would be our plan for V3 release?
Any volunteer to act as release manager?
On my side, I prefer acting on some specific jiras rather than as
release manager.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: Actions for V3 release
Posted by Eric Charles <er...@apache.org>.
Impressive work Benoit.
https://github.com/chibenwa/james-project/blob/v3.0_roadmap/v3.0_mailet_inventory.adoc
- What does "Tested" mean for you (unit test, user test...)?
- Matchers /mailet/standard has some formatting issues
- IsInWhiteList: SQL specific stuff: does it mean it does not work at
all - The SQL may be inline with the JPA entities.
https://github.com/chibenwa/james-project/blob/v3.0_roadmap/v3.0_roadmap.adoc
- Do we need a new logo and website to release (I agree we need to do
something, but it should not block v3).
- Maildir is flagged unsupported (Known issue on MailboxPath handling).
Does it mean it is not usable in current state?
How can we further work on the docs in a collaborative way? We have for
now a web site, a wiki (http://wiki.apache.org/james/) and now pages on
github. Any visitor will be confused with this.
If we can define the recipe for doc (the default one being the current
svn site where you can write markdown), I can help migrating content to it.
On 03/06/16 12:01, Benoit Tellier wrote:
> Hi Eric,
>
> We took a few day to debate internally about what should be done, and we
> opened a Pull Request with our proposals :
>
> https://github.com/apache/james-project/pull/42
>
> Every one is welcome to debate on this pull request about what should be
> the scope of this release. Then we will be able to create the related
> JIRA tickets.
>
> Regards,
>
> Benoit
>
> Le 29/05/2016 � 14:42, Eric Charles a �crit :
>> What would be our plan for V3 release?
>> Any volunteer to act as release manager?
>>
>> On my side, I prefer acting on some specific jiras rather than as
>> release manager.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
>> For additional commands, e-mail: server-dev-help@james.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
> For additional commands, e-mail: server-dev-help@james.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: Actions for V3 release
Posted by Benoit Tellier <be...@minet.net>.
Hi Eric,
We took a few day to debate internally about what should be done, and we
opened a Pull Request with our proposals :
https://github.com/apache/james-project/pull/42
Every one is welcome to debate on this pull request about what should be
the scope of this release. Then we will be able to create the related
JIRA tickets.
Regards,
Benoit
Le 29/05/2016 � 14:42, Eric Charles a �crit :
> What would be our plan for V3 release?
> Any volunteer to act as release manager?
>
> On my side, I prefer acting on some specific jiras rather than as
> release manager.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
> For additional commands, e-mail: server-dev-help@james.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org