You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@concerted.apache.org by Atri Sharma <at...@gmail.com> on 2015/11/06 14:47:53 UTC
Planning First Release
Hi,
I am thinking of planning first release.
I think locking manager and current structures should be fine for first
release. We have automated build process and automated tests right now.
Mentors, please advice.
Regards,
Atri
Re: Planning First Release
Posted by Julian Hyde <jh...@apache.org>.
+1 focus on a release with good IP hygiene
The other important thing is that a developer should be able to build and run the bits with a minimum of fuss. How much the bits do at this point is less important.
Julian
> On Nov 6, 2015, at 9:39 AM, Roman Shaposhnik <ro...@shaposhnik.org> wrote:
>
> On Fri, Nov 6, 2015 at 5:47 AM, Atri Sharma <at...@gmail.com> wrote:
>> Hi,
>>
>> I am thinking of planning first release.
>>
>> I think locking manager and current structures should be fine for first
>> release. We have automated build process and automated tests right now.
>>
>> Mentors, please advice.
>
> What I would really recommend you guys do is to NOT focus on features,
> stability, etc. but rather have a first release being an alpha release (properly
> labeled as such of course!) that focuses on IP hygiene.
>
> Decoupling these concerns helps a great deal.
>
> Thanks,
> Roman.
Re: Planning First Release
Posted by Roman Shaposhnik <ro...@shaposhnik.org>.
On Fri, Nov 6, 2015 at 5:47 AM, Atri Sharma <at...@gmail.com> wrote:
> Hi,
>
> I am thinking of planning first release.
>
> I think locking manager and current structures should be fine for first
> release. We have automated build process and automated tests right now.
>
> Mentors, please advice.
What I would really recommend you guys do is to NOT focus on features,
stability, etc. but rather have a first release being an alpha release (properly
labeled as such of course!) that focuses on IP hygiene.
Decoupling these concerns helps a great deal.
Thanks,
Roman.