Feature freeze

[Greg Brown <gk...@mac.com>]

I am thinking that we should impose a feature freeze once the  
remaining tickets for 1.4 have been resolved. Here is what is  
currently outstanding:

PIVOT-205	Pivot collections test suite

I think we can safely push this back to 1.41.

PIVOT-235	Complete tutorial

This one is nearly complete. There are only 2 or 3 remaining sections,  
and I think we should push to wrap this up for 1.4. This was one of  
our primary focuses for 1.4, and it will be even more important to  
have solid documentation should we graduate to a TLP. So we should  
make sure we finish this one.

PIVOT-23	Ensure that popups are constrained to display bounds

I think this can safely be deferred to 1.4.1.

PIVOT-43	Add support for digest authentication to web queries

I suggest that we move this to 1.4.1 as well.

That would leave the tutorial docs as the only outstanding item.

Any objections?

G

Re: Feature freeze

[Sandro Martini <sa...@gmail.com>]

Hi Todd,

> sorry for the confusion.
no problem.

Byeeee

Re: Feature freeze

[Todd Volkert <tv...@gmail.com>]

> So I can fix them (but tomorrow), but please tell me if (or what) wanted.
> Or I can wait after the code freeze, no problem.
>

No, let's wait until 1.4.1 to address those, since none of them look too
serious.  I was actually responding to Noel with my previous email, since it
sounded like he has already coded the variable row height feature in
TableView - sorry for the confusion.

-T

Re: Feature freeze

[Sandro Martini <sa...@gmail.com>]

Hi Todd,
no I haven't started fixing all those simple things or warnings ...
also because I don't want to waste my (little) time to make fixes that
after has to be reverted ... like yesterday (and other times in the
past).

So I can fix them (but tomorrow), but please tell me if (or what) wanted.
Or I can wait after the code freeze, no problem.

Thanks,
Sandro

Re: Feature freeze

[Todd Volkert <tv...@gmail.com>]

If you've already done the work, then I'd say by all means, go ahead and
submit (just as I had already started the work of Image.getBaseline()).
We'll have plenty of time to make sure it's stable.  Let's all just turn our
collective effort towards stabilizing the code base after we're done
committing our work-in-progress.

On Wed, Nov 18, 2009 at 1:41 AM, Noel Grandin <no...@gmail.com> wrote:

> Is it OK if I commit my TableView variableRowHeight code?
>
> It's a pretty straightforward port of the variableItemHeight code from
> ListView.
>
> -- Noel
>
> Greg Brown wrote:
> > I am thinking that we should impose a feature freeze once the
> > remaining tickets for 1.4 have been resolved. Here is what is
> > currently outstanding:
> >
> > PIVOT-205    Pivot collections test suite
> >
> > I think we can safely push this back to 1.41.
> >
> > PIVOT-235    Complete tutorial
> >
> > This one is nearly complete. There are only 2 or 3 remaining sections,
> > and I think we should push to wrap this up for 1.4. This was one of
> > our primary focuses for 1.4, and it will be even more important to
> > have solid documentation should we graduate to a TLP. So we should
> > make sure we finish this one.
> >
> > PIVOT-23    Ensure that popups are constrained to display bounds
> >
> > I think this can safely be deferred to 1.4.1.
> >
> > PIVOT-43    Add support for digest authentication to web queries
> >
> > I suggest that we move this to 1.4.1 as well.
> >
> > That would leave the tutorial docs as the only outstanding item.
> >
> > Any objections?
> >
> > G
> >
>
>

Re: Feature freeze

[Noel Grandin <no...@gmail.com>]

Is it OK if I commit my TableView variableRowHeight code?

It's a pretty straightforward port of the variableItemHeight code from
ListView.

-- Noel

Greg Brown wrote:
> I am thinking that we should impose a feature freeze once the
> remaining tickets for 1.4 have been resolved. Here is what is
> currently outstanding:
>
> PIVOT-205    Pivot collections test suite
>
> I think we can safely push this back to 1.41.
>
> PIVOT-235    Complete tutorial
>
> This one is nearly complete. There are only 2 or 3 remaining sections,
> and I think we should push to wrap this up for 1.4. This was one of
> our primary focuses for 1.4, and it will be even more important to
> have solid documentation should we graduate to a TLP. So we should
> make sure we finish this one.
>
> PIVOT-23    Ensure that popups are constrained to display bounds
>
> I think this can safely be deferred to 1.4.1.
>
> PIVOT-43    Add support for digest authentication to web queries
>
> I suggest that we move this to 1.4.1 as well.
>
> That would leave the tutorial docs as the only outstanding item.
>
> Any objections?
>
> G
>

Re: Feature freeze

[Greg Brown <gk...@mac.com>]

