-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Going with the following release definitions: X.Y.Z A change in Z is bug-fix only A change in Y is new feature + bug fix + backward compatible A change in X is new feature | rework + bug fix + not necessarily backward compatible
I knew I was going to be asking this... With the addition of the CSS issue, and what I'm looking at for the application catalog search [TAPESTRY-881 - http://issues.apache.org/jira/browse/TAPESTRY-881], we've moved from a change in Z to a change in Y. Without changing any timetables (hopefully next 3.x release being end May), would anyone object to bypassing 3.0.5 and going straight to 3.1? If this is agreed upon, I will go through JIRA and migrate all 3.0.5 issues to 3.1 and we go from there. If we do this it's possible we can actually get an extra issue resolved (which might otherwise result in a 'new feature'). Thoughts? Brian -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (MingW32) iD8DBQFEUbbtaCoPKRow/gARAlM0AJ9D3Zf0AxMYquNokOu31cq7OKML8gCgqcqe UFyZ60m7Sb+JQnmsZhQ6wRU= =5R2M -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
