Hello Stefan,

Yes, I believe your idea has merit but would like to delay it, to not get in 
the way of current release, which is just now underway.

I’ll open a JIRA ticket and we can use that to track decisions relating to the 
activity.

Thanks,
--Shawn

> On Nov 5, 2018, at 4:03 PM, Stefan Seelmann <m...@stefan-seelmann.de> wrote:
> 
> Hi Shawn,
> 
> I think we already discussed that, but I wonder if it makes sense to
> merge the 4 fortress git repos into a single one? You anyway release
> them simultaneously and all have same version. I think it would simplify
> the release process. But maybe it's too short term before the actual
> release :)
> 
> Kind Regards,
> Stefan
> 
> 
> On 10/26/18 5:29 PM, Shawn McKinney wrote:
>> Hello,
>> 
>> This is notification of intent to begin working on a new release of fortress 
>> 2.0.3, includes enhancements and bug fixes:
>> 
>> https://issues.apache.org/jira/issues/?jql=project%20%3D%2012315921%20AND%20fixVersion%20%3D%2012344047%20ORDER%20BY%20priority%20DESC%2C%20key%20ASC
>> 
>> Please let me know if you have any questions or concerns.
>> 
>> Thanks,
>> --Shawn
>> 
>> 
>> 
>> 
>> 
> 

Attachment: signature.asc
Description: Message signed with OpenPGP

Reply via email to