You are viewing a plain text version of this content. The canonical link for it is here.
Posted to batik-dev@xmlgraphics.apache.org by bu...@apache.org on 2008/07/15 11:16:27 UTC
DO NOT REPLY [Bug 45397] New: Missing target milestones in bug
reporting tool
https://issues.apache.org/bugzilla/show_bug.cgi?id=45397
Summary: Missing target milestones in bug reporting tool
Product: Batik
Version: 2.0
Platform: All
URL: https://issues.apache.org/bugzilla/enter_bug.cgi?product
=Batik
OS/Version: All
Status: NEW
Severity: trivial
Priority: P5
Component: Web Site
AssignedTo: batik-dev@xmlgraphics.apache.org
ReportedBy: helder.magalhaes@gmail.com
Although version 2.0 is already displayed in version list, no target milestones
are available to point issues/improvements at.
As of (SVN) revision 676833, current target seems to be 1.8 ("batik-1.8pre" is
internally used) so I believe that (at least) target milestone 1.8 should be
created. This would allow attaching patches for things which can be committed
when this milestone is made available (for example, I can think of the Java 1.3
support removed somewhere after 1.7 was released and to which documentation
changes can start being harvested).
Also, should a "bugzilla" or "bug tracker" component be created for this sort
of issues? I've attached this one to "Web Site" which, being somehow related,
is a bit off-topic...
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: batik-dev-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: batik-dev-help@xmlgraphics.apache.org
DO NOT REPLY [Bug 45397] Missing target milestones in bug reporting
tool
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=45397
--- Comment #1 from Helder Magalhães <he...@gmail.com> 2008-12-18 03:30:25 PST ---
(In reply to comment #0)
[...]
> (for example, I can think of the Java 1.3
> support removed somewhere after 1.7 was released and to which documentation
> changes can start being harvested).
Apparently this was already made effective (revision 701292 ( https://svn.apache.org/viewcvs.cgi?view=rev&rev=701292 ), revision 713578 ( https://svn.apache.org/viewcvs.cgi?view=rev&rev=713578 )).
Nevertheless, this still makes sense in the scope of, for example:
* Schedule future Java version drops (Java 1.4, Java 1.5, etc.)
* Target major features which may need lots of work but are interesting to
have before a conceptual release 2.0 (for example, an interesting feature which
will not make it before releasing 1.8 but that would be interesting to have in
1.9).
As no comment was made on this issue, I ask if this is hard to accomplish
and/or not relevant. If so, I might try to create bugs such as "Drop Java 1.4
support", "Drop Java 1.5 support" (to use as blockers) whenever possible and
defer the version scheduling for the future...
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: batik-dev-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: batik-dev-help@xmlgraphics.apache.org
DO NOT REPLY [Bug 45397] Missing target milestones in bug reporting
tool
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=45397
--- Comment #2 from Cameron McCormack <ca...@apache.org> 2008-12-21 13:34:59 PST ---
Hi Helder.
I think making a bug for dropping 1.4 support, and adding it as a dependency
for other bugs that have patches for actual removal of 1.4 support is a good
idea.
I've just asked infrastructure to give me access to edit the components and
versions in the Batik product here. My feeling is that we could have a 1.8
release before 2.0.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: batik-dev-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: batik-dev-help@xmlgraphics.apache.org
DO NOT REPLY [Bug 45397] Missing target milestones in bug reporting
tool
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=45397
Helder Magalhães <he...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |VERIFIED
--- Comment #4 from Helder Magalhães <he...@gmail.com> 2008-12-22 07:38:48 PST ---
(In reply to comment #2)
> I think making a bug for dropping 1.4 support, and adding it as a dependency
> for other bugs that have patches for actual removal of 1.4 support is a good
> idea.
Thanks for your feedback, Cameron. :-) I've just created bug 46434 [1].
> My feeling is that we could have a 1.8 release before 2.0.
Agreed. There is a (small) number of quite interesting bug fixes and/or
features since 1.7 which surely should make it to the masses before such a
conceptual release ("2.0"). ;-)
(In reply to comment #3)
> I've changed the 2.0 version to 1.8, and added an additional component for
> animation support. I'm not adding any milestones for now, and suggest doing
> the above if Java version support drop tracking is needed.
Great - the newly created issue makes use of this new version, although I've
suggested [1] milestones to allow scheduling of bugs to specific targets
versions.
[1] https://issues.apache.org/bugzilla/show_bug.cgi?id=46434
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: batik-dev-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: batik-dev-help@xmlgraphics.apache.org
DO NOT REPLY [Bug 45397] Missing target milestones in bug reporting
tool
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=45397
Cameron McCormack <ca...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
--- Comment #3 from Cameron McCormack <ca...@apache.org> 2008-12-22 01:51:01 PST ---
(In reply to comment #2)
> I think making a bug for dropping 1.4 support, and adding it as a dependency
> for other bugs that have patches for actual removal of 1.4 support is a good
> idea.
>
> I've just asked infrastructure to give me access to edit the components and
> versions in the Batik product here. My feeling is that we could have a 1.8
> release before 2.0.
I've changed the 2.0 version to 1.8, and added an additional component for
animation support. I'm not adding any milestones for now, and suggest doing
the above if Java version support drop tracking is needed.
Thanks,
Cameron
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: batik-dev-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: batik-dev-help@xmlgraphics.apache.org