RC3 status update

[Hamilton Verissimo]

Guys,

Just an update and call for help.

-- Documentation

I've added lots of stubs to the xdocs site, so we know what needs to
be documented. I dont think we need to complete those before releasing
it. We can get back to it later

-- Branch

If someone wasnt to start merging the trunk with the 1.0. branch, I'd
really appreciate.

-- WiX setup

This needs to be updated as well. I think I can start tonight, but I'm
using my energy to work on the new generator. If someone feels like
jumping in, be my guest.

-- The NewGenerator

This is something I'm building based on our needs here at Stronghold.
It should create a project structure and allow to add an AR project,
AR Models, Controllers (with or without windsor). It's quite
challenging, especially if you consider changing/updating VS solutions
and projects. But so far I think it's going on smoothly.
Also, if someone more capable can work on the nant scripts templates
for it, that would be great.


If you intend to work on some of these bullets, please let us know

Thanks

--
Cheers,
hamilton verissimo
hammett@...
http://www.castlestronghold.com/

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Castle Project Development List" group.
To post to this group, send email to castle-project-devel@...
To unsubscribe from this group, send email to castle-project-devel-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en
-~----------~----~----~----~------~----~------~--~---

[Ayende Rahien-2]

Why do we want to merge it with the 1.0 branch?
Are there any bug fixes there that are not on the trunk?

On 8/28/07, Hamilton Verissimo <hammett@...> wrote:

Guys,

Just an update and call for help.

-- Documentation

I've added lots of stubs to the xdocs site, so we know what needs to
be documented. I dont think we need to complete those before releasing
it. We can get back to it later

-- Branch

If someone wasnt to start merging the trunk with the 1.0. branch, I'd
really appreciate.

-- WiX setup

This needs to be updated as well. I think I can start tonight, but I'm
using my energy to work on the new generator. If someone feels like
jumping in, be my guest.

-- The NewGenerator

This is something I'm building based on our needs here at Stronghold.
It should create a project structure and allow to add an AR project,
AR Models, Controllers (with or without windsor). It's quite
challenging, especially if you consider changing/updating VS solutions
and projects. But so far I think it's going on smoothly.
Also, if someone more capable can work on the nant scripts templates
for it, that would be great.


If you intend to work on some of these bullets, please let us know

Thanks

--
Cheers,
hamilton verissimo
hammett@...
http://www.castlestronghold.com/
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Castle Project Development List" group.
To post to this group, send email to castle-project-devel@...
To unsubscribe from this group, send email to castle-project-devel-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en
-~----------~----~----~----~------~----~------~--~---

[josh robb]

On 8/28/07, Ayende Rahien <ayende@...> wrote:
> Why do we want to merge it with the 1.0 branch?
> Are there any bug fixes there that are not on the trunk?


Amen - Shouldn't we just create a new branch?

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Castle Project Development List" group.
To post to this group, send email to castle-project-devel@...
To unsubscribe from this group, send email to castle-project-devel-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en
-~----------~----~----~----~------~----~------~--~---

[Hamilton Verissimo]

No brave man volunteering?

On 8/28/07, Hamilton Verissimo <hammett@...> wrote:

> Guys,
>
> Just an update and call for help.
>
> -- Documentation
>
> I've added lots of stubs to the xdocs site, so we know what needs to
> be documented. I dont think we need to complete those before releasing
> it. We can get back to it later
>
> -- Branch
>
> If someone wasnt to start merging the trunk with the 1.0. branch, I'd
> really appreciate.
>
> -- WiX setup
>
> This needs to be updated as well. I think I can start tonight, but I'm
> using my energy to work on the new generator. If someone feels like
> jumping in, be my guest.
>
> -- The NewGenerator
>
> This is something I'm building based on our needs here at Stronghold.
> It should create a project structure and allow to add an AR project,
> AR Models, Controllers (with or without windsor). It's quite
> challenging, especially if you consider changing/updating VS solutions
> and projects. But so far I think it's going on smoothly.
> Also, if someone more capable can work on the nant scripts templates
> for it, that would be great.
>
>
> If you intend to work on some of these bullets, please let us know
>
> Thanks
>
> --
> Cheers,
> hamilton verissimo
> hammett@...
> http://www.castlestronghold.com/
>

--
Cheers,
hamilton verissimo
hammett@...
http://www.castlestronghold.com/

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Castle Project Development List" group.
To post to this group, send email to castle-project-devel@...
To unsubscribe from this group, send email to castle-project-devel-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en
-~----------~----~----~----~------~----~------~--~---

[Ayende Rahien-2]

I will try on the weekend

On 8/29/07, Hamilton Verissimo <hammett@...> wrote:

No brave man volunteering?

On 8/28/07, Hamilton Verissimo <hammett@...> wrote:

> Guys,
>
> Just an update and call for help.
>
> -- Documentation
>
> I've added lots of stubs to the xdocs site, so we know what needs to
> be documented. I dont think we need to complete those before releasing
> it. We can get back to it later
>
> -- Branch
>
> If someone wasnt to start merging the trunk with the 1.0. branch, I'd
> really appreciate.
>
> -- WiX setup
>
> This needs to be updated as well. I think I can start tonight, but I'm
> using my energy to work on the new generator. If someone feels like
> jumping in, be my guest.
>
> -- The NewGenerator
>
> This is something I'm building based on our needs here at Stronghold.
> It should create a project structure and allow to add an AR project,
> AR Models, Controllers (with or without windsor). It's quite
> challenging, especially if you consider changing/updating VS solutions
> and projects. But so far I think it's going on smoothly.
> Also, if someone more capable can work on the nant scripts templates
> for it, that would be great.
>
>
> If you intend to work on some of these bullets, please let us know
>
> Thanks
>
> --
> Cheers,
> hamilton verissimo
> hammett@...
> http://www.castlestronghold.com/
>

--
Cheers,
hamilton verissimo
hammett@...
http://www.castlestronghold.com/

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Castle Project Development List" group.
To post to this group, send email to castle-project-devel@...
To unsubscribe from this group, send email to castle-project-devel-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en
-~----------~----~----~----~------~----~------~--~---

