Grzegorz Kossakowski wrote:
Reinhard Poetz napisał(a):
Unless we have big concerns, we should have only one series of release
candidates and than a final release of all modules that have been
releases as milestones so far. As said some days ago, I plan to
release in the week after the Easter break.
Releasing more than half of ours modules is *a lot* of work. After the
series of final releases (scheduled for May), we should only release
modules that have significant improvements or bugfixes.
I agree with all you said. Now, I wonder if we could create subprojects
for most active Cocoon blocks/modules. Currently we use components for
separation but AFAIK they can't have version independent from owning
project.
Is it technically possible to create these subprojects?
I guess yes but this will require our own JIRA instance. This shouldn't be
impossible because other Apache projects have their own but I don't know if
Infra would be particularly happy with such a request.
--
Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
--------------------------------------------------------------------