Yes, we want to only include functional and tested code in the 1.4  
release. So, if this feature is not done, we would temporarily remove  
the associated files (you could easily add them again in a later  
release). That is actually what I suggest we do, since (IMO) any time  
we have available now would be better spent testing and validating the  
many other features that are already complete.
G

On Nov 17, 2009, at 10:30 AM, Sandro Martini wrote:

> For me all is Ok, but only a curiosity ... deferring PIVOT-43 to
> 1.4.1, means that the file will be dropped in the 1.4, and re-added
> later (on Subversion for some things I'm a newbie :-) ) ?
>
> In practical terms, should I copy that source in a local folder, and
> commit after the 1.4 release (so in the mean time I can finish to
> modify it) ?
>
>
> In any case, if I have some days until code freeze, now I can start to
> work on it, starting from now, and I can tell you if ready for 1.4, ok
> ?
>
>
> Thanks,
> Sandro

Re: Feature freeze

[Sandro Martini <sa...@gmail.com>]

For me all is Ok, but only a curiosity ... deferring PIVOT-43 to
1.4.1, means that the file will be dropped in the 1.4, and re-added
later (on Subversion for some things I'm a newbie :-) ) ?

In practical terms, should I copy that source in a local folder, and
commit after the 1.4 release (so in the mean time I can finish to
modify it) ?


In any case, if I have some days until code freeze, now I can start to
work on it, starting from now, and I can tell you if ready for 1.4, ok
?


Thanks,
Sandro

Re: Feature freeze

[Sandro Martini <sa...@gmail.com>]

Hi Greg,
> Since the code needs some significant rework, I'd prefer to remove it for now. We can make sure we spend the time to get it right for Pivot 1.4.x.
Uh, I hope not so much rework :-) , but Ok, I've already a local copy
to work, and re-commit after the 1.4 final release.
Remember that you have to drop also the related unit test (and
probably also the package html file).

For the next commits, you are speaking also of small bug fixing like
my warnings from Findbugs of yesterday, right ?

Bye

Re: Feature freeze

[Greg Brown <gk...@mac.com>]

Exactly. I fully expect to see additional commits before we release.  
They should be primarily bug fixes, but minor updates such as this are  
OK too. We just want to avoid any major changes from here on in.

On Nov 17, 2009, at 12:30 PM, Todd Volkert wrote:

> Don't worry about it - we're not tagging in the next few days or  
> anything;
> it's more that we should be winding down our new feature commits and
> focusing on stability in preparation for our graduation (and the 1.4  
> release
> that will follow thereafter).
>
> -T
>
> On Tue, Nov 17, 2009 at 12:19 PM, Christopher Brind <
> christopher.brind@googlemail.com> wrote:
>
>> Damn, I must have checked out the code read only or something as I'm
>> getting
>> a forbidden response.  Will have to commit it on Thursday now - if  
>> you want
>> to freeze before then that's OK, I'll work around it.
>>
>> Cheers,
>> Chris
>>
>>
>> 2009/11/17 Todd Volkert <tv...@gmail.com>
>>
>>> Sounds fine to me
>>>
>>> On Tue, Nov 17, 2009 at 11:53 AM, Christopher Brind <
>>> christopher.brind@googlemail.com> wrote:
>>>
>>>> Am I OK to commit my changes to the SerializationExcepton and those
>> other
>>>> serializer changes we discussed?
>>>>
>>>> Cheers,
>>>> Chris
>>>>
>>>>
>>>> 2009/11/17 Sandro Martini <sa...@gmail.com>
>>>>
>>>>> Hi Todd,
>>>>>> Sandro, no need to keep a local copy of DigestAuthentication as a
>>>> backup
>>>>> --
>>>>>> the SVN server will keep the historical copy for you.
>>>>> Ok, but so in the meantime I could proceed with finishing it.
>>>>>
>>>>> For Greg:
>>>>>> Yes, we want to only include functional and tested code in the  
>>>>>> 1.4
>>>>> release.
>>>>> the code in DigestAuthentication is working (the related unit test
>>>>> works good with apache 2.2.x), but as you said to me, it hasn't  
>>>>> the
>>>>> right flow inside. So at this point I don't know if you prefer to
>>>>> remove it (and its unit test) temporary (in any case) or to keep  
>>>>> and
>>>>> mark as experimental, but no problem whatever you choose.
>>>>>
>>>>> In you give me some days (until mid on next week, or it is too  
>>>>> later
>>>>> ?) I can finish it, so if you can wait to remove it it will be
>> simpler
>>>>> also for me to do tests, otherwise anytime I synchronize from the
>>>>> trunk (using the replace all for security) i miss my local files
>>>>> inside the project.
>>>>>
>>>>>
>>>>> Byeeee
>>>>>
>>>>
>>>
>>

Re: Feature freeze

[Todd Volkert <tv...@gmail.com>]

Don't worry about it - we're not tagging in the next few days or anything;
it's more that we should be winding down our new feature commits and
focusing on stability in preparation for our graduation (and the 1.4 release
that will follow thereafter).

-T

On Tue, Nov 17, 2009 at 12:19 PM, Christopher Brind <
christopher.brind@googlemail.com> wrote:

> Damn, I must have checked out the code read only or something as I'm
> getting
> a forbidden response.  Will have to commit it on Thursday now - if you want
> to freeze before then that's OK, I'll work around it.
>
> Cheers,
> Chris
>
>
> 2009/11/17 Todd Volkert <tv...@gmail.com>
>
> > Sounds fine to me
> >
> > On Tue, Nov 17, 2009 at 11:53 AM, Christopher Brind <
> > christopher.brind@googlemail.com> wrote:
> >
> > > Am I OK to commit my changes to the SerializationExcepton and those
> other
> > > serializer changes we discussed?
> > >
> > > Cheers,
> > > Chris
> > >
> > >
> > > 2009/11/17 Sandro Martini <sa...@gmail.com>
> > >
> > > > Hi Todd,
> > > > > Sandro, no need to keep a local copy of DigestAuthentication as a
> > > backup
> > > > --
> > > > > the SVN server will keep the historical copy for you.
> > > > Ok, but so in the meantime I could proceed with finishing it.
> > > >
> > > > For Greg:
> > > > > Yes, we want to only include functional and tested code in the 1.4
> > > > release.
> > > > the code in DigestAuthentication is working (the related unit test
> > > > works good with apache 2.2.x), but as you said to me, it hasn't the
> > > > right flow inside. So at this point I don't know if you prefer to
> > > > remove it (and its unit test) temporary (in any case) or to keep and
> > > > mark as experimental, but no problem whatever you choose.
> > > >
> > > > In you give me some days (until mid on next week, or it is too later
> > > > ?) I can finish it, so if you can wait to remove it it will be
> simpler
> > > > also for me to do tests, otherwise anytime I synchronize from the
> > > > trunk (using the replace all for security) i miss my local files
> > > > inside the project.
> > > >
> > > >
> > > > Byeeee
> > > >
> > >
> >
>

Re: Feature freeze

[Christopher Brind <ch...@googlemail.com>]

Damn, I must have checked out the code read only or something as I'm getting
a forbidden response.  Will have to commit it on Thursday now - if you want
to freeze before then that's OK, I'll work around it.

Cheers,
Chris


2009/11/17 Todd Volkert <tv...@gmail.com>

> Sounds fine to me
>
> On Tue, Nov 17, 2009 at 11:53 AM, Christopher Brind <
> christopher.brind@googlemail.com> wrote:
>
> > Am I OK to commit my changes to the SerializationExcepton and those other
> > serializer changes we discussed?
> >
> > Cheers,
> > Chris
> >
> >
> > 2009/11/17 Sandro Martini <sa...@gmail.com>
> >
> > > Hi Todd,
> > > > Sandro, no need to keep a local copy of DigestAuthentication as a
> > backup
> > > --
> > > > the SVN server will keep the historical copy for you.
> > > Ok, but so in the meantime I could proceed with finishing it.
> > >
> > > For Greg:
> > > > Yes, we want to only include functional and tested code in the 1.4
> > > release.
> > > the code in DigestAuthentication is working (the related unit test
> > > works good with apache 2.2.x), but as you said to me, it hasn't the
> > > right flow inside. So at this point I don't know if you prefer to
> > > remove it (and its unit test) temporary (in any case) or to keep and
> > > mark as experimental, but no problem whatever you choose.
> > >
> > > In you give me some days (until mid on next week, or it is too later
> > > ?) I can finish it, so if you can wait to remove it it will be simpler
> > > also for me to do tests, otherwise anytime I synchronize from the
> > > trunk (using the replace all for security) i miss my local files
> > > inside the project.
> > >
> > >
> > > Byeeee
> > >
> >
>

Re: Feature freeze

[Todd Volkert <tv...@gmail.com>]

Sounds fine to me

On Tue, Nov 17, 2009 at 11:53 AM, Christopher Brind <
christopher.brind@googlemail.com> wrote:

> Am I OK to commit my changes to the SerializationExcepton and those other
> serializer changes we discussed?
>
> Cheers,
> Chris
>
>
> 2009/11/17 Sandro Martini <sa...@gmail.com>
>
> > Hi Todd,
> > > Sandro, no need to keep a local copy of DigestAuthentication as a
> backup
> > --
> > > the SVN server will keep the historical copy for you.
> > Ok, but so in the meantime I could proceed with finishing it.
> >
> > For Greg:
> > > Yes, we want to only include functional and tested code in the 1.4
> > release.
> > the code in DigestAuthentication is working (the related unit test
> > works good with apache 2.2.x), but as you said to me, it hasn't the
> > right flow inside. So at this point I don't know if you prefer to
> > remove it (and its unit test) temporary (in any case) or to keep and
> > mark as experimental, but no problem whatever you choose.
> >
> > In you give me some days (until mid on next week, or it is too later
> > ?) I can finish it, so if you can wait to remove it it will be simpler
> > also for me to do tests, otherwise anytime I synchronize from the
> > trunk (using the replace all for security) i miss my local files
> > inside the project.
> >
> >
> > Byeeee
> >
>

Re: Feature freeze

[Christopher Brind <ch...@googlemail.com>]

Am I OK to commit my changes to the SerializationExcepton and those other
serializer changes we discussed?

Cheers,
Chris


2009/11/17 Sandro Martini <sa...@gmail.com>

> Hi Todd,
> > Sandro, no need to keep a local copy of DigestAuthentication as a backup
> --
> > the SVN server will keep the historical copy for you.
> Ok, but so in the meantime I could proceed with finishing it.
>
> For Greg:
> > Yes, we want to only include functional and tested code in the 1.4
> release.
> the code in DigestAuthentication is working (the related unit test
> works good with apache 2.2.x), but as you said to me, it hasn't the
> right flow inside. So at this point I don't know if you prefer to
> remove it (and its unit test) temporary (in any case) or to keep and
> mark as experimental, but no problem whatever you choose.
>
> In you give me some days (until mid on next week, or it is too later
> ?) I can finish it, so if you can wait to remove it it will be simpler
> also for me to do tests, otherwise anytime I synchronize from the
> trunk (using the replace all for security) i miss my local files
> inside the project.
>
>
> Byeeee
>

Re: Feature freeze

[Greg Brown <gk...@mac.com>]

> For Greg:
>> Yes, we want to only include functional and tested code in the 1.4  
>> release.
> the code in DigestAuthentication is working (the related unit test
> works good with apache 2.2.x), but as you said to me, it hasn't the
> right flow inside. So at this point I don't know if you prefer to
> remove it (and its unit test) temporary (in any case) or to keep and
> mark as experimental, but no problem whatever you choose.
>
> In you give me some days (until mid on next week, or it is too later
> ?) I can finish it, so if you can wait to remove it it will be simpler
> also for me to do tests, otherwise anytime I synchronize from the
> trunk (using the replace all for security) i miss my local files
> inside the project.

Since the code needs some significant rework, I'd prefer to remove it  
for now. We can make sure we spend the time to get it right for Pivot  
1.4.x.

Re: Feature freeze

[Sandro Martini <sa...@gmail.com>]

Hi Todd,
> Sandro, no need to keep a local copy of DigestAuthentication as a backup --
> the SVN server will keep the historical copy for you.
Ok, but so in the meantime I could proceed with finishing it.

For Greg:
> Yes, we want to only include functional and tested code in the 1.4 release.
the code in DigestAuthentication is working (the related unit test
works good with apache 2.2.x), but as you said to me, it hasn't the
right flow inside. So at this point I don't know if you prefer to
remove it (and its unit test) temporary (in any case) or to keep and
mark as experimental, but no problem whatever you choose.

In you give me some days (until mid on next week, or it is too later
?) I can finish it, so if you can wait to remove it it will be simpler
also for me to do tests, otherwise anytime I synchronize from the
trunk (using the replace all for security) i miss my local files
inside the project.


Byeeee

Re: Feature freeze

[Todd Volkert <tv...@gmail.com>]

I'm adding some functionality to baseline alignment (to support images being
able to specify a manual baseline alignment -- for the use case when they
have embedded text).  Once that's in, I'll be all set, and this sounds good.

Sandro, no need to keep a local copy of DigestAuthentication as a backup --
the SVN server will keep the historical copy for you.

-T

On Tue, Nov 17, 2009 at 10:20 AM, Greg Brown <gk...@mac.com> wrote:

> I am thinking that we should impose a feature freeze once the remaining
> tickets for 1.4 have been resolved. Here is what is currently outstanding:
>
> PIVOT-205       Pivot collections test suite
>
> I think we can safely push this back to 1.41.
>
> PIVOT-235       Complete tutorial
>
> This one is nearly complete. There are only 2 or 3 remaining sections, and
> I think we should push to wrap this up for 1.4. This was one of our primary
> focuses for 1.4, and it will be even more important to have solid
> documentation should we graduate to a TLP. So we should make sure we finish
> this one.
>
> PIVOT-23        Ensure that popups are constrained to display bounds
>
> I think this can safely be deferred to 1.4.1.
>
> PIVOT-43        Add support for digest authentication to web queries
>
> I suggest that we move this to 1.4.1 as well.
>
> That would leave the tutorial docs as the only outstanding item.
>
> Any objections?
>
> G
>
>