james-mime4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Robert Burrell Donkin <robertburrelldon...@gmail.com>
Subject Re: [jira] Commented: (MIME4J-101) Convert Mime4J into a project with multiple modules
Date Fri, 27 Feb 2009 14:50:02 GMT
On Thu, Feb 26, 2009 at 8:02 PM, Oleg Kalnichevski <olegk@apache.org> wrote:
> Markus Wiederkehr wrote:
>> On Wed, Feb 25, 2009 at 1:34 PM, Robert Burrell Donkin (JIRA)
>> <mime4j-dev@james.apache.org> wrote:
>>>   [
>>> https://issues.apache.org/jira/browse/MIME4J-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676626#action_12676626
>>> ]
>>> Robert Burrell Donkin commented on MIME4J-101:
>>> ----------------------------------------------
>>> I have a plan that would allow work to begin on this before the 0.6
>>> release is finalised.
>>> My proposal is to create a peer directory in subversion next to tags,
>>> branchs and trunk called 'future'. svn:externals would be used to import the
>>> current trunk as a subdirectory. This would allow work to start on the top
>>> level components as work continues on the 0.6 release.
>>> Once 0.6 is released, the svn:externals would be removed, trunk moved to
>>> future/main and future renamed to trunk.
>> I think 0.6 is maybe only a matter of days and after that the trunk is
>> all yours if you like (unless Oleg has plans, of course). Personally I
>> have a few other thinks to attend to and there will be probably not
>> much time for Mime4j for a few weeks..
>> If you prefer the svn:externals approach I have no objections though..
>> Markus
> Robert,
> If you can hold off for a few more days, I intend to resume working on the
> release as soon as MIME4J-118 is resolved. I have no problem with the
> svn:externals approach as well.

svn:externals is the appoach i plan to take anyway  but i can wait
until after the release

- robert

View raw message