[Markus Zywitza]

Something else:

There are currently 29 open bugs (see link below) in JIRA. Should we
really branch with this number of open bugs? All those fixes must be
backported to the trunk then.
My proposal is to allocate fix versions to each bug, and then decide
whether to branch the trunk for the RC or whether to reduce the number
of bugs first.

JIRA permlink:
http://support.castleproject.org/secure/IssueNavigator.jspa?reset=true&&type=1&pid=10001&pid=10006&pid=10008&pid=10050&pid=10040&pid=10003&pid=10004&pid=10002&pid=10000&pid=10020&pid=10010&resolution=-1&priority=1&priority=2&priority=3&status=1&status=3&status=4&sorter/field=issuekey&sorter/order=DESC

-Markus

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Castle Project Development List" group.
To post to this group, send email to castle-project-devel@...
To unsubscribe from this group, send email to castle-project-devel-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en
-~----------~----~----~----~------~----~------~--~---

[Hamilton Verissimo]

If we stop to release only when all bugs are fixed we will never
release... What I'm doing is fixing what I consider very important, so
we minimize the risk of making the trunk unstable.

On 8/30/07, Markus Zywitza <markus.zywitza@...> wrote:

>
> Something else:
>
> There are currently 29 open bugs (see link below) in JIRA. Should we
> really branch with this number of open bugs? All those fixes must be
> backported to the trunk then.
> My proposal is to allocate fix versions to each bug, and then decide
> whether to branch the trunk for the RC or whether to reduce the number
> of bugs first.
>
> JIRA permlink:
> http://support.castleproject.org/secure/IssueNavigator.jspa?reset=true&&type=1&pid=10001&pid=10006&pid=10008&pid=10050&pid=10040&pid=10003&pid=10004&pid=10002&pid=10000&pid=10020&pid=10010&resolution=-1&priority=1&priority=2&priority=3&status=1&status=3&status=4&sorter/field=issuekey&sorter/order=DESC
>
> -Markus
>
> >
>

--
Cheers,
hamilton verissimo
hammett@...
http://www.castlestronghold.com/

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Castle Project Development List" group.
To post to this group, send email to castle-project-devel@...
To unsubscribe from this group, send email to castle-project-devel-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en
-~----------~----~----~----~------~----~------~--~---

[josh robb]

On 8/30/07, Hamilton Verissimo <hammett@...> wrote:
> If we stop to release only when all bugs are fixed we will never
> release... What I'm doing is fixing what I consider very important, so
> we minimize the risk of making the trunk unstable.

Agreed - however shouldn't we have a list of bugs which we consider
blockers for this release?

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Castle Project Development List" group.
To post to this group, send email to castle-project-devel@...
To unsubscribe from this group, send email to castle-project-devel-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en
-~----------~----~----~----~------~----~------~--~---

[James Curran-2]

JIRA does provide a "Priority" field, where one choice is "Blocker" (with no items presently cited as such), and another,  "Critical" (2 issues).  So all that is really needed is a possible re-assessment of those assignments.  (Priority can be filtered on --- it's on the bottom left on the Issue Navigator page)

 

On 8/30/07, josh robb <josh_robb@...> wrote:

Agreed - however shouldn't we have a list of bugs which we consider
blockers for this release?

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Castle Project Development List" group.
To post to this group, send email to castle-project-devel@...
To unsubscribe from this group, send email to castle-project-devel-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en
-~----------~----~----~----~------~----~------~--~---

[Roelof Blom]

It would help if we revise the JIRA 'Fix Version/s:' field of the open issues, and put in the version (we think) it's going to be fixed in. Right now there are lots of issues that are 'unscheduled', effectively rendering the Roadmap view of JIRA unusable. This Roadmap is a nice way to drive development towards the upcoming RC, and upcoming releases.

I also propose a 'Future' Fix Version, this way issues can be scheduled after the current release and still show up on the roadmap.

What also would help if we communicate what the specific versions of the individual projects are in Castle RC3, something like this:

• AR RC2
• COMP RC1? (currently not versioned in JIRA)
• CORE RC1? (currently not versioned in JIRA)
• DYNPROXY (no idea, currently 3 different versions http://support.castleproject.org/browse/DYNPROXY?report=com.atlassian.jira.plugin.system.project:roadmap-panel)
• FACILITIES BETA3
• IOC RC4
• MR RC3
• NVELOCITY RC1? (currently not versioned in JIRA)
• SERVICES RC1? (currently not versioned in JIRA)

As you can see the versioning needs a little love.

-- Roelof.

On 8/30/07, James Curran <james.curran@...> wrote:

JIRA does provide a "Priority" field, where one choice is "Blocker" (with no items presently cited as such), and another,  "Critical" (2 issues).  So all that is really needed is a possible re-assessment of those assignments.  (Priority can be filtered on --- it's on the bottom left on the Issue Navigator page)

 

On 8/30/07, josh robb <josh_robb@...> wrote:

Agreed - however shouldn't we have a list of bugs which we consider
blockers for this release?

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Castle Project Development List" group.
To post to this group, send email to castle-project-devel@...
To unsubscribe from this group, send email to castle-project-devel-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en
-~----------~----~----~----~------~----~------~--~---

[Hamilton Verissimo]

I'm asking for help, not for more aggravation :-)

On 8/31/07, Roelof Blom <roelof.blom@...> wrote:

> It would help if we revise the JIRA 'Fix Version/s:' field of the open
> issues, and put in the version (we think) it's going to be fixed in. Right
> now there are lots of issues that are 'unscheduled', effectively rendering
> the Roadmap view of JIRA unusable. This Roadmap is a nice way to drive
> development towards the upcoming RC, and upcoming releases.
>
> I also propose a 'Future' Fix Version, this way issues can be scheduled
> after the current release and still show up on the roadmap.
>
> What also would help if we communicate what the specific versions of the
> individual projects are in Castle RC3, something like this:
>
> AR RC2
> COMP RC1? (currently not versioned in JIRA)
> CORE RC1? (currently not versioned in JIRA)
> DYNPROXY (no idea, currently 3 different versions
> http://support.castleproject.org/browse/DYNPROXY?report=com.atlassian.jira.plugin.system.project:roadmap-panel)
> FACILITIES BETA3
> IOC RC4
> MR RC3
> NVELOCITY RC1? (currently not versioned in JIRA)
> SERVICES RC1? (currently not versioned in JIRA)As you can see the versioning
> needs a little love.
>
> -- Roelof.
>
>
> On 8/30/07, James Curran <james.curran@...> wrote:
> >
> > JIRA does provide a "Priority" field, where one choice is "Blocker" (with
> no items presently cited as such), and another,  "Critical" (2 issues).  So
> all that is really needed is a possible re-assessment of those assignments.
> (Priority can be filtered on --- it's on the bottom left on the Issue
> Navigator page)
> >
> >
> >
> > On 8/30/07, josh robb <josh_robb@... > wrote:
> > >
> > > Agreed - however shouldn't we have a list of bugs which we consider
> > > blockers for this release?
> > >
> >
> >
> >
>
>
>  >
>

--
Cheers,
hamilton verissimo
hammett@...
http://www.castlestronghold.com/

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Castle Project Development List" group.
To post to this group, send email to castle-project-devel@...
To unsubscribe from this group, send email to castle-project-devel-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en
-~----------~----~----~----~------~----~------~--~---

[Roelof Blom]

:-) It was meant as help, and I will update JIRA this weekend with the proposed 'Future' Fix version and assign any issue without a fix version to 'Future', if there are no objections. From there one we can move them in desired versions.

BTW, does the list of versions seem correct? If it doesn't please fix, as I will use this list to create versions in the JIRA projects.

On 8/31/07, Hamilton Verissimo <hammett@...> wrote:

I'm asking for help, not for more aggravation :-)

On 8/31/07, Roelof Blom <roelof.blom@...> wrote:

> It would help if we revise the JIRA 'Fix Version/s:' field of the open
> issues, and put in the version (we think) it's going to be fixed in. Right
> now there are lots of issues that are 'unscheduled', effectively rendering
> the Roadmap view of JIRA unusable. This Roadmap is a nice way to drive
> development towards the upcoming RC, and upcoming releases.
>
> I also propose a 'Future' Fix Version, this way issues can be scheduled
> after the current release and still show up on the roadmap.
>
> What also would help if we communicate what the specific versions of the
> individual projects are in Castle RC3, something like this:
>
> AR RC2
> COMP RC1? (currently not versioned in JIRA)
> CORE RC1? (currently not versioned in JIRA)
> DYNPROXY (no idea, currently 3 different versions
> http://support.castleproject.org/browse/DYNPROXY?report=com.atlassian.jira.plugin.system.project:roadmap-panel)
> FACILITIES BETA3
> IOC RC4
> MR RC3
> NVELOCITY RC1? (currently not versioned in JIRA)
> SERVICES RC1? (currently not versioned in JIRA)As you can see the versioning
> needs a little love.
>
> -- Roelof.
>
>
> On 8/30/07, James Curran <james.curran@...> wrote:
> >
> > JIRA does provide a "Priority" field, where one choice is "Blocker" (with
> no items presently cited as such), and another,  "Critical" (2 issues).  So
> all that is really needed is a possible re-assessment of those assignments.
> (Priority can be filtered on --- it's on the bottom left on the Issue
> Navigator page)
> >
> >
> >
> > On 8/30/07, josh robb <josh_robb@... > wrote:
> > >
> > > Agreed - however shouldn't we have a list of bugs which we consider
> > > blockers for this release?
> > >
> >
> >
> >
>
>
>  >
>

--
Cheers,
hamilton verissimo
hammett@...
http://www.castlestronghold.com/
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Castle Project Development List" group.
To post to this group, send email to castle-project-devel@...
To unsubscribe from this group, send email to castle-project-devel-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en
-~----------~----~----~----~------~----~------~--~---

[Roelof Blom]

Some parts of this message have been removed. Learn more about Nabble's security policy.

Done. I've added the 'Future' version to all projects and assigned it to unscheduled issues. (Sorry about the 15 emails from the first JIRA bulk change).

On 8/31/07, Roelof Blom <roelof.blom@...> wrote:

:-) It was meant as help, and I will update JIRA this weekend with the proposed 'Future' Fix version and assign any issue without a fix version to 'Future', if there are no objections. From there one we can move them in desired versions.

BTW, does the list of versions seem correct? If it doesn't please fix, as I will use this list to create versions in the JIRA projects.

On 8/31/07, Hamilton Verissimo <hammett@...> wrote:

I'm asking for help, not for more aggravation :-)

On 8/31/07, Roelof Blom <roelof.blom@...> wrote:

> It would help if we revise the JIRA 'Fix Version/s:' field of the open
> issues, and put in the version (we think) it's going to be fixed in. Right
> now there are lots of issues that are 'unscheduled', effectively rendering
> the Roadmap view of JIRA unusable. This Roadmap is a nice way to drive
> development towards the upcoming RC, and upcoming releases.
>
> I also propose a 'Future' Fix Version, this way issues can be scheduled
> after the current release and still show up on the roadmap.
>
> What also would help if we communicate what the specific versions of the
> individual projects are in Castle RC3, something like this:
>
> AR RC2
> COMP RC1? (currently not versioned in JIRA)
> CORE RC1? (currently not versioned in JIRA)
> DYNPROXY (no idea, currently 3 different versions
> http://support.castleproject.org/browse/DYNPROXY?report=com.atlassian.jira.plugin.system.project:roadmap-panel)
> FACILITIES BETA3
> IOC RC4
> MR RC3
> NVELOCITY RC1? (currently not versioned in JIRA)
> SERVICES RC1? (currently not versioned in JIRA)As you can see the versioning
> needs a little love.
>
> -- Roelof.
>
>
> On 8/30/07, James Curran <james.curran@...> wrote:
> >
> > JIRA does provide a "Priority" field, where one choice is "Blocker" (with
> no items presently cited as such), and another,  "Critical" (2 issues).  So
> all that is really needed is a possible re-assessment of those assignments.
> (Priority can be filtered on --- it's on the bottom left on the Issue
> Navigator page)
> >
> >

> >

> > On 8/30/07, josh robb <josh_robb@... > wrote:
> > >
> > > Agreed - however shouldn't we have a list of bugs which we consider
> > > blockers for this release?
> > >
> >
> >
> >
>
>
>  >
>

--
Cheers,
hamilton verissimo
hammett@...
http://www.castlestronghold.com/

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Castle Project Development List" group.
To post to this group, send email to castle-project-devel@...
To unsubscribe from this group, send email to castle-project-devel-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en
-~----------~----~----~----~------~----~------~--~---

[Hamilton Verissimo]

Thanks man!

On 8/31/07, Roelof Blom <roelof.blom@...> wrote:

> Done. I've added the 'Future' version to all projects and assigned it to
> unscheduled issues. (Sorry about the 15 emails from the first JIRA bulk
> change).
>
>
> On 8/31/07, Roelof Blom <roelof.blom@...> wrote:
> > :-) It was meant as help, and I will update JIRA this weekend with the
> proposed 'Future' Fix version and assign any issue without a fix version to
> 'Future', if there are no objections. From there one we can move them in
> desired versions.
> >
> > BTW, does the list of versions seem correct? If it doesn't please fix, as
> I will use this list to create versions in the JIRA projects.
> >
> >
> >
> > On 8/31/07, Hamilton Verissimo <hammett@...> wrote:
> > >
> > > I'm asking for help, not for more aggravation :-)
> > >
> > > On 8/31/07, Roelof Blom <roelof.blom@... > wrote:
> > > > It would help if we revise the JIRA 'Fix Version/s:' field of the open
> > > > issues, and put in the version (we think) it's going to be fixed in.
> Right
> > > > now there are lots of issues that are 'unscheduled', effectively
> rendering
> > > > the Roadmap view of JIRA unusable. This Roadmap is a nice way to drive
> > > > development towards the upcoming RC, and upcoming releases.
> > > >
> > > > I also propose a 'Future' Fix Version, this way issues can be
> scheduled
> > > > after the current release and still show up on the roadmap.
> > > >
> > > > What also would help if we communicate what the specific versions of
> the
> > > > individual projects are in Castle RC3, something like this:
> > > >
> > > > AR RC2
> > > > COMP RC1? (currently not versioned in JIRA)
> > > > CORE RC1? (currently not versioned in JIRA)
> > > > DYNPROXY (no idea, currently 3 different versions
> > > >
> http://support.castleproject.org/browse/DYNPROXY?report=com.atlassian.jira.plugin.system.project:roadmap-panel)
> > > > FACILITIES BETA3
> > > > IOC RC4
> > > > MR RC3
> > > > NVELOCITY RC1? (currently not versioned in JIRA)
> > > > SERVICES RC1? (currently not versioned in JIRA)As you can see the
> versioning
> > > > needs a little love.
> > > >
> > > > -- Roelof.
> > > >
> > > >
> > > > On 8/30/07, James Curran < james.curran@...> wrote:
> > > > >
> > > > > JIRA does provide a "Priority" field, where one choice is "Blocker"
> (with
> > > > no items presently cited as such), and another,  "Critical" (2
> issues).  So
> > > > all that is really needed is a possible re-assessment of those
> assignments.
> > > > (Priority can be filtered on --- it's on the bottom left on the Issue
> > > > Navigator page)
> > > > >
> > > > >
> > > > >
> > > > > On 8/30/07, josh robb <josh_robb@... > wrote:
> > > > > >
> > > > > > Agreed - however shouldn't we have a list of bugs which we
> consider
> > > > > > blockers for this release?
> > > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > >  >
> > > >
> > >
> > >
> > > --
> > > Cheers,
> > > hamilton verissimo
> > > hammett@...
> > > http://www.castlestronghold.com/
> > >
> > >
> >
>
>
>  >
>

--
Cheers,
hamilton verissimo
hammett@...
http://www.castlestronghold.com/

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Castle Project Development List" group.
To post to this group, send email to castle-project-devel@...
To unsubscribe from this group, send email to castle-project-devel-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en
-~----------~----~----~----~------~----~------~--~---

[Roelof Blom]

Just de-aggrevating you somewhat :-)

On 8/31/07, Hamilton Verissimo <hammett@...> wrote:

Thanks man!

On 8/31/07, Roelof Blom <roelof.blom@...> wrote:

> Done. I've added the 'Future' version to all projects and assigned it to
> unscheduled issues. (Sorry about the 15 emails from the first JIRA bulk
> change).
>
>
> On 8/31/07, Roelof Blom <roelof.blom@...> wrote:
> > :-) It was meant as help, and I will update JIRA this weekend with the
> proposed 'Future' Fix version and assign any issue without a fix version to
> 'Future', if there are no objections. From there one we can move them in
> desired versions.
> >
> > BTW, does the list of versions seem correct? If it doesn't please fix, as

> I will use this list to create versions in the JIRA projects.

> >
> >
> >
> > On 8/31/07, Hamilton Verissimo <hammett@...> wrote:
> > >
> > > I'm asking for help, not for more aggravation :-)
> > >
> > > On 8/31/07, Roelof Blom <roelof.blom@... > wrote:
> > > > It would help if we revise the JIRA 'Fix Version/s:' field of the open
> > > > issues, and put in the version (we think) it's going to be fixed in.
> Right
> > > > now there are lots of issues that are 'unscheduled', effectively
> rendering
> > > > the Roadmap view of JIRA unusable. This Roadmap is a nice way to drive
> > > > development towards the upcoming RC, and upcoming releases.
> > > >
> > > > I also propose a 'Future' Fix Version, this way issues can be
> scheduled
> > > > after the current release and still show up on the roadmap.

> > > >

> > > > What also would help if we communicate what the specific versions of
> the
> > > > individual projects are in Castle RC3, something like this:
> > > >
> > > > AR RC2
> > > > COMP RC1? (currently not versioned in JIRA)
> > > > CORE RC1? (currently not versioned in JIRA)
> > > > DYNPROXY (no idea, currently 3 different versions
> > > >
> http://support.castleproject.org/browse/DYNPROXY?report=com.atlassian.jira.plugin.system.project:roadmap-panel )
> > > > FACILITIES BETA3
> > > > IOC RC4
> > > > MR RC3
> > > > NVELOCITY RC1? (currently not versioned in JIRA)
> > > > SERVICES RC1? (currently not versioned in JIRA)As you can see the
> versioning
> > > > needs a little love.
> > > >
> > > > -- Roelof.
> > > >
> > > >
> > > > On 8/30/07, James Curran < james.curran@...> wrote:
> > > > >
> > > > > JIRA does provide a "Priority" field, where one choice is "Blocker"
> (with
> > > > no items presently cited as such), and another,  "Critical" (2
> issues).  So
> > > > all that is really needed is a possible re-assessment of those
> assignments.
> > > > (Priority can be filtered on --- it's on the bottom left on the Issue
> > > > Navigator page)
> > > > >
> > > > >
> > > > >
> > > > > On 8/30/07, josh robb <josh_robb@... > wrote:
> > > > > >
> > > > > > Agreed - however shouldn't we have a list of bugs which we
> consider
> > > > > > blockers for this release?
> > > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > >  >
> > > >
> > >
> > >
> > > --
> > > Cheers,
> > > hamilton verissimo
> > > hammett@...
> > > http://www.castlestronghold.com/
> > >
> > >
> >
>
>
>  >
>

--
Cheers,
hamilton verissimo
hammett@...
http://www.castlestronghold.com/
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Castle Project Development List" group.
To post to this group, send email to castle-project-devel@...
To unsubscribe from this group, send email to castle-project-devel-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en
-~----------~----~----~----~------~----~------~--~---

[goodwill-4]

hey man how to test newgenerator? Is that in a level usable so I could
test it out?

On Sep 1, 4:02 am, "Hamilton Verissimo" <hamm...@...>
wrote:

> Thanks man!
>
> On 8/31/07, Roelof Blom <roelof.b...@...> wrote:
>
>
>
> > Done. I've added the 'Future' version to all projects and assigned it to
> > unscheduled issues. (Sorry about the 15 emails from the first JIRA bulk
> > change).
>
> > On 8/31/07, Roelof Blom <roelof.b...@...> wrote:
> > > :-) It was meant as help, and I will update JIRA this weekend with the
> > proposed 'Future' Fix version and assign any issue without a fix version to
> > 'Future', if there are no objections. From there one we can move them in
> > desired versions.
>
> > > BTW, does the list of versions seem correct? If it doesn't please fix, as
> > I will use this list to create versions in the JIRA projects.
>
> > > On 8/31/07, Hamilton Verissimo <hamm...@...> wrote:
>
> > > > I'm asking for help, not for more aggravation :-)
>
> > > > On 8/31/07, Roelof Blom <roelof.b...@... > wrote:
> > > > > It would help if we revise the JIRA 'Fix Version/s:' field of the open
> > > > > issues, and put in the version (we think) it's going to be fixed in.
> > Right
> > > > > now there are lots of issues that are 'unscheduled', effectively
> > rendering
> > > > > the Roadmap view of JIRA unusable. This Roadmap is a nice way to drive
> > > > > development towards the upcoming RC, and upcoming releases.
>
> > > > > I also propose a 'Future' Fix Version, this way issues can be
> > scheduled
> > > > > after the current release and still show up on the roadmap.
>
> > > > > What also would help if we communicate what the specific versions of
> > the
> > > > > individual projects are in Castle RC3, something like this:
>
> > > > > AR RC2
> > > > > COMP RC1? (currently not versioned in JIRA)
> > > > > CORE RC1? (currently not versioned in JIRA)
> > > > > DYNPROXY (no idea, currently 3 different versions
>
> >http://support.castleproject.org/browse/DYNPROXY?report=com.atlassian...)
> > > > > FACILITIES BETA3
> > > > > IOC RC4
> > > > > MR RC3
> > > > > NVELOCITY RC1? (currently not versioned in JIRA)
> > > > > SERVICES RC1? (currently not versioned in JIRA)As you can see the
> > versioning
> > > > > needs a little love.
>
> > > > > -- Roelof.
>
> > > > > On 8/30/07, James Curran < james.cur...@...> wrote:
>
> > > > > > JIRA does provide a "Priority" field, where one choice is "Blocker"
> > (with
> > > > > no items presently cited as such), and another,  "Critical" (2
> > issues).  So
> > > > > all that is really needed is a possible re-assessment of those
> > assignments.
> > > > > (Priority can be filtered on --- it's on the bottom left on the Issue
> > > > > Navigator page)
>
> > > > > > On 8/30/07, josh robb <josh_r...@... > wrote:
>
> > > > > > > Agreed - however shouldn't we have a list of bugs which we
> > consider
> > > > > > > blockers for this release?
>
> > > > --
> > > > Cheers,
> > > > hamilton verissimo
> > > > hamm...@...
> > > >http://www.castlestronghold.com/
>
> --
> Cheers,
> hamilton verissimo
> hamm...@...://www.castlestronghold.com/

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Castle Project Development List" group.
To post to this group, send email to castle-project-devel@...
To unsubscribe from this group, send email to castle-project-devel-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en
-~----------~----~----~----~------~----~------~--~---

[Hamilton Verissimo]

Not really dude, sorry. I'm installing leopard on my machine, removed
my bootcamp partition and I'm restoring win backups, so it's going to
take some time to get up to speed with the code again.

On 8/31/07, goodwill <william.yeung.hk@...> wrote:

>
> hey man how to test newgenerator? Is that in a level usable so I could
> test it out?
>
> On Sep 1, 4:02 am, "Hamilton Verissimo" <hamm...@...>
> wrote:
> > Thanks man!
> >
> > On 8/31/07, Roelof Blom <roelof.b...@...> wrote:
> >
> >
> >
> > > Done. I've added the 'Future' version to all projects and assigned it to
> > > unscheduled issues. (Sorry about the 15 emails from the first JIRA bulk
> > > change).
> >
> > > On 8/31/07, Roelof Blom <roelof.b...@...> wrote:
> > > > :-) It was meant as help, and I will update JIRA this weekend with the
> > > proposed 'Future' Fix version and assign any issue without a fix version to
> > > 'Future', if there are no objections. From there one we can move them in
> > > desired versions.
> >
> > > > BTW, does the list of versions seem correct? If it doesn't please fix, as
> > > I will use this list to create versions in the JIRA projects.
> >
> > > > On 8/31/07, Hamilton Verissimo <hamm...@...> wrote:
> >
> > > > > I'm asking for help, not for more aggravation :-)
> >
> > > > > On 8/31/07, Roelof Blom <roelof.b...@... > wrote:
> > > > > > It would help if we revise the JIRA 'Fix Version/s:' field of the open
> > > > > > issues, and put in the version (we think) it's going to be fixed in.
> > > Right
> > > > > > now there are lots of issues that are 'unscheduled', effectively
> > > rendering
> > > > > > the Roadmap view of JIRA unusable. This Roadmap is a nice way to drive
> > > > > > development towards the upcoming RC, and upcoming releases.
> >
> > > > > > I also propose a 'Future' Fix Version, this way issues can be
> > > scheduled
> > > > > > after the current release and still show up on the roadmap.
> >
> > > > > > What also would help if we communicate what the specific versions of
> > > the
> > > > > > individual projects are in Castle RC3, something like this:
> >
> > > > > > AR RC2
> > > > > > COMP RC1? (currently not versioned in JIRA)
> > > > > > CORE RC1? (currently not versioned in JIRA)
> > > > > > DYNPROXY (no idea, currently 3 different versions
> >
> > >http://support.castleproject.org/browse/DYNPROXY?report=com.atlassian...)
> > > > > > FACILITIES BETA3
> > > > > > IOC RC4
> > > > > > MR RC3
> > > > > > NVELOCITY RC1? (currently not versioned in JIRA)
> > > > > > SERVICES RC1? (currently not versioned in JIRA)As you can see the
> > > versioning
> > > > > > needs a little love.
> >
> > > > > > -- Roelof.
> >
> > > > > > On 8/30/07, James Curran < james.cur...@...> wrote:
> >
> > > > > > > JIRA does provide a "Priority" field, where one choice is "Blocker"
> > > (with
> > > > > > no items presently cited as such), and another,  "Critical" (2
> > > issues).  So
> > > > > > all that is really needed is a possible re-assessment of those
> > > assignments.
> > > > > > (Priority can be filtered on --- it's on the bottom left on the Issue
> > > > > > Navigator page)
> >
> > > > > > > On 8/30/07, josh robb <josh_r...@... > wrote:
> >
> > > > > > > > Agreed - however shouldn't we have a list of bugs which we
> > > consider
> > > > > > > > blockers for this release?
> >
> > > > > --
> > > > > Cheers,
> > > > > hamilton verissimo
> > > > > hamm...@...
> > > > >http://www.castlestronghold.com/
> >
> > --
> > Cheers,
> > hamilton verissimo
> > hamm...@...://www.castlestronghold.com/
>
>
> >
>

--
Cheers,
hamilton verissimo
hammett@...
http://www.castlestronghold.com/

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Castle Project Development List" group.
To post to this group, send email to castle-project-devel@...
To unsubscribe from this group, send email to castle-project-devel-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en
-~----------~----~----~----~------~----~------~--~---

[goodwill-4]

Its ok, just keep us informed- I would be really happy to help on
testing and some patch work once I know more about it.

On Sep 1, 10:41 am, "Hamilton Verissimo"
<hamm...@...> wrote:

> Not really dude, sorry. I'm installing leopard on my machine, removed
> my bootcamp partition and I'm restoring win backups, so it's going to
> take some time to get up to speed with the code again.
>
> On 8/31/07, goodwill <william.yeung...@...> wrote:
>
>
>
>
>
>
>
> > hey man how to test newgenerator? Is that in a level usable so I could
> > test it out?
>
> > On Sep 1, 4:02 am, "Hamilton Verissimo" <hamm...@...>
> > wrote:
> > > Thanks man!
>
> > > On 8/31/07, Roelof Blom <roelof.b...@...> wrote:
>
> > > > Done. I've added the 'Future' version to all projects and assigned it to
> > > > unscheduled issues. (Sorry about the 15 emails from the first JIRA bulk
> > > > change).
>
> > > > On 8/31/07, Roelof Blom <roelof.b...@...> wrote:
> > > > > :-) It was meant as help, and I will update JIRA this weekend with the
> > > > proposed 'Future' Fix version and assign any issue without a fix version to
> > > > 'Future', if there are no objections. From there one we can move them in
> > > > desired versions.
>
> > > > > BTW, does the list of versions seem correct? If it doesn't please fix, as
> > > > I will use this list to create versions in the JIRA projects.
>
> > > > > On 8/31/07, Hamilton Verissimo <hamm...@...> wrote:
>
> > > > > > I'm asking for help, not for more aggravation :-)
>
> > > > > > On 8/31/07, Roelof Blom <roelof.b...@... > wrote:
> > > > > > > It would help if we revise the JIRA 'Fix Version/s:' field of the open
> > > > > > > issues, and put in the version (we think) it's going to be fixed in.
> > > > Right
> > > > > > > now there are lots of issues that are 'unscheduled', effectively
> > > > rendering
> > > > > > > the Roadmap view of JIRA unusable. This Roadmap is a nice way to drive
> > > > > > > development towards the upcoming RC, and upcoming releases.
>
> > > > > > > I also propose a 'Future' Fix Version, this way issues can be
> > > > scheduled
> > > > > > > after the current release and still show up on the roadmap.
>
> > > > > > > What also would help if we communicate what the specific versions of
> > > > the
> > > > > > > individual projects are in Castle RC3, something like this:
>
> > > > > > > AR RC2
> > > > > > > COMP RC1? (currently not versioned in JIRA)
> > > > > > > CORE RC1? (currently not versioned in JIRA)
> > > > > > > DYNPROXY (no idea, currently 3 different versions
>
> > > >http://support.castleproject.org/browse/DYNPROXY?report=com.atlassian...)
> > > > > > > FACILITIES BETA3
> > > > > > > IOC RC4
> > > > > > > MR RC3
> > > > > > > NVELOCITY RC1? (currently not versioned in JIRA)
> > > > > > > SERVICES RC1? (currently not versioned in JIRA)As you can see the
> > > > versioning
> > > > > > > needs a little love.
>
> > > > > > > -- Roelof.
>
> > > > > > > On 8/30/07, James Curran < james.cur...@...> wrote:
>
> > > > > > > > JIRA does provide a "Priority" field, where one choice is "Blocker"
> > > > (with
> > > > > > > no items presently cited as such), and another,  "Critical" (2
> > > > issues).  So
> > > > > > > all that is really needed is a possible re-assessment of those
> > > > assignments.
> > > > > > > (Priority can be filtered on --- it's on the bottom left on the Issue
> > > > > > > Navigator page)
>
> > > > > > > > On 8/30/07, josh robb <josh_r...@... > wrote:
>
> > > > > > > > > Agreed - however shouldn't we have a list of bugs which we
> > > > consider
> > > > > > > > > blockers for this release?
>
> > > > > > --
> > > > > > Cheers,
> > > > > > hamilton verissimo
> > > > > > hamm...@...
> > > > > >http://www.castlestronghold.com/
>
> > > --
> > > Cheers,
> > > hamilton verissimo
> > > hamm...@...://www.castlestronghold.com/
>
> --
> Cheers,
> hamilton verissimo
> hamm...@...://www.castlestronghold.com/- Hide quoted text -
>
> - Show quoted text -

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Castle Project Development List" group.
To post to this group, send email to castle-project-devel@...
To unsubscribe from this group, send email to castle-project-devel-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en
-~----------~----~----~----~------~----~------~--~---

[Craig Neuwirt]

Out of curiousity, why are you not using bootcamp anymore?
Are you going to just use parrallels or VMWare for Windows?
Leopard looks really cool, I may try it myself. :^)

I am a recent mac converter to and I am trying to find my ideal environment.
I have always been a Windows + Cygwin + Emacs guy

On 8/31/07, Hamilton Verissimo <hammett@...> wrote:

Not really dude, sorry. I'm installing leopard on my machine, removed
my bootcamp partition and I'm restoring win backups, so it's going to
take some time to get up to speed with the code again.

On 8/31/07, goodwill <william.yeung.hk@...> wrote:

>
> hey man how to test newgenerator? Is that in a level usable so I could
> test it out?
>
> On Sep 1, 4:02 am, "Hamilton Verissimo" <hamm...@...>
> wrote:
> > Thanks man!
> >
> > On 8/31/07, Roelof Blom <roelof.b...@...> wrote:
> >

> >

> >
> > > Done. I've added the 'Future' version to all projects and assigned it to
> > > unscheduled issues. (Sorry about the 15 emails from the first JIRA bulk
> > > change).
> >
> > > On 8/31/07, Roelof Blom <roelof.b...@...> wrote:
> > > > :-) It was meant as help, and I will update JIRA this weekend with the
> > > proposed 'Future' Fix version and assign any issue without a fix version to
> > > 'Future', if there are no objections. From there one we can move them in
> > > desired versions.
> >
> > > > BTW, does the list of versions seem correct? If it doesn't please fix, as
> > > I will use this list to create versions in the JIRA projects.
> >
> > > > On 8/31/07, Hamilton Verissimo < hamm...@...> wrote:
> >
> > > > > I'm asking for help, not for more aggravation :-)
> >
> > > > > On 8/31/07, Roelof Blom < roelof.b...@... > wrote:
> > > > > > It would help if we revise the JIRA 'Fix Version/s:' field of the open
> > > > > > issues, and put in the version (we think) it's going to be fixed in.
> > > Right
> > > > > > now there are lots of issues that are 'unscheduled', effectively
> > > rendering
> > > > > > the Roadmap view of JIRA unusable. This Roadmap is a nice way to drive
> > > > > > development towards the upcoming RC, and upcoming releases.
> >
> > > > > > I also propose a 'Future' Fix Version, this way issues can be
> > > scheduled
> > > > > > after the current release and still show up on the roadmap.
> >
> > > > > > What also would help if we communicate what the specific versions of
> > > the
> > > > > > individual projects are in Castle RC3, something like this:
> >
> > > > > > AR RC2
> > > > > > COMP RC1? (currently not versioned in JIRA)
> > > > > > CORE RC1? (currently not versioned in JIRA)
> > > > > > DYNPROXY (no idea, currently 3 different versions
> >
> > > http://support.castleproject.org/browse/DYNPROXY?report=com.atlassian...)
> > > > > > FACILITIES BETA3
> > > > > > IOC RC4
> > > > > > MR RC3
> > > > > > NVELOCITY RC1? (currently not versioned in JIRA)
> > > > > > SERVICES RC1? (currently not versioned in JIRA)As you can see the
> > > versioning
> > > > > > needs a little love.
> >
> > > > > > -- Roelof.
> >
> > > > > > On 8/30/07, James Curran < james.cur...@...> wrote:
> >
> > > > > > > JIRA does provide a "Priority" field, where one choice is "Blocker"
> > > (with
> > > > > > no items presently cited as such), and another,  "Critical" (2
> > > issues).  So
> > > > > > all that is really needed is a possible re-assessment of those
> > > assignments.
> > > > > > (Priority can be filtered on --- it's on the bottom left on the Issue
> > > > > > Navigator page)
> >
> > > > > > > On 8/30/07, josh robb < josh_r...@... > wrote:
> >
> > > > > > > > Agreed - however shouldn't we have a list of bugs which we
> > > consider
> > > > > > > > blockers for this release?
> >
> > > > > --
> > > > > Cheers,
> > > > > hamilton verissimo
> > > > > hamm...@...
> > > > >http://www.castlestronghold.com/
> >
> > --
> > Cheers,
> > hamilton verissimo
> > hamm...@...://www.castlestronghold.com/
>
>
> >
>

--
Cheers,
hamilton verissimo
hammett@...
http://www.castlestronghold.com/
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Castle Project Development List" group.
To post to this group, send email to castle-project-devel@...
To unsubscribe from this group, send email to castle-project-devel-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en
-~----------~----~----~----~------~----~------~--~---

[Hamilton Verissimo]

Craig, I installed leopard and then just fusion running on a virtual
disk. It's much much faster than bootcamp disk. I still need bootcamp
to play games, but as I dont have much time anyway, I'll postpone its
creation :-)

Good to hear you joined the Mac camp, I'm sure you wont regret. As for
an editor, try TextMate with the optional bundles.

On 9/2/07, Craig Neuwirt <cneuwirt@...> wrote:

> Out of curiousity, why are you not using bootcamp anymore?
> Are you going to just use parrallels or VMWare for Windows?
> Leopard looks really cool, I may try it myself. :^)
>
> I am a recent mac converter to and I am trying to find my ideal environment.
> I have always been a Windows + Cygwin + Emacs guy
>
>
> On 8/31/07, Hamilton Verissimo <hammett@... > wrote:
> >
> >
> > Not really dude, sorry. I'm installing leopard on my machine, removed
> > my bootcamp partition and I'm restoring win backups, so it's going to
> > take some time to get up to speed with the code again.
> >
> > On 8/31/07, goodwill <william.yeung.hk@... > wrote:
> > >
> > > hey man how to test newgenerator? Is that in a level usable so I could
> > > test it out?
> > >
> > > On Sep 1, 4:02 am, "Hamilton Verissimo" < hamm...@...>
> > > wrote:
> > > > Thanks man!
> > > >
> > > > On 8/31/07, Roelof Blom <roelof.b...@...> wrote:
> > > >
> > > >
> > > >
> > > > > Done. I've added the 'Future' version to all projects and assigned
> it to
> > > > > unscheduled issues. (Sorry about the 15 emails from the first JIRA
> bulk
> > > > > change).
> > > >
> > > > > On 8/31/07, Roelof Blom <roelof.b...@...> wrote:
> > > > > > :-) It was meant as help, and I will update JIRA this weekend with
> the
> > > > > proposed 'Future' Fix version and assign any issue without a fix
> version to
> > > > > 'Future', if there are no objections. From there one we can move
> them in
> > > > > desired versions.
> > > >
> > > > > > BTW, does the list of versions seem correct? If it doesn't please
> fix, as
> > > > > I will use this list to create versions in the JIRA projects.
> > > >
> > > > > > On 8/31/07, Hamilton Verissimo < hamm...@...>
> wrote:
> > > >
> > > > > > > I'm asking for help, not for more aggravation :-)
> > > >
> > > > > > > On 8/31/07, Roelof Blom < roelof.b...@... > wrote:
> > > > > > > > It would help if we revise the JIRA 'Fix Version/s:' field of
> the open
> > > > > > > > issues, and put in the version (we think) it's going to be
> fixed in.
> > > > > Right
> > > > > > > > now there are lots of issues that are 'unscheduled',
> effectively
> > > > > rendering
> > > > > > > > the Roadmap view of JIRA unusable. This Roadmap is a nice way
> to drive
> > > > > > > > development towards the upcoming RC, and upcoming releases.
> > > >
> > > > > > > > I also propose a 'Future' Fix Version, this way issues can be
> > > > > scheduled
> > > > > > > > after the current release and still show up on the roadmap.
> > > >
> > > > > > > > What also would help if we communicate what the specific
> versions of
> > > > > the
> > > > > > > > individual projects are in Castle RC3, something like this:
> > > >
> > > > > > > > AR RC2
> > > > > > > > COMP RC1? (currently not versioned in JIRA)
> > > > > > > > CORE RC1? (currently not versioned in JIRA)
> > > > > > > > DYNPROXY (no idea, currently 3 different versions
> > > >
> > > > >
> http://support.castleproject.org/browse/DYNPROXY?report=com.atlassian...)
> > > > > > > > FACILITIES BETA3
> > > > > > > > IOC RC4
> > > > > > > > MR RC3
> > > > > > > > NVELOCITY RC1? (currently not versioned in JIRA)
> > > > > > > > SERVICES RC1? (currently not versioned in JIRA)As you can see
> the
> > > > > versioning
> > > > > > > > needs a little love.
> > > >
> > > > > > > > -- Roelof.
> > > >
> > > > > > > > On 8/30/07, James Curran < james.cur...@...> wrote:
> > > >
> > > > > > > > > JIRA does provide a "Priority" field, where one choice is
> "Blocker"
> > > > > (with
> > > > > > > > no items presently cited as such), and another,  "Critical" (2
> > > > > issues).  So
> > > > > > > > all that is really needed is a possible re-assessment of those
> > > > > assignments.
> > > > > > > > (Priority can be filtered on --- it's on the bottom left on
> the Issue
> > > > > > > > Navigator page)
> > > >
> > > > > > > > > On 8/30/07, josh robb < josh_r...@... > wrote:
> > > >
> > > > > > > > > > Agreed - however shouldn't we have a list of bugs which we
> > > > > consider
> > > > > > > > > > blockers for this release?
> > > >
> > > > > > > --
> > > > > > > Cheers,
> > > > > > > hamilton verissimo
> > > > > > > hamm...@...
> > > > > > >http://www.castlestronghold.com/
> > > >
> > > > --
> > > > Cheers,
> > > > hamilton verissimo
> > > >
> hamm...@...://www.castlestronghold.com/
> > >
> > >
> > > >
> > >
> >
> >
> > --
> > Cheers,
> > hamilton verissimo
> > hammett@...
> > http://www.castlestronghold.com/
> >
> > > >
> >
>

--
Cheers,
hamilton verissimo
hammett@...
http://www.castlestronghold.com/

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Castle Project Development List" group.
To post to this group, send email to castle-project-devel@...
To unsubscribe from this group, send email to castle-project-devel-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en
-~----------~----~----~----~------~----~------~--~